Registry Tools

VerifiedSafe

Lists all available commands for the Pulumi Registry, grouped by category.

Sby Skills Guide Bot
ProductivityBeginner
7/30/2026
Claude Code
#slash-commands#discovery#help#pulumi-registry#workflow

Recommended for

Automated summary

This command lists all Claude Code commands available in the Pulumi Registry repository, grouped by category.

Strengths

  • Prints commands in a terminal-friendly layout grouped by theme (review, package management, shipping, issues, repo health)
  • Auto-discovers additional commands through scrape-metadata.py and places them under an "Other" category
  • Acts as a single entry point for discovering the repository's tooling without reading the docs

Limitations

  • The main list is hardcoded in the file and must be updated by hand when new commands are added
  • Depends on a Python script living at a fixed path (.claude/commands/registry-tools/scripts/scrape-metadata.py)
  • Only works in a repository set up with these commands and with Claude Code slash-command support
When to use it

Reach for it when you are new to the Pulumi Registry repo or cannot remember which commands exist.

When not to use it

Do not use it to perform real work: it only displays the command list and runs no review or validation itself.

Security analysis

Safe
Quality score85/100

The skill only instructs running a local Python metadata scraper to list available commands for the Pulumi Registry. It does not involve destructive operations, network exfiltration, secret handling, or disabling safety mechanisms. The command is a standard repository utility and poses no meaningful execution risk.

No concerns found

How this analysis is made

Examples

Run the command
/registry-tools
Discover repo commands
What Claude Code commands are available in this Pulumi Registry repository? Group them by category.
Find a command for a task
Is there a command here for validating a provider package YAML, and what other registry tools exist?

description: List available registry tools and commands. user-invocable: true

Registry Tools

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

Lists all available commands grouped by category.


Usage

/registry-tools


Implementation

  1. Run the metadata scraper to discover all available commands:

    python3 .claude/commands/registry-tools/scripts/scrape-metadata.py
    
  2. Parse the JSON output and group commands by category:

    Review & Quality:

    • /registry-review - Review changes for quality
    • /pr-review <PR_NUMBER> - Full PR review workflow with approve/merge/close
    • /validate-package [name] - Validate provider package YAML

    Package Management:

    • /new-package - Guided workflow to add a new provider package
    • /validate-package [name] - Validate provider package YAML

    Shipping & PRs:

    • /shipit - Commit, push, and create PR with quality checks

    Issue Management:

    • /fix-issue <issue-number> - Analyze issue and create implementation plan

    Repository Health:

    • /dashboard [mode] - Repository status, PRs, issues, CI health

    Discovery:

    • /registry-tools - This command (list all available tools)
  3. Display the grouped list in a terminal-friendly format:

    ════════════════════════════════════════════════════════════════════════════════
    📦 PULUMI REGISTRY - Available Commands
    ════════════════════════════════════════════════════════════════════════════════
    
    Review & Quality:
      /registry-review        Review changes for quality before committing
      /pr-review <PR>         Review and approve/merge pull requests
      /validate-package       Validate provider package YAML
    
    Package Management:
      /new-package            Add a new provider package to the registry
    
    Shipping & PRs:
      /shipit                 Commit, push, and create PR with quality checks
    
    Issue Management:
      /fix-issue <issue>      Analyze issue and create implementation plan
    
    Repository Health:
      /dashboard [mode]       Repository status and health metrics
    
    Discovery:
      /registry-tools         List all available commands (this command)
    
    ════════════════════════════════════════════════════════════════════════════════
    Tip: Run any command by typing it in the chat (e.g., /dashboard)
    
  4. If the scraper discovers additional commands not in the hardcoded list above, include them in an "Other" category.

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/registry-tools-ms71b3x0/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/registry-tools-ms71b3x0' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/registry-tools-ms71b3x0/download' --output '.skill-downloads/registry-tools-ms71b3x0/SKILL.md.part' && mv '.skill-downloads/registry-tools-ms71b3x0/SKILL.md.part' '.skill-downloads/registry-tools-ms71b3x0/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.

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

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

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/registry-tools-ms71b3x0/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