Agent skill

Dossier

by pnp in pnp/sharepoint-skills

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

MITAuto-check passedDocuments & Office

Install Dossier

skills CLI
$ npx skills add pnp/sharepoint-skills --skill dossier -a claude-code

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

GitHub CLI
$ gh skill install pnp/sharepoint-skills dossier --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/dossier/dossier .claude/skills/dossier && 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
dossier
GitHub stars
131
Token cost
~1.9k tokens
SKILL.md length
950 words
Files
4 (incl. references, assets)
Skills in repo
51
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 6 steps: Determine the Data Source → Interview the User → Choose the Rendering Mode → …
  • Asked to build a competitor landscape
  • SKILL.md covers Step 1: Determine the Data…, Step 2: Interview the User, Step 3: Choose the Rendering… and Step 4: Decide What Goes Where, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Dossier is an agent skill from pnp/sharepoint-skills. Renders a polished, self-contained HTML briefing from any data source — SharePoint lists, uploaded documents, or a verbal description. Use when asked to build a competitor landscape, account brief, candidate summary, site inventory, board bio, speaker profile, partner overview, or any grid of profile cards or single-subject one-pager. Interviews the user if data is incomplete, constructs a validated JSON document, then renders it into a sandbox-safe HTML file using grid mode (2–8 subjects as responsive cards) or…

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files and assets (for example `references/components.md` and `references/design-system.md`).

It sits in Documents & Office, covering Cloud office suites and Sales call preparation. It works with Microsoft SharePoint. The repository describes itself as: Skills for Copilot in SharePoint. The licence is MIT.

When your agent uses it

  • Asked to build a competitor landscape
  • Candidate summary
  • Speaker profile
  • Partner overview

Example prompts

  • “Use the dossier skill to render a polished, self-contained HTML briefing from any data source — SharePoint lists, uploaded documents, or a verbal…”
  • “/dossier”

Workflow steps

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

  1. Determine the Data Source
  2. Interview the User
  3. Choose the Rendering Mode
  4. Decide What Goes Where
  5. Build and Validate the JSON Document
  6. Render the HTML

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

Dossier loads about 1.9k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 162 tokens; SKILL.md has 950 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~162
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~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). 950 words, ~1,904 tokens.

Download SKILL.mdSave it as .claude/skills/dossier/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
dossier
description
Renders a polished, self-contained HTML briefing from any data source — SharePoint lists, uploaded documents, or a verbal description. Use when asked to build a competitor landscape, account brief, candidate summary, site inventory, board bio, speaker profile, partner overview, or any grid of profile cards or single-subject one-pager. Interviews the user if data is incomplete, constructs a validated JSON document, then renders it into a sandbox-safe HTML file using grid mode (2–8 subjects as responsive cards) or one-pager mode (1 subject as a rich briefing). No external dependencies — output runs inside a SharePoint sandboxed iframe.
metadata.author
zrosenfield

Dossier

Generates a complete, self-contained HTML briefing by (1) interviewing the user or parsing their data, (2) constructing and validating a JSON document, then (3) rendering that JSON into HTML using assets/dossier-template.html. The JSON is the authoritative source of truth; the HTML is fully determined by it.


Step 1: Determine the Data Source

Check what the user has already provided before asking anything:

  • SharePoint lists: Call list_items on the relevant lists. Read all needed columns before proceeding.
  • Uploaded documents or tables pasted in chat: Parse all content. Do not ask for data you already have.
  • Verbal description only: Proceed to Step 2.

Step 2: Interview the User

If the data or intent is not fully clear, ask these questions in a single message — not one at a time:

  1. Subject type: What are you profiling? (competitors, accounts/prospects, candidates, SharePoint sites, board members, speakers, partners, vendors — or something else)
  2. Subject count: How many subjects? This determines the rendering mode.
  3. Purpose and audience: What decision does this briefing support? Who reads it? This determines detail level and which key facts matter most.
  4. Key facts: What are the 3–6 structured facts most important for each subject? Examples for competitors: HQ, founded, ARR, headcount. For candidates: current role, tenure, location, skills. For sites: owner, content type, last activity.
  5. Narrative emphasis: Should the summary emphasize product/capabilities, financials, relationships, risks, or something else?
  6. Palette: Warm paper (cream/terra-cotta), deep ink (dark/gold), clean white (white/green), or slate (gray/blue)? Default to warm paper.
  7. Mode override (only ask if count is 1 or user seems to want detail): Do you want a full one-pager briefing or a compact card?

Confirm your understanding before building the JSON.


Step 3: Choose the Rendering Mode

Auto-detection rule:

  • 2–8 subjects → grid mode
  • 1 subject → one-pager mode
  • User explicitly says "one-pager" or "full briefing" → one-pager mode regardless of count
  • User explicitly says "grid" or "landscape" → grid mode

Do not ask about mode unless the count is exactly 1 and the user has not indicated a preference.


Step 4: Decide What Goes Where

Key facts hold structured, scannable, low-word-count data — the kind of facts a reader needs in 5 seconds. Rules:

  • 3–6 pairs. No sentences. Values should be short (under 6 words).
  • Good: "HQ | Austin, TX", "ARR | ~$40M est.", "Founded | 2019"
  • Bad: "Company description | This is a company that..." (belongs in summary)

Tags are the fastest signal — 2–5 short labels that classify the subject. Use for: industry vertical, stage, geography, product category, or any grouping the reader uses for orientation.

Summary is 2–5 sentences of prose. Write in third person. Lead with the most important fact. No bullet points. This is the editorial paragraph — what an analyst would write.

Activity holds the 2–5 most recent, most relevant developments — in most-recent-first order. Each item gets a short date prefix (e.g., "Apr 2026") and a one-sentence description. For competitors: product launches, fundraises, acquisitions, executive changes. For candidates: recent projects, promotions, publications. For sites: content updates, ownership changes, traffic milestones.


Show full SKILL.md (453 more words)Show less

Step 5: Build and Validate the JSON Document

Construct the JSON object. Top-level structure:

report object (document metadata):

FieldRequiredDescription
titleyesPage title, e.g. "Competitor Landscape — Q2 2026"
subtitlenoOptional subtitle shown below title
paletteyeswarm-paper, deep-ink, clean-white, or slate
modeno"grid", "one-pager", or "auto" (default: "auto")
footernoFooter text, e.g. "Prepared May 28, 2026 · Confidential"

subjects array — ordered list of subject objects (1–8 items):

FieldRequiredDescription
idyesUnique slug, e.g. "acme-corp"
nameyesSubject display name
typeyesCategory label shown as a pill, e.g. "Competitor", "Prospect", "Enterprise Site"
statusnoStatus label text, e.g. "Active", "Watch", "Inactive"
status_colornogreen, amber, red, gray, or blue
key_factsyesArray of {label, value} pairs, 2–6 items
tagsyesArray of strings, 1–6 tags
summaryyes2–5 sentence prose paragraph
activitynoArray of {date, text} items, 0–5, most-recent first
Validation Checklist

Run every check before rendering. Fix any failure before proceeding.

Document level:

  • report.palette is one of: warm-paper, deep-ink, clean-white, slate
  • subjects array has 1–8 entries
  • report.mode is "grid", "one-pager", or "auto" (or omitted)

Per subject:

  • id is present and unique
  • name and type are present and non-empty
  • key_facts has 2–6 items; each item has label and value
  • tags has 1–6 items
  • summary is present and 2–5 sentences
  • status_color (if present) is one of: green, amber, red, gray, blue
  • activity items (if present) each have date and text; at most 5 items

Data integrity:

  • No key_facts value is a sentence — values must be short labels
  • Activity items are ordered most-recent first
  • Subject count matches the chosen mode (grid: 2–8, one-pager: 1; or mode is explicitly set)

Step 6: Render the HTML

  1. Read assets/dossier-template.html.
  2. Replace {{REPORT_TITLE}} in <title> with a concise page title.
  3. Replace {{PALETTE_CLASS}} on <body> with palette- + the palette name.
  4. Determine final mode: if report.mode is "auto" or omitted, use "grid" for 2–8 subjects and "one-pager" for 1 subject.
  5. Replace {{PAGE_HEADER}} with the .rpt-header strip (title + optional subtitle).
  6. Replace {{CONTENT}} with the rendered subjects — either the grid of cards or the one-pager layout. See references/components.md for exact HTML patterns.
  7. Replace {{FOOTER}} with the footer text (or empty string).
  8. Deliver the complete file as the response. No prose outside the file.

Hard Constraints

  • No external URLs, CDN links, or web fonts in the output HTML.
  • No <script src> tags. All JavaScript must be inline.
  • All values must be pre-rendered — the page must be fully correct with JavaScript disabled.
  • Do not generate Python, PowerShell, or any other scripts — output is always the HTML file.
  • Do not render until the validation checklist passes.
  • Do not use SharePoint Person column types in any accompanying list schema — use text columns only.

© 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

SKILL.md and 3 other files (references, assets) in Skills/dossier/dossier of pnp/sharepoint-skills.

  • SKILL.md
  • assets/dossier-template.html
  • references/components.md
  • references/design-system.md

Open the folder on GitHubat commit aa9eb14

Compare with similar skills

Dossier 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.

Dossier compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dossier this skillpnp/sharepoint-skills131—~1.9kAutomated safety check: PassMIT
Colleague DistillationZhixiangLuo/10xProductivity478—~2.1kAutomated safety check: NotesMIT
Msgraphcodemie-ai/codemie-code294—~4.1kAutomated safety check: PassApache-2.0
aai-cli Microsoft 365aai-labs/agent-barn109—~1.2kAutomated safety check: PassApache-2.0
Workiqmicrosoft/work-iq1k—~15kAutomated safety check: PassCustom licence
Workiq Previewmicrosoft/work-iq1k—~3.3kAutomated safety check: PassCustom licence

Similar skills

  • Colleague Distillation

    ZhixiangLuo/10xProductivity

    Distill a colleague into a reusable AI skill (work + persona) using tool connections — Slack, Slack AI, Jira, GHE, Bitbucket, Confluence, SharePoint, Teams, Outlook, Notion, Linear, Google Docs, and…

    478 GitHub stars~2.1k tokensUpdated 2 mo ago
    Documents & OfficeAuto-check: notes
  • Msgraph

    codemie-ai/codemie-code

    Work with Microsoft 365 services via the Graph API — emails, calendar events, SharePoint sites (read and write), Teams chats and channel messages, OneDrive files, OneNote notebooks, Planner task…

    294 GitHub stars~4.1k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • aai-cli Microsoft 365

    aai-labs/agent-barn

    Guides work with Outlook, OneDrive, SharePoint, Teams, Excel, To Do and Planner through aai-cli's Microsoft Graph commands, starting from which service owns the data.

    109 GitHub stars~1.2k tokensUpdated today
    Documents & OfficeAuto-check passed
  • Workiq

    microsoft/work-iq

    Official

    WorkIQ tools for Microsoft 365 workplace data and actions. An agent skill from microsoft/work-iq.

    1k GitHub stars~15k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Workiq Preview

    microsoft/work-iq

    Official

    WorkIQ tools for Microsoft 365 workplace data and actions. An agent skill from microsoft/work-iq.

    1k GitHub stars~3.3k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Hunt Ntlm Info

    sickn33/agentic-awesome-skills

    Hunt NTLM/Negotiate information disclosure on internet-reachable IIS/SharePoint/Exchange.

    47k GitHub starsUsed in 1 repo~4.7k 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…

    131 GitHub stars~1.9k tokensUpdated 2 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.

    131 GitHub stars~899 tokensUpdated 2 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.

    131 GitHub stars~2.5k tokensUpdated 2 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…

    131 GitHub stars~1.2k tokensUpdated 2 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.

    131 GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed
  • File Classifier

    pnp/sharepoint-skills

    Classifies files in a SharePoint document library by reading their content and matching them to known content types (Contracts, Invoices, Purchase Orders).

    131 GitHub stars~4.1k tokensUpdated 2 days ago
    Auto-check passed

Questions about Dossier

What does Dossier do?

Renders a polished, self-contained HTML briefing from any data source — SharePoint lists, uploaded documents, or a verbal description. Dossier is an agent skill from pnp/sharepoint-skills. Renders a polished, self-contained HTML briefing from any data source — SharePoint lists, uploaded documents, or a verbal description.

When should I use Dossier?

Dossier fits situations like: asked to build a competitor landscape; candidate summary; speaker profile; partner overview.

How do I install Dossier in Claude Code?

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

How do I install Dossier in Codex?

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

Can I use Dossier 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 dossier -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dossier, .gemini/skills/dossier, .github/skills/dossier and .opencode/skills/dossier in your project.

What does Dossier need to run?

SKILL.md names no scripts, command-line tools or credentials: Dossier is instructions for the agent only.

Does Dossier 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 Dossier 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 Dossier use?

Dossier 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 Dossier use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.1k tokens, read only when the agent opens those files.

What are the alternatives to Dossier?

Skills that share tags, products or a category with Dossier: Colleague Distillation (ZhixiangLuo/10xProductivity, 478 stars), Msgraph (codemie-ai/codemie-code, 294 stars), aai-cli Microsoft 365 (aai-labs/agent-barn, 109 stars) and Workiq (microsoft/work-iq, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dossier?

pnp (a GitHub organization) maintains it in pnp/sharepoint-skills, which has 131 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.