Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
Create an adaptive interactive explainer dashboard for a user-specified topic, using a clean professional card-based structure with concept cards, comparisons, topic-fit sections, optional decision…
Install Topic Explainer
$ npx skills add pnp/sharepoint-skills --skill topic-explainer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pnp/sharepoint-skills topic-explainer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Skills/topic-explainer/topic-explainer .claude/skills/topic-explainer && rm -rf skills-srcUse ~/.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/
Install the "topic-explainer" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/topic-explainer/topic-explainer into .claude/skills/topic-explainer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topic-explainer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pnp/sharepoint-skills/tree/main/Skills/topic-explainer/topic-explainerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pnp/sharepoint-skills --skill topic-explainer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pnp/sharepoint-skills topic-explainer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Skills/topic-explainer/topic-explainer .agents/skills/topic-explainer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "topic-explainer" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/topic-explainer/topic-explainer into .agents/skills/topic-explainer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topic-explainer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pnp/sharepoint-skills --skill topic-explainer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pnp/sharepoint-skills topic-explainer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Skills/topic-explainer/topic-explainer .cursor/skills/topic-explainer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "topic-explainer" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/topic-explainer/topic-explainer into .cursor/skills/topic-explainer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topic-explainer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pnp/sharepoint-skills.git --path Skills/topic-explainer/topic-explainer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pnp/sharepoint-skills --skill topic-explainer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pnp/sharepoint-skills topic-explainer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Skills/topic-explainer/topic-explainer .gemini/skills/topic-explainer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "topic-explainer" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/topic-explainer/topic-explainer into .gemini/skills/topic-explainer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topic-explainer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pnp/sharepoint-skills topic-explainerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pnp/sharepoint-skills --skill topic-explainer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Skills/topic-explainer/topic-explainer .github/skills/topic-explainer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "topic-explainer" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/topic-explainer/topic-explainer into .github/skills/topic-explainer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topic-explainer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pnp/sharepoint-skills --skill topic-explainer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pnp/sharepoint-skills topic-explainer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Skills/topic-explainer/topic-explainer .opencode/skills/topic-explainer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "topic-explainer" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/topic-explainer/topic-explainer into .opencode/skills/topic-explainer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topic-explainer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
topic-explainer- GitHub stars
- 131
- Token cost
- ~1.5k tokens
- SKILL.md length
- 582 words
- Files
- 1
- Skills in repo
- 51
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create an adaptive interactive explainer dashboard for a user-specified topic, using a clean professional card-based structure with concept cards, comparisons, topic-fit sections, optional decision…
- Works in 7 steps: Identify the explainer topic, audience,… → Decide which sections fit the topic… → If a section is skipped, rebalance the… → …
- Documents & Office work in your project
- SKILL.md covers When to use, Inputs, Steps and Output format
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Topic Explainer is an agent skill from pnp/sharepoint-skills. Create an adaptive interactive explainer dashboard for a user-specified topic, using a clean professional card-based structure with concept cards, comparisons, topic-fit sections, optional decision guides, use cases, governance notes, and source notes. Use when the user says: - "create an explainer of a topic" - "create an explainer dashboard for <topic" - "make an explainer about <topic" - "turn this topic into an explainer" - "build a dashboard that explains <topic" - "create a topic explainer"
Its SKILL.md is about 1.5k 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 Documents & Office. The repository describes itself as: Skills for Copilot in SharePoint. The licence is MIT.
When your agent uses it
- Documents & Office work in your project
Example prompts
- “create an explainer of a topic”
- “create an explainer dashboard for <topic”
- “make an explainer about <topic”
- “/topic-explainer”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Identify the explainer topic, audience, and main user need from the request.
- Decide which sections fit the topic before building the dashboard. Use the strongest-fit sections only
- If a section is skipped, rebalance the layout. Do not leave an empty adjacent panel. Expand the neighboring section to full width, replace…
- Build the dashboard content around the selected sections. Common section options
- Create the dashboard as standalone HTML/CSS/JavaScript rather than raw React unless the environment explicitly supports React build output.
- Preserve a clean professional design spirit
- Use this content schema when adapting the original code
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 (its code samples are javascript).
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
Topic Explainer loads about 1.5k tokens when it runs. Until then it costs about 133 tokens; SKILL.md has 582 words of instructions outside code blocks.
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). 582 words, ~1,468 tokens.
Download SKILL.mdSave it as
.claude/skills/topic-explainer/SKILL.md (or your agent's skills folder).- name
- topic-explainer
- description
- Create an adaptive interactive explainer dashboard for a user-specified topic, using a clean professional card-based structure with concept cards, comparisons, topic-fit sections, optional decision guides, use cases, governance notes, and source notes. Use when the user says: - "create an explainer of a topic" - "create an explainer dashboard for <topic>" - "make an explainer about <topic>" - "turn this topic into an explainer" - "build a dashboard that explains <topic>" - "create a topic explainer"
Topic Explainer
When to use
Use this skill whenever the user asks to create an explainer, explainer page, or explainer dashboard for a topic. The output should be a polished, interactive HTML dashboard that explains the topic clearly for a business audience.
Use a clean, professional card-based design as the content model, but adapt the sections to fit the topic and content. Do not force every section into every dashboard.
Inputs
- Required: the topic to explain.
- Optional: target audience, organization/team context, preferred tone, source files/pages, and whether the dashboard should be saved as a SharePoint file or shown inline.
- If the topic needs current, enterprise, or document-specific information, retrieve or summarize the relevant content first. Do not invent source-specific claims.
Steps
- Identify the explainer topic, audience, and main user need from the request.
- Decide which sections fit the topic before building the dashboard. Use the strongest-fit sections only:
- Always consider: hero/header, shortest version, core concept cards, active-detail panel, comparison table, use cases/examples, governance or watch-outs, and source notes.
- Include a decision guide only when the topic asks users to choose between options, make a recommendation, follow a path, or decide “when to use what”.
- Include a Without vs With section only when the topic naturally compares adopting a capability, method, or maturity step. Skip it for side-by-side product comparisons where it feels artificial.
- Include a context overload / complexity explanation only when reusable instructions, knowledge context, complexity, or prompt burden is central to the topic.
- Include implementation, rollout, adoption, governance, or operating model sections only when relevant.
- If a section is skipped, rebalance the layout. Do not leave an empty adjacent panel. Expand the neighboring section to full width, replace the skipped section with a better-fit section, or use a single-column layout for that row.
- Build the dashboard content around the selected sections. Common section options:
- Hero/header with a short title, subtitle, and “shortest version”.
- 3–5 core concept cards for the most important ideas in the topic.
- Active concept detail panel containing: what it is, analogy, when to use it, example prompts/scenarios, and watch-outs.
- Decision guide with practical questions and recommendations, when relevant.
- Clear comparison table across the core concepts, platforms, methods, or options.
- “Without vs with” section, only when it creates real explanatory value.
- Topic-specific section such as channel selection, operating principles, adoption playbook, risks, anti-patterns, stakeholder map, maturity model, or examples.
- Searchable use cases and examples by team, role, or scenario.
- Governance notes, risks, or implementation considerations.
- Source notes listing the sources or assumptions used.
- Create the dashboard as standalone HTML/CSS/JavaScript rather than raw React unless the environment explicitly supports React build output.
- Preserve a clean professional design spirit:
- Clean card-based layout.
- Interactive concept selection.
- Search/filter for use cases where useful.
- Professional, clear tone with plain-language explanations, analogies, practical examples, and clear distinctions between concepts, benefits, limitations, and governance.
- Use this content schema when adapting the original code:
Show full SKILL.md (96 more words)Show less
const concepts = [
{
key: 'short-key',
label: 'Concept name',
plain: 'One-sentence plain-language definition.',
analogy: 'Simple analogy.',
useWhen: 'When to use this concept or approach.',
examples: ['Example 1', 'Example 2', 'Example 3'],
limits: 'Watch-out or limitation.'
}
];
const comparison = [
['Question', 'Concept A answer', 'Concept B answer', 'Concept C answer'],
['Primary purpose', '...', '...', '...'],
['Best for', '...', '...', '...'],
['Context model', '...', '...', '...'],
['Example', '...', '...', '...'],
['Governance need', '...', '...', '...']
];
const useCases = [
{ team: 'Team or role', task: 'Task or scenario', choose: 'Recommended option', value: 'Business value' }
];
const decisionTree = [
{ q: 'Practical decision question?', a: 'Recommended answer.' }
];Optional schema when the topic benefits from it:
const withoutWith = [
{ area: 'Area', without: 'What happens without this approach.', with: 'What improves with it.', why: 'Why it matters.' }
];
const topicSections = [
{ title: 'Section title', cards: [{ heading: 'Card heading', body: 'Card body' }] }
];- If saving the dashboard, create an
.htmlfile with a descriptive filename such as<topic>-explainer-dashboard.html. - If a tool fails or returns empty, say so plainly. Do not fabricate retrieved content, file URLs, or source notes.
Output format
Return a concise confirmation with:
- The dashboard title.
- Where it was created or how it was delivered.
- Any assumptions or missing sources, if relevant.
When presenting the dashboard content inline, provide only the final HTML or a short preview plus the saved file link, depending on the user's request.
© 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/topic-explainer/topic-explainer of pnp/sharepoint-skills.
Open the folder on GitHubat commit aa9eb14
Compare with similar skills
Topic Explainer 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Topic Explainer this skillpnp/sharepoint-skills | 131 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Markdown Article FormatterJimLiu/baoyu-skills | 26k | 6 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Gzh Designisjiamu/gzh-design-skill | 3.9k | 1 repos | ~2.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Obsidian Markdown
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
Gzh Design
isjiamu/gzh-design-skill
微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…
Word Document Reader and Writer
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
More from pnp/sharepoint-skills
All 51 skills in this repoScorecard 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…
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.
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.
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…
Dossier
pnp/sharepoint-skills
Renders a polished, self-contained HTML briefing from any data source — SharePoint lists, uploaded documents, or a verbal description.
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.
Related
Categories
Questions about Topic Explainer
What does Topic Explainer do?
Create an adaptive interactive explainer dashboard for a user-specified topic, using a clean professional card-based structure with concept cards, comparisons, topic-fit sections, optional decision…. Topic Explainer is an agent skill from pnp/sharepoint-skills. Create an adaptive interactive explainer dashboard for a user-specified topic, using a clean professional card-based structure with concept cards, comparisons, topic-fit sections, optional decision guides, use cases, governance notes, and source notes.
When should I use Topic Explainer?
Topic Explainer fits situations like: documents & Office work in your project.
How do I install Topic Explainer in Claude Code?
Run `npx skills add pnp/sharepoint-skills --skill topic-explainer -a claude-code`. Or copy the skill folder (Skills/topic-explainer/topic-explainer in pnp/sharepoint-skills) into .claude/skills/topic-explainer in your project. Claude Code loads it when a task matches its description.
How do I install Topic Explainer in Codex?
Run `npx skills add pnp/sharepoint-skills --skill topic-explainer -a codex`. Or copy the skill folder (Skills/topic-explainer/topic-explainer in pnp/sharepoint-skills) into .agents/skills/topic-explainer in your project. Codex loads it when a task matches its description.
Can I use Topic Explainer 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 topic-explainer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/topic-explainer, .gemini/skills/topic-explainer, .github/skills/topic-explainer and .opencode/skills/topic-explainer in your project.
What does Topic Explainer need to run?
SKILL.md names no scripts, command-line tools or credentials: Topic Explainer is instructions for the agent only.
Does Topic Explainer 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 Topic Explainer 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 Topic Explainer use?
Topic Explainer 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 Topic Explainer use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 Topic Explainer?
Skills that share tags, products or a category with Topic Explainer: Markdown Article Formatter (JimLiu/baoyu-skills, 26k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Topic Explainer?
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.