mcpbeat

Docs Tools

pulumi/docs-tools

List available documentation tools and commands.

1k tokens
context cost
the whole folder, loaded on every use
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
178
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/pulumi/docs --skill docs-tools

What comes with it

2 581 bytes besides the instruction
scripts/scrape-metadata.py

The instruction itself

4 sections, as written by the author

Documentation Tools

Use this when: You want to see all available Claude Code commands for the Pulumi Docs repository.


Implementation

Step 1: Scrape command metadata

Run the metadata scraper:

python3 .claude/commands/docs-tools/scripts/scrape-metadata.py

The script outputs a JSON array:

[{"command": "/name", "description": "..."}]

IMPORTANT: ONLY include commands found by the script. Do NOT include any commands from the system reminder or global Claude Code skills list (such as /keybindings-help).

Step 2: Render categorized display

Parse the JSON and display grouped by category. Use the following format:

# Documentation Tools & Commands

Available Claude Code commands for the Pulumi Docs repository:

[grouped list of commands]

---

Type any command above (e.g., `/new-doc`) to use it, or just tell me what you need help with!

Group commands into categories such as:

  • Content Creation (creating docs/posts)
  • Review & Quality (reviewing/improving content, SEO)
  • File Operations (moving/modifying files)
  • Issue Management (analyzing/planning fixes)
  • Repository Management (dashboards/status)
  • Discovery (tools for finding other tools)

Add additional categories as needed based on the commands found. Assign an appropriate emoji to each category header. Format each entry as:

- /command-name - description

Use color, formatting, and emojis to enhance readability.

How to use it

Copy the folder

Take pulumi/docs-tools from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.