source-command-unifi-mcp-update-docs
Skill294 starsChanged 18 days agoApache-2.0View on GitHub
Auto-generate and update API.md documentation from tool docstrings
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when the user asks to run the migrated source command unifi-mcp-update-docs.
- Distinctive: line 20
Import each module and extract tool functions
- Distinctive: line 31
Document available operations (list, read, subscribe)
- Distinctive: line 47
Read current API.md to preserve:
- Distinctive: line 84
Add new tools that aren't documented
- Distinctive: line 85
Remove documentation for deleted tools
- Distinctive: line 86
Update version number and last updated date
- Distinctive: line 89
Check for missing descriptions
- Distinctive: line 90
Verify all parameters are documented
- Distinctive: line 91
Ensure examples are valid JSON
- Distinctive: line 92
Check for broken internal links
- Distinctive: line 140
Never expose credentials in examples
- Distinctive: line 141
Use placeholder values for sensitive data
- Distinctive: line 143
Create backup before major changes
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
source-command-unifi-mcp-update-docs
Use this skill when the user asks to run the migrated source command unifi-mcp-update-docs.
Command Template
Automatically generate and update API.md documentation from tool docstrings and code.
This command scans all MCP tools and resources, extracts documentation from code, and updates API.md to ensure it stays in sync with the implementation.
Steps to execute:
- Discover all MCP tools:
- Scan
src/tools/directory for all tool modules - Import each module and extract tool functions
- Parse docstrings to get:
- Description
- Parameters with types and descriptions
- Return values
- Raises (errors)
- Example usage
- Scan
- Discover all MCP resources:
- Scan
src/resources/directory for resource handlers - Extract resource URI templates
- Document available operations (list, read, subscribe)
- Scan
- Categorize tools by functionality:
- Site Management
- Device Operations
- Client Management
- Network Configuration
- WiFi/WLAN Management
- Firewall & Security
- Port Forwarding
- DPI (Deep Packet Inspection)
- Zone-Based Firewall
- Traffic Flows
- Vouchers
- Webhooks
- Read current API.md to preserve:
- Overview and introduction sections
- Authentication details
- Rate limiting information
- Error handling guide
- Custom examples or notes
- Generate updated documentation:
- Table of contents with all categories
Tool documentation for each category:
### tool_name **Description:** Brief description **Parameters:** - `param1` (type): Description - `param2` (type, optional): Description **Returns:** Return value description **Example:** ```json { "tool": "tool_name", "arguments": { "param1": "value1" } }
- Update API.md:
- Preserve manual sections (overview, auth, errors)
- Replace tool documentation sections
- Add new tools that aren't documented
- Remove documentation for deleted tools
- Update version number and last updated date
- Validate documentation:
- Check for missing descriptions
- Verify all parameters are documented
- Ensure examples are valid JSON
- Check for broken internal links
Report back with:
- Number of tools documented
- Number of resources documented
- Tools added to documentation
- Tools removed from documentation
- Tools with incomplete documentation
- Summary of changes made
- Validation results
Example output:
Documentation Update Complete!
Tools Documented: 40
Resources Documented: 4
Changes:
✓ Added documentation for 2 new tools:
- create_traffic_flow_rule
- update_zbf_matrix
✓ Updated 5 tool descriptions
✓ Removed 1 deprecated tool: old_firewall_rule
⚠ Warning: 3 tools missing example usage:
- get_device_stats
- list_dpi_restrictions
- create_port_forward
Categories:
- Site Management: 3 tools
- Device Operations: 6 tools
- Client Management: 5 tools
- Network Configuration: 4 tools
- WiFi/WLAN: 4 tools
- Firewall & Security: 8 tools
- Zone-Based Firewall: 5 tools
- Traffic Flows: 3 tools
- Other: 2 tools
API.md updated successfully!
Last updated: 2025-01-15Safety checks:
- Never expose credentials in examples
- Use placeholder values for sensitive data
- Preserve existing manual documentation
- Create backup before major changes
In this repository52 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/fastmcp/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude/skills/fastmcp/CLAUDE.mdCLAUDE.md
- .cursor/rules/common-mistakes.mdcCursor rule
- .cursor/rules/core-principles.mdcCursor rule
- .cursor/rules/environment-setup.mdcCursor rule
- .cursor/rules/mcp-tools.mdcCursor rule
- .cursor/rules/project-context.mdcCursor rule
- .cursor/rules/README.mdCursor rule
- .cursor/rules/unifi-api.mdcCursor rule
- .cursor/rules/workflow.mdcCursor rule
- FastMCP DevelopmentSkill
- mcp-builderSkill
- source-command-build-dockerSkill
- source-command-check-depsSkill
- source-command-cleanSkill
- source-command-docsSkill
- source-command-formatSkill
- source-command-lintSkill
- source-command-prSkill
- source-command-securitySkill
- source-command-setupSkill
- source-command-testSkill
- source-command-unifi-api-docs-update-2Skill
- source-command-unifi-api-docs-updateSkill
- source-command-unifi-mcp-add-toolSkill
- source-command-unifi-mcp-release-prepSkill
- source-command-unifi-mcp-test-coverageSkill
- unifi-cloud-fleet-toolsSkill
- unifi-mcp-tool-builderSkill
- unifi-network-config-toolsSkill
- unifi-protect-toolsSkill
- unifi-security-toolsSkill
- FastMCP DevelopmentSkill
- mcp-builderSkill
- unifi-cloud-fleet-toolsSkill
- unifi-mcp-tool-builderSkill
- unifi-network-config-toolsSkill
- unifi-protect-toolsSkill
- unifi-security-toolsSkill
- unifiSkill
- unifi-channel-planningSkill
- unifi-cloud-fleet-toolsSkill
- unifi-devicesSkill
- unifi-mcp-tool-builderSkill
- unifi-network-config-toolsSkill
- unifi-networkSkill
- unifi-protect-toolsSkill
- unifi-securitySkill
- unifi-security-toolsSkill
- unifi-systemSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

