documentation-update
Automatically regenerates marketplace documentation files from Jinja2 templates and catalog data.
- Generates four synchronized documentation files (agents.md, agent-skills.md, plugins.md, usage.md) by reading marketplace.json and plugin metadata
- Provides Python script with command-line options for full generation, selective file output, dry-run mode, and custom path configuration
- Includes pre-built Jinja2 templates with access to comprehensive context: plugins organized by category, indexed agents and skills, component statistics, and marketplace metadata
- Designed for integration with plugin create/update commands to keep documentation in sync whenever marketplace changes occur
Documentation Update Skill
This skill automatically regenerates documentation files in the docs/ directory by reading the marketplace catalog and applying Jinja2 templates.
Purpose
Maintain synchronized documentation by:
- Generating agent reference documentation
- Creating skill catalog documentation
- Building plugin directory
- Updating usage guides
- Ensuring consistency across all docs
When to Use
Use this skill when:
More from geoffjay/claude-plugins
git-troubleshooting
Git troubleshooting techniques including recovering lost commits, fixing merge conflicts, resolving detached HEAD, and diagnosing repository issues. Use when user encounters git errors or needs to recover from mistakes.
295git-advanced
Advanced git operations including complex rebase strategies, interactive staging, commit surgery, and history manipulation. Use when user needs to perform complex git operations like rewriting history or advanced merging.
281tokio-patterns
Common Tokio patterns and idioms for async programming. Use when implementing worker pools, request-response patterns, pub/sub, timeouts, retries, or graceful shutdown.
73tokio-concurrency
Advanced concurrency patterns for Tokio including fan-out/fan-in, pipeline processing, rate limiting, and coordinated shutdown. Use when building high-concurrency async systems.
49git-repository
Repository management strategies including branch strategies (Git Flow, GitHub Flow, trunk-based), monorepo patterns, submodules, and repository organization. Use when user needs guidance on repository structure or branching strategies.
43tokio-troubleshooting
Debugging and troubleshooting Tokio applications using tokio-console, detecting deadlocks, memory leaks, and performance issues. Use when diagnosing async runtime problems.
40