Automatically regenerates marketplace documentation files from Jinja2 templates and catalog data.
Works with
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, i
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondocumentation-updateExecute the skills CLI command in your project's root directory to begin installation:
Fetches documentation-update from geoffjay/claude-plugins and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate documentation-update. Access via /documentation-update in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
8
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
8
stars
This skill automatically regenerates documentation files in the docs/ directory by reading the marketplace catalog and applying Jinja2 templates.
Maintain synchronized documentation by:
Use this skill when:
This skill generates four main documentation files:
Complete reference of all agents across all plugins:
Catalog of all skills with progressive disclosure details:
Directory of all plugins in the marketplace:
Usage guide and command reference:
Templates are stored in assets/ using Jinja2 syntax:
assets/
├── agents.md.j2
├── agent-skills.md.j2
├── plugins.md.j2
└── usage.md.j2
All templates receive the following context:
{
"marketplace": {
"name": "marketplace-name",
"owner": {...},
"metadata": {...},
"plugins": [...]
},
"plugins_by_category": {
"category-name": [plugin1, plugin2, ...]
},
"all_agents": [
{
"plugin": "plugin-name",
"name": "agent-name",
"file": "agent-file.md",
"description": "...",
"model": "..."
}
],
"all_skills": [
{
"plugin": "plugin-name",
"name": "skill-name",
"path": "skill-path",
"description": "..."
}
],
"all_commands": [
{
"plugin": "plugin-name",
"name": "command-name",
"file": "command-file.md",
"description": "..."
}
],
"stats": {
"total_plugins": 10,
"total_agents": 25,
"total_commands": 15,
"total_skills": 30
}
}
The skill includes a Python script doc_generator.py that:
Loads marketplace.json
Scans Plugin Files
Prepares Template Context
Renders Templates
# Generate all documentation files
python doc_generator.py
# Generate specific file only
python doc_generator.py --file agents
# Dry run (show output without writing)
python doc_generator.py --dry-run
# Specify custom paths
python doc_generator.py \
--marketplace .claude-plugin/marketplace.json \
--templates plugins/claude-plugin/skills/documentation-update/assets \
--output docs
The /claude-plugin:create and /claude-plugin:update commands should invoke this skill automatically after marketplace updates:
1. Plugin operation completes (add/update/remove)
2. Marketplace.json is updated
3. Invoke documentation-update skill
4. Documentation files regenerated
5. Changes ready to commit
# After creating/updating plugin
print("Updating documentation...")
# Run doc generator
import subprocess
result = subprocess.run(
["python", "plugins/claude-plugin/skills/documentation-update/doc_generator.py"],
capture_output=True,
text=True
)
if result.returncode == 0:
print("✓ Documentation updated")
else:
print(f"❌ Documentation update failed: {result.stderr}")
# Agent Reference
This document lists all agents available across plugins in the marketplace.
{% for category, plugins in plugins_by_category.items() %}
## {{ category|title }}
{% for plugin in plugins %}
### {{ plugin.name }}
{{ plugin.description }}
**Agents:**
{% for agent in all_agents %}
{% if agent.plugin == plugin.name %}
- **{{ agent.name }}** (`{{ agent.model }}`)
- {{ agent.description }}
- File: `plugins/{{ plugin.name }}/agents/{{ agent.file }}`
{% endif %}
{% endfor %}
{% endfor %}
{% endfor %}
---
*Last updated: {{ now }}*
*Total agents: {{ stats.total_agents }}*
# Agent Skills Reference
This document catalogs all skills with progressive disclosure patterns.
{% for plugin in marketplace.plugins %}
## {{ plugin.name }}
{{ plugin.description }}
**Skills:**
{% for skill in all_skills %}
{% if skill.plugin == plugin.name %}
### {{<Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
sammcj/agentic-coding
yejinlei/pdf-ocr-skill
yejinlei/pdf-ocr-skill
kagurananaga/official-document-writing-skill
duc01226/easyplatform
steipete/clawdis
documentation-update is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: documentation-update is focused, and the summary matches what you get after install.
documentation-update is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
documentation-update fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: documentation-update is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: documentation-update is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added documentation-update from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for documentation-update matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: documentation-update is focused, and the summary matches what you get after install.
Keeps context tight: documentation-update is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 44