Our review
Generates a comprehensive Markdown catalog of all available Claude skills by scanning personal, project, and plugin directories.
Strengths
- Automatically discovers skills from three distinct sources
- Plugin skill discovery is scoped to enabled plugins only, avoiding unnecessary scanning
- Outputs a well-structured Markdown table that is easy to read and use
Limitations
- Requires correct plugin configuration in JSON files
- Only reads the YAML frontmatter (first 5 lines) of SKILL.md files
- Plugin discovery is multi-step and may fail if paths or manifest structures are incorrect
When you need to inventory all Claude skills in your environment for documentation, auditing, or sharing purposes.
If you need to use a specific skill rather than list them all, or if the environment has no plugins and minimal custom skills.
Security analysis
SafeThe skill only reads local files within specified directories and writes a summary markdown file. No destructive, network, or exfiltration actions are performed. All allowed tools are safe reads (echo, cat, find, ls). No execution of downloaded scripts or risky commands.
No concerns found
Examples
Generate Markdown catalog of all available Claude skills and save to SKILLS.mdScan ~/.claude/skills for SKILL.md files and create a table of themDiscover all enabled plugins from settings.json, find their skills, and include them in the exportname: skill-export description: Export Claude skills. Use to generate documentation of all available Claude Skills. allowed-tools: TodoWrite, Glob, Read, Bash(echo:), Bash(cat:), Bash(find:), Bash(ls:) license: MIT
Skill Export
Generate a comprehensive markdown catalog of all Claude skills available in the environment.
Workflow
Discover Skills from Three Sources
Personal Skills: ~/.claude/skills/*/SKILL.md
- Scan all subdirectories for SKILL.md files
Project Skills: .claude/skills/*/SKILL.md
- Scan all subdirectories relative to current working directory
Plugin Skills: Requires careful multi-step discovery
- Read
~/.claude/settings.jsonto get enabled plugins (format:plugin-name@marketplace-id) - Parse each plugin ID into plugin name and marketplace ID
- Look up marketplace location in
~/.claude/plugins/known_marketplaces.json - Read
{marketplaceLocation}/.claude-plugin/marketplace.jsonto get the marketplace manifest - Find the specific plugin by name in the manifest's
pluginsarray - Only scan skills listed in that plugin's
skillsarray (do not scan entire marketplace) - For each skill path, read
{marketplaceLocation}/{skillPath}/SKILL.md
Critical: Plugin discovery must be scoped to enabled plugins. Do not scan all skills in a marketplace—only those listed in the specific enabled plugin's manifest entry.
Extract and Format
For each SKILL.md file:
- Parse YAML frontmatter to extract
nameanddescription. - Record location as absolute path to the skill directory (use
dirname()of SKILL.md path)
Critical: Only read the YAML frontmatter, i.e., the top 5 lines, of SKILL.md files.
Generate markdown table:
# Skills
Skills are additional instructions for specific scenarios. Given below is a list of name, description, and location of all available skills.
If a skill is relevant to the task you're performing based on its description, read the SKILL.md file at the location of that skill for additional instructions.
| Name | Description | Location |
|------|-------------|----------|
| skill-name | Description text | /absolute/path/to/skill |
Formatting: escape pipe characters (\|), remove newlines from descriptions, sort by location type then name.
Write Output
Write the output into a SKILLS.md file at the current working directory. Write the generated markdown into the file, and display summary to the user in chat.
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Pivot Decision Framework
Documentation
Documents a strategic pivot or persevere decision with evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.