Claude Skills Export

VerifiedSafe

Generates a comprehensive markdown catalog of all Claude skills from personal, project, and plugin sources. It helps you document or review all available skills in your environment at a glance.

Sby Skills Guide Bot
DocumentationIntermediate
6/2/2026
Claude Code
#skill-export#documentation#catalog#markdown#skills-management

Recommended for

Automated summary

Generates a comprehensive markdown catalog of all available Claude skills from personal, project, and plugin sources.

Strengths

  • Automates documentation of skills
  • Scans multiple sources (personal, project, plugins)
  • Outputs an organized markdown table
  • Handles discovery of enabled plugins

Limitations

  • Requires Claude-specific file structure
  • Plugin discovery is complex and error-prone
  • Only reads YAML frontmatter, not full skill content
When to use it

Use when you need to create or update an inventory of all installed Claude skills for reference or sharing.

When not to use it

Do not use if you want to modify skills or understand their full content; it is not suitable for non-Claude environments.

Security analysis

Safe
Quality score90/100

The skill only reads existing SKILL.md files and generates a documentation file using echo. The allowed bash tools are read-only (cat, find, ls) and echo, posing no risk of data loss, exfiltration, or destructive actions.

No concerns found

How this analysis is made

Examples

Export all skills
Export all available Claude skills to a markdown catalog file.
Generate skills documentation
Generate a documentation file (SKILLS.md) listing all personal, project, and plugin skills.
Create skills inventory
Create an inventory of all installed Claude skills with their names, descriptions, and locations.

name: 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

  1. Read ~/.claude/settings.json to get enabled plugins (format: plugin-name@marketplace-id)
  2. Parse each plugin ID into plugin name and marketplace ID
  3. Look up marketplace location in ~/.claude/plugins/known_marketplaces.json
  4. Read {marketplaceLocation}/.claude-plugin/marketplace.json to get the marketplace manifest
  5. Find the specific plugin by name in the manifest's plugins array
  6. Only scan skills listed in that plugin's skills array (do not scan entire marketplace)
  7. 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 name and description.
  • 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.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/claude-skills-export-mm78nncj/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/claude-skills-export-mm78nncj' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/claude-skills-export-mm78nncj/download' --output '.skill-downloads/claude-skills-export-mm78nncj/SKILL.md.part' && mv '.skill-downloads/claude-skills-export-mm78nncj/SKILL.md.part' '.skill-downloads/claude-skills-export-mm78nncj/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): TodoWrite, Glob, Read, Bash(echo:*), Bash(cat:*), Bash(find:*), Bash(ls:*)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/claude-skills-export-mm78nncj/SKILL.md' && test -s '.skill-downloads/claude-skills-export-mm78nncj/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/skill-export' && cp -R '.skill-downloads/claude-skills-export-mm78nncj' '.claude/skills/skill-export'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/claude-skills-export-mm78nncj'

openskills read 'claude-skills-export-mm78nncj'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/claude-skills-export-mm78nncj/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills