pnp

Audits the metadata quality of a SharePoint document library or list. Scans every item against its required columns, flags missing, blank, or placeholder values, computes a completeness score per item and per column, and saves a self-contained HTML gap-report dashboard to the site. It is strictly read-only — it never changes the list or its items. Use when the user says: - "metadata audit" - "metadata completeness" - "metadata health" - "missing metadata" - "audit metadata" - "metadata quality" - "check metadata" - "metadata gap report" - "which items are missing metadata" - "find blank columns"

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.

Reads the Change Events list and produces a full causal analysis of a project failure — a counterfactual root-cause test, the causal chain, intervention windows, and early-warning signal analysis — ending in one actionable recommendation, persisted back to SharePoint. Use when the user asks to "find the root cause", "run root cause analysis on the project", "what went wrong and when did we know", "trace the causal chain", or "analyze the change log". Second stage of the Project Intelligence Engine; requires the Change Events list populated by Change Event Extraction.

Generates a self-contained, dependency-free HTML timeline dashboard that visualises the Project Intelligence Engine output — KPI bar, planned-vs-actual contrast panel, root cause, causal chain, signal-trail timeline, early-warnings table, governance summary, and recommendation. Use when the user asks to "build the timeline dashboard", "visualize the project intelligence output", "generate the project intelligence dashboard", or "create the root cause HTML dashboard". Final stage of the Project Intelligence Engine; requires the Change Events list and analysis from the prior two skills.

Convert an existing Copilot Cowork skill into a Copilot in SharePoint skill. Use this skill to inspect the source skill, identify Cowork-specific assumptions, produce a SharePoint-native conversion plan, get user approval, then create or update the converted skill in AgentAssets/Skills. Use when the user says: - "Convert my skill" - "Rewrite my Cowork skill" - "Make my Cowork skill work in SharePoint" - "Adapt this Cowork skill for Copilot in SharePoint" - "Port this skill from Cowork to SharePoint"

Creates single-file HTML artifacts that render reliably in SharePoint, OneDrive, Teams, File Viewer, and embedded iframe preview surfaces. Use this skill whenever the user asks for SharePoint-safe HTML, an HTML report, dashboard, deck, artifact, visual page, one-pager, or embeddable HTML file for Microsoft 365 preview surfaces. Enforces inline CSS, no external dependencies, no runtime network calls, responsive iframe-friendly layout, optional live-linked CSV/XLSX data files, accessibility, and privacy-safe escaping.

Create a read-only permission and sharing access review report as a self-contained HTML file saved to SharePoint. Use when the user says: - "who has access" - "permission report" - "sharing report" - "access review" - "review permissions" - "create a Permission Report"

Minimal KB quality-check skill for SharePoint libraries. It creates missing review columns, writes short review outputs in Markdown, sets review status, records completion time, and schedules the next review by category.

Transform any rough prompt, request, or idea into a well-structured, context-engineered prompt using Andrej Karpathy's context engineering principles. Use this skill whenever the user asks to improve, rewrite, restructure, optimize, or "engineer" a prompt; mentions prompt engineering or context engineering; pastes a prompt and asks to make it better; wants help writing a system prompt or instructions for an AI; or says things like "turn this into a good prompt", "make this prompt work better", or "Claude isn't giving me what I want with this prompt". Also use it when the user shares a vague request and explicitly wants it converted into a reusable, high-quality prompt. Do NOT use this skill to answer or execute the original prompt itself, to write general (non-prompt) documents, or for code or content generation that isn't about crafting a prompt.

Generates valid, importable Power Apps Source Code YAML for canvas app screens. Use when asked to create YAML, scaffold, or modify any Power Apps canvas app screen — including full screens, dialogs, forms, galleries, detail views, dashboards, or any layout container — or when asked to generate Power Fx formulas or produce Power Apps source code for import.

Analyzes the user's upcoming or current work week using Work IQ signals (calendar, email volume, and semantic themes) and produces a visualized pacing report — classifying each day as Rest, Light, Focus, or Heavy based on meeting load, back-to-back density, communication volume, and available deep-work time. Designed for anxious users: leads with reassurance, names rest days first, surfaces the dominant themes of the week so it feels intentional, flags which days need focus, and ends with one concrete suggestion — never a list of warnings. Use when user asks to "show my week", "how does my week look", "is my week busy", "weekly pacing", "weekly workload", "do I have rest time", "which days are heavy", "where can I breathe this week", "workiq my week", "scan my week", "weekly rhythm check", "what's the shape of my week", or expresses anxiety about an upcoming week ("I'm dreading next week", "is this week going to be brutal"). Do NOT use for: daily briefings (use daily-briefing), single-meeting prep (use mee

Generates a weekly PowerPoint slide from a PnP copilot-prompts GitHub sample URL (for example, samples/agent-instructions/creator-agent), derives the correct weekly title from the sample folder, and produces a styled .pptx file that matches the Prompt-K template layout.

Generate comprehensive documentation for Microsoft Copilot Studio agents from exported Dataverse solutions using the Power Platform CLI. Use when asked, to analyse the solution with the agents file and create documentation from the contents.

Generate structured API reference documentation from source code, OpenAPI specs, or route definitions. Trigger phrases include "generate API docs", "document this API", "create API reference", "write endpoint docs", "scaffold API docs".

Perform structured code reviews of C# source code covering naming conventions, performance, security, readability, and .NET best practices. Trigger phrases include "review this C# code", "check my C# for best practices", "analyze this C# class", "find issues in my C# code".

This skill should be used when the user asks to "create a new prompt sample", "add a new prompt sample", "scaffold a new prompt sample", "create a prompt contribution", "add a prompt", or needs to create a new prompt sample with proper folder structure, README, and sample.json metadata. Do NOT use this skill for agent instructions or system prompts.

Use CLI for Microsoft 365 (`m365`) to manage Microsoft 365 tenants, SharePoint, Entra ID, Teams, Outlook, Planner, Power Platform, Viva, Purview, and more from the command line. Activate when the user asks to manage, query, configure, or automate anything in Microsoft 365 — including SharePoint sites/lists/pages, Entra users/groups/apps, Teams channels/messages, Outlook mail/calendars, Planner tasks, Power Automate flows, Power Apps, Viva Engage/Connections, Purview labels, OneDrive, To Do, or Microsoft Graph extensions.

This skill should be used when the user asks to "review a PR", "check this pull request", "PR review", "review pull request", "check PR against checklist", or needs to review a pull request against the project's PR checklist and coding standards.

This skill should be used when the user asks to "build a new command", "create a command", "implement a command", "add a new CLI command", or needs to build a new command for CLI for Microsoft 365 from a GitHub issue spec. It covers the full workflow: command logic, unit tests, documentation, sidebar registration, and PR checklist verification.

Regenerate the clim365 skill's command index after adding, removing, or renaming CLI for Microsoft 365 commands. Use when asked to "refresh the clim365 skill", "update the command index", "regenerate commands.txt", or after shipping a new command.

This skill should be used when the user asks to "patch vulnerabilities", "fix npm audit issues", "update vulnerable dependencies", "update outdated dependencies", "scan and fix vulnerabilities", "run npm audit and patch", "fix security vulnerabilities", "update npm packages", "check for outdated packages", or needs to comprehensively scan, patch, and re-verify npm dependencies with a cooldown safety check. Covers three blind spots: npm audit (security), npm outdated (staleness), and override checks.

Migrate CLI for Microsoft 365 commands from legacy initOptions/initValidators/initTelemetry pattern to Zod schema validation. Use when asked to "migrate to zod", "upgrade command to zod", "convert command validation to zod", or when working on commands that still use the old pattern.

Update release notes based on the latest changes from the current branch. Use when: "update release notes", "add to release notes", "write release notes", "document changes in release notes", "sync release notes with branch".

This skill should be used when the user asks to "manage products", "check inventory", "list orders", "update a product", "cancel an order", "check stock levels", or needs to perform operations against the Contoso product catalog and order management API.

This skill should be used when the user asks to "validate a sample", "check my sample", "review before submitting", "verify sample structure", or needs to validate a Dev Proxy sample for correctness before submission.

This skill should be used when the user asks to "pick up an issue", "work on issue

This skill should be used when the user asks to "create a sample", "add a new sample", "make a Dev Proxy sample", "start a new sample", "scaffold a sample", or needs to create a new Dev Proxy sample with proper structure, config files, metadata, and README.

This skill should be used when the user asks to "upgrade a sample", "update to new Dev Proxy version", "bump the version", "update schemas", or needs to upgrade existing Dev Proxy samples to a new version with updated schemas and documentation.

Extract classic SharePoint pages and build a CIM (Canonical Intermediate Model) for migration.

Orchestrate bulk classic-to-modern SharePoint page migration for an entire site. Supports plan, migrate, and refine modes.

Compare migrated modern page against the classic original using structural extraction, score quality, and refine until coverage is acceptable.

Transform classic page content into modern web parts, assemble canvas layout, and create/update the modern page.

Supplementary reference for PnP selector functions, Community Script Editor, Quick Links layouts, and JavaScript alternatives. Read on-demand for deeper migration details.

Reports important information or incidents to your line manager via email or Teams. Use when user says: "report this to my manager", "escalate this", "escalate to [manager name]", "flag this to my boss", "notify my line manager", "tell my manager about [issue]", "urgent update for my manager", "let my manager know about [incident]". Handles three criticality levels — Notify, Important, Critical — and can optionally start a coordination Teams chat. Do NOT use for: general "who is my manager" lookups, scheduling meetings with your manager, replying to an existing thread from your manager, or writing broader updates aimed at leadership or the wider team (use stakeholder-comms for audience-targeted leadership/team updates).

This is a skill to check whether a list has been customised beyond the default list or document library template.

This skill is designed to take a skill that has been submitted as a PR and scaffold it into the sample format as an expected standard by the repository.

Review PRs for Microsoft Copilot Studio samples (mcs-* folders) in pnp/copilot-pro-dev-samples.

Review PRs for declarative agent samples (da-* folders) in pnp/copilot-pro-dev-samples. Use when reviewing da-* sample submissions, checking manifest versions, validating README format. Triggers on "review PR", "review this sample", or PR review requests for declarative agent samples.

Write PowerShell scripts using CLI for Microsoft 365 commands to automate Microsoft 365 management tasks. Use when: writing PowerShell scripts that use m365 commands, automating SharePoint Online provisioning, automating Entra ID user/group management, automating Teams setup, batch operations on Microsoft 365 resources, CI/CD scripts for Microsoft 365, error handling for m365 commands in PowerShell.

Use CLI for Microsoft 365 to manage Microsoft 365 tenants from the terminal. Use when: running m365 commands, managing SharePoint Online, managing Entra ID, managing Teams teams/channels/chats, managing Power Platform, Planner, To Do,Outlook, Viva Engage, querying Microsoft Graph, authenticating to Microsoft 365, scripting Microsoft 365 automation, filtering CLI output with JMESPath.

Create and maintain AGENTS.md / CLAUDE.md snippet indexes that route tasks to the correct ai-skills skills (including compressed Vercel-style indexes).

Enforces SharePoint Framework (SPFx) best practices when generating, reviewing or refactoring SPFx code. Ensures solutions are modern, maintainable, performant, secure and aligned with official guidance and community patterns.

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