New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Project Intelligence Change Event Extraction

by pnp in pnp/sharepoint-skills

Reads every document in a SharePoint project library and compiles a complete, structured record of every change event — scope assumptions, scope changes, technical decisions, client requests, risks…

MITAuto-check passedDevelopment

Install Project Intelligence Change Event Extraction

skills CLI
$ npx skills add pnp/sharepoint-skills --skill project-intelligence-change-event-extraction -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pnp/sharepoint-skills project-intelligence-change-event-extraction --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Skills/project-intelligence-change-event-extraction/project-intelligence-change-event-extraction .claude/skills/project-intelligence-change-event-extraction && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
project-intelligence-change-event-extraction
GitHub stars
132
Token cost
~2.6k tokens
SKILL.md length
1,343 words
Files
1
Skills in repo
51
Repo updated
First seen
Licence
MIT

At a glance

Reads every document in a SharePoint project library and compiles a complete, structured record of every change event — scope assumptions, scope changes, technical decisions, client requests, risks…

  • Works in 4 steps: Read all documents → Identify change events → Extract all fields for every event → …
  • The user asks to extract change events from the project
  • SKILL.md covers Purpose, Step 1 — Read all documents, Step 2 — Identify change events and Step 3 — Extract all fields…, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Project Intelligence Change Event Extraction is an agent skill from pnp/sharepoint-skills. Reads every document in a SharePoint project library and compiles a complete, structured record of every change event — scope assumptions, scope changes, technical decisions, client requests, risks, budget and schedule events, governance events, and early-warning signals — writing each to the Change Events SharePoint list with signal strength and governance flags. Use when the user asks to "extract change events from the project", "build the project change log", "find the signals in these project documents"…

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Cloud office suites and Root cause analysis. It works with Microsoft SharePoint. The repository describes itself as: Skills for Copilot in SharePoint. The licence is MIT.

When your agent uses it

  • The user asks to extract change events from the project
  • Build the project change log
  • Find the signals in these project documents
  • Populate the Change Events list

Example prompts

  • “extract change events from the project”
  • “build the project change log”
  • “find the signals in these project documents”
  • “/project-intelligence-change-event-extraction”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Read all documents
  2. Identify change events
  3. Extract all fields for every event
  4. Write to the Change Events list

What it can do on your machine

Read from SKILL.md and the folder at commit aa9eb14. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Project Intelligence Change Event Extraction loads about 2.6k tokens when it runs. Until then it costs about 184 tokens; SKILL.md has 1,343 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~184
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pnp/sharepoint-skills at commit aa9eb14, republished under its MIT licence (© pnp). 1,343 words, ~2,559 tokens.

Download SKILL.mdSave it as .claude/skills/project-intelligence-change-event-extraction/SKILL.md (or your agent's skills folder).
name
project-intelligence-change-event-extraction
description
Reads every document in a SharePoint project library and compiles a complete, structured record of every change event — scope assumptions, scope changes, technical decisions, client requests, risks, budget and schedule events, governance events, and early-warning signals — writing each to the Change Events SharePoint list with signal strength and governance flags. Use when the user asks to "extract change events from the project", "build the project change log", "find the signals in these project documents", "populate the Change Events list", or "start the Project Intelligence Engine on this site". First stage of the Project Intelligence Engine; its output feeds Root Cause Analysis.

Change Event Extraction

Purpose

Read every document in this project library and compile a complete, structured record of every event that affected — or should have affected — the project's scope, timeline, budget, or technical approach. This is the factual foundation for all subsequent analysis. Be thorough: a signal buried in a footnote is as important as a formal change request.

Step 1 — Read all documents

Process ALL documents in the Project Documents library. Note each document's title, author (if stated), and date. Do not skip or skim any document. Read attachments, appendices, and meeting notes as carefully as the main body.

Step 2 — Identify change events

For each document, identify every instance of the following event types:

Event typeWhat qualifies
Scope assumption establishedA baseline, estimate, or assumption that the project plan, budget, or timeline depends on — especially if unvalidated
Scope changeAddition, reduction, or modification to agreed deliverables, data, or work
Technical decisionArchitecture or technology choice made or changed during delivery
Client requestAny instruction or request from the client affecting scope, approach, schedule, or budget — formal or informal
Risk eventRisk identified, rating changed, risk materialising, risk dismissed, or risk downgraded below its true severity
Budget eventCost variance, overrun, approved financial change, or budget assumption set
Schedule eventMilestone slippage, date change, sprint replan, or timeline extension
Governance eventChange request raised, steering committee decision, approval, escalation, or missed change control step
Signal / early warningAny observation, comment, or flagged item that indicated potential future risk — even if not formally escalated

Step 3 — Extract all fields for every event

For each event, extract every field in the table below. If a field is not documented, state "Not documented" — do not omit the field or leave it blank.

FieldWhat to captureIf not available
#Sequential event number
DateExact date if statedApproximate (e.g. "~Week 5")
WeekEngagement week numberDerive from date if possible
Event typeOne of the categories above
Source documentFile name and section or heading
TitleShort descriptive title, 5–8 words
DescriptionOne factual sentence — exactly what happened
Parameter changedSpecific value that changed, with before/after (e.g. "Data volume: 2 TB → 6.24 TB")"N/A — no parameter change"
Reason / rationaleWhy did this happen? What drove the change or decision? Quote the source if available"Not documented"
Raised byName and role of person who raised, flagged, or initiated the event"Not documented"
Approved / acknowledged byName and role of person who formally approved or acknowledged, or "Not required" / "Not obtained""Not documented"
Action takenWhat was done in response — CR raised, risk logged, observation noted, escalated, ignored"No action documented"
Missing informationWhat should have been captured, validated, or escalated but was not — be specific"None identified"
ImpactDownstream consequence this event had or could have had — be specific and quantify if possible
Change order raised?Yes / No / Pending / Not Applicable
Signal strengthHIGH = project-threatening if unresolved; MEDIUM = concerning, warrants escalation; LOW = noted for awareness

Step 4 — Write to the Change Events list

For each event extracted in Step 3, create one item in the Change Events list on this SharePoint site. Use the exact column names defined in SHAREPOINT.md. Populate every column for every event. Do not skip any event.

If an item for this event already exists in the list (matched by Title and Date), update it rather than creating a duplicate.

After all items are written, confirm the count: "N events written to the Change Events list."

Output — produce the following in chat

SECTION 1: CHAT SUMMARY

Begin with the following framing statement, exactly as written:

"Names in this log record who held information or decision authority at each event point. This analysis identifies process and governance gaps — where controls were needed and not in place."

Then produce the following:

Change Events list: State the total count — "[N] change events have been written to the Change Events list on this site." Do not reproduce the full change log table in chat.

Headline metrics:

  • HIGH signal events: list each by title
  • Events with no change order raised: count and % of total
  • Governance gap score: N / 10
  • Scope Churn Index: N%

Missing Information Summary: a bulleted list of the most significant documentation gaps across all events — things that should exist in a well-run engagement but were absent. Be direct and specific. Examples: "No formal validation of the Week 2 data volume estimate is documented anywhere in the project record." or "Risk R-009 was rated Medium/Low but no quantitative basis for that rating is recorded."

SECTION 2: THREE SUMMARY LEVELS

Produce all three of the following, clearly labelled:

ULTRA-SHORT SUMMARY

For: executive slide decks, steering committee updates, RAID log entries

Write 4–6 bullet points. Each bullet is one sentence. Cover only the most consequential events — decisions made, things that went wrong, and outcomes. A reader should be able to read this in 20 seconds and understand the project's critical path of failure. No background, no process detail.

Show full SKILL.md (517 more words)Show less
GET ME UP TO SPEED

For: a new project manager stepping in, a delivery director being briefed, a client asking "what happened"

Write 3–5 paragraphs as a coherent narrative. Chronological. Imagine you are briefing someone intelligent who knows nothing about this project and has 3 minutes. Cover: what the project was, the key decisions and assumptions made, what signals appeared and how they were handled, when the failure became visible, and what the current situation is. Include specific dates, numbers, names, and document references. Write in plain English — no jargon, no passive voice.

DETAILED FULL HISTORY

For: post-mortem reviews, governance audits, contract disputes, lessons learned

A structured narrative with one paragraph per major phase or cluster of events. This is the complete record — every event matters. Include all rationale recorded, who knew what and when, what was actioned and what was not, and where the documentation record falls short. Do not summarise away detail. This section should be suitable for use in a formal project review or as background for a legal review.

SECTION 3: PROJECT INTELLIGENCE DASHBOARD

Produce this section under the heading ## PROJECT INTELLIGENCE DASHBOARD.

Change Event KPIs
KPIValueCommentary
Total change events extracted
Events with no change order raisedInclude % of total
Events with undocumented or missing rationaleInclude % of total
Events with no named approverInclude % of total
HIGH signal strength events
HIGH signal events that were formally actionedState as "N of N"
Weeks between first HIGH signal and impact eventQuantifies how long the window was open
Change concentration periodThe engagement week range with highest event density
Governance gap scoreRate 0–10: 0 = all changes properly governed; 10 = none
Change Type Breakdown

State the count of events by type. Example format: 3 scope events · 4 risk events · 2 governance events · 1 budget event · 2 schedule events

Scope Churn Index

For every project parameter that changed between baseline and actual (data volume, table count, budget, timeline, team size, etc.):

ParameterBaseline valueSource of baselineActual valueSource of actualVarianceVariance %

Sum the absolute variance percentages and divide by the number of parameters — this is the overall Scope Churn Index. A score above 50% indicates a project that was significantly mispriced or misscoped at inception.

Top 3 Governance Gaps

The three most consequential instances where a change, risk, or assumption should have triggered formal governance but did not. Each gap on one line: what it was, when it was present, and what the correct governance action should have been.

  1. [Gap description — date — correct action]
  2. [Gap description — date — correct action]
  3. [Gap description — date — correct action]
Documentation Quality Rating

Rate the overall quality of the project's change management documentation on a scale of 1–5:

  • 5 — Complete: every change has rationale, approver, and action documented
  • 4 — Good: most changes documented; minor gaps
  • 3 — Partial: key decisions documented but rationale and approvals often missing
  • 2 — Poor: events can be inferred but documentation is sparse and inconsistent
  • 1 — Inadequate: significant events reconstructed from context; major gaps in record

State the rating and one sentence explaining the primary reason for the score.

© pnp, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in Skills/project-intelligence-change-event-extraction/project-intelligence-change-event-extraction of pnp/sharepoint-skills.

Open the folder on GitHubat commit aa9eb14

Compare with similar skills

Project Intelligence Change Event Extraction next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Project Intelligence Change Event Extraction compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Project Intelligence Change Event Extraction this skillpnp/sharepoint-skills132—~2.6kAutomated safety check: PassMIT
CLI Microsoft365pnp/cli-microsoft365-mcp-server132—~3.5kAutomated safety check: PassMIT
Spfx Releasepnp/docker-spfx134—~572Automated safety check: NotesMIT
CLI Microsoft365 Scriptpnp/cli-microsoft365-mcp-server132—~3.3kAutomated safety check: PassMIT
Sap Btp Build Work Zone Advancedsecondsky/sap-skills462—~3.3kAutomated safety check: PassGPL-3.0
Msgraph SDKgithub/awesome-copilot40k—~2.1kAutomated safety check: PassMIT

Similar skills

  • CLI Microsoft365

    pnp/cli-microsoft365-mcp-server

    Use CLI for Microsoft 365 to manage Microsoft 365 tenants from the terminal.

    132 GitHub stars~3.5k tokensUpdated 3 days ago
    Documents & OfficeAuto-check passed

  • Spfx Release

    pnp/docker-spfx

    Automate SPFx version releases - branch, update files, commit, open PR, then tag after merge

    134 GitHub stars~572 tokensUpdated 3 mo ago
    Documents & OfficeAuto-check: notes

  • CLI Microsoft365 Script

    pnp/cli-microsoft365-mcp-server

    Write PowerShell scripts using CLI for Microsoft 365 commands to automate Microsoft 365 management tasks.

    132 GitHub stars~3.3k tokensUpdated 3 days ago
    Documents & OfficeAuto-check passed

  • Sap Btp Build Work Zone Advanced

    secondsky/sap-skills

    Develops and administers SAP Build Work Zone, advanced edition digital workplace solutions.

    462 GitHub stars~3.3k tokensUpdated 4 days ago
    Backend & APIsAuto-check passed

  • Msgraph SDK

    github/awesome-copilot

    Official

    Integrate Microsoft Graph SDK into any project — .NET, TypeScript/JavaScript, or Python.

    40k GitHub stars~2.1k tokensUpdated today
    Documents & OfficeAuto-check passed

  • Add Data Source

    microsoft/power-platform-skills

    Official

    Guide the user to add a data source, connection, or API connector to a Canvas App via Power Apps Studio, then verify and continue.

    979 GitHub starsUsed in 1 repo~1.1k tokens
    Documents & OfficeAuto-check passed

More from pnp/sharepoint-skills

All 51 skills in this repo

  • Scorecard Matrix

    pnp/sharepoint-skills

    Generates a polished, self-contained HTML heatmap scorecard — a weighted comparison matrix where entities (rows) are scored across dimensions (columns), with computed totals, rank badges, and a…

    132 GitHub stars~1.9k tokensUpdated 3 days ago
    Auto-check passed

  • Analyze Document Library

    pnp/sharepoint-skills

    Analyze the current SharePoint document library in read-only mode and produce a structured summary of files, folders, file types, recent activity, naming issues, and organization recommendations.

    132 GitHub stars~899 tokensUpdated 3 days ago
    Auto-check passed

  • Broken Link Auditor

    pnp/sharepoint-skills

    Audits SharePoint pages, news posts, and hyperlink fields for broken or risky links and saves a self-contained HTML link-health report to the site.

    132 GitHub stars~2.5k tokensUpdated 3 days ago
    Auto-check passed

  • Custom Image Tagger

    pnp/sharepoint-skills

    Analyze selected construction images, create missing object metadata columns, and write concise visual metadata back to SharePoint columns using explicit image-analysis, list-schema, list-update…

    132 GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed

  • Dossier

    pnp/sharepoint-skills

    Renders a polished, self-contained HTML briefing from any data source — SharePoint lists, uploaded documents, or a verbal description.

    132 GitHub stars~1.9k tokensUpdated 3 days ago
    Auto-check passed

  • Exec Report

    pnp/sharepoint-skills

    Generates a polished, self-contained HTML executive report or dashboard from any data source — SharePoint lists, CSV exports, or a user description.

    132 GitHub stars~2k tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Project Intelligence Change Event Extraction

What does Project Intelligence Change Event Extraction do?

Reads every document in a SharePoint project library and compiles a complete, structured record of every change event — scope assumptions, scope changes, technical decisions, client requests, risks…. Project Intelligence Change Event Extraction is an agent skill from pnp/sharepoint-skills. Reads every document in a SharePoint project library and compiles a complete, structured record of every change event — scope assumptions, scope changes, technical decisions, client requests, risks, budget and schedule events, governance events, and early-warning signals — writing each to the Change Events SharePoint list with signal strength and governance flags.

When should I use Project Intelligence Change Event Extraction?

Project Intelligence Change Event Extraction fits situations like: the user asks to extract change events from the project; build the project change log; find the signals in these project documents; populate the Change Events list.

How do I install Project Intelligence Change Event Extraction in Claude Code?

Run `npx skills add pnp/sharepoint-skills --skill project-intelligence-change-event-extraction -a claude-code`. Or copy the skill folder (Skills/project-intelligence-change-event-extraction/project-intelligence-change-event-extraction in pnp/sharepoint-skills) into .claude/skills/project-intelligence-change-event-extraction in your project. Claude Code loads it when a task matches its description.

How do I install Project Intelligence Change Event Extraction in Codex?

Run `npx skills add pnp/sharepoint-skills --skill project-intelligence-change-event-extraction -a codex`. Or copy the skill folder (Skills/project-intelligence-change-event-extraction/project-intelligence-change-event-extraction in pnp/sharepoint-skills) into .agents/skills/project-intelligence-change-event-extraction in your project. Codex loads it when a task matches its description.

Can I use Project Intelligence Change Event Extraction in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pnp/sharepoint-skills --skill project-intelligence-change-event-extraction -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/project-intelligence-change-event-extraction, .gemini/skills/project-intelligence-change-event-extraction, .github/skills/project-intelligence-change-event-extraction and .opencode/skills/project-intelligence-change-event-extraction in your project.

What does Project Intelligence Change Event Extraction need to run?

SKILL.md names no scripts, command-line tools or credentials: Project Intelligence Change Event Extraction is instructions for the agent only.

Does Project Intelligence Change Event Extraction access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Project Intelligence Change Event Extraction safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Project Intelligence Change Event Extraction use?

Project Intelligence Change Event Extraction is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Project Intelligence Change Event Extraction use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Project Intelligence Change Event Extraction?

Skills that share tags, products or a category with Project Intelligence Change Event Extraction: CLI Microsoft365 (pnp/cli-microsoft365-mcp-server, 132 stars), Spfx Release (pnp/docker-spfx, 134 stars), CLI Microsoft365 Script (pnp/cli-microsoft365-mcp-server, 132 stars) and Sap Btp Build Work Zone Advanced (secondsky/sap-skills, 462 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Project Intelligence Change Event Extraction?

pnp (a GitHub organization) maintains it in pnp/sharepoint-skills, which has 132 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on October 6, 2026.

Source: pnp/sharepoint-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.