Loading...
Loading...
Found 1,415 Skills
Parses interface/API information from files or directories and generates OpenAPI-compliant documentation with timestamps
Intelligent skill suggestion engine that analyzes user intent and project context to recommend appropriate documentation skills
Produce clear, accurate, and maintainable technical documentation for APIs, systems, and user workflows.
Comprehensive documentation quality system combining automated validation with ToolUniverse-specific auditing. Detects outdated commands, circular navigation, inconsistent terminology, auto-generated file conflicts, broken links, and structural problems. Use when reviewing documentation, before releases, after refactoring, or when user asks to audit, optimize, or improve documentation quality.
Auto-generate Claude skills from documentation URLs using Firecrawl agent. Use when user wants to create a skill from docs, API references, or tool homepages. Asks up to 3 clarifying questions before deep extraction. Supports topic focus (e.g., "only auth endpoints") and outputs to local .claude/skills/ by default.
Generate and update structured documentation from project data sources. Supports initial generation and modification of existing documents. Use this skill when users request creating, generating, updating, or modifying documentation.
Update the API reference documentation by downloading the latest OpenAPI spec from production and regenerating the Docusaurus API docs
Publish documentation generated by doc-smith-create to DocSmith Cloud and obtain an online preview URL. Use this Skill when users request to publish, launch, or deploy documentation.
Enforces strict use of Chinese in all interactions, code comments, and documentation generation, in compliance with advanced technical writing standards. Enforces strict adherence to the Chinese language in all interactions, code comments, and documentation with high-quality technical writing standards.
Guide for setup Context7 MCP server to load documentation for specific technologies.
Use when documenting public APIs. Use when writing library code. Use when using JSDoc-style comments. Use when generating documentation. Use when explaining complex types.
Initialize projects with agentic coding structure. Use when setting up a new project, adding AI agent support to existing project, or when user says "init", "initialize", "setup project", or "scaffold". Creates AGENTS folder, documentation templates, and _NOTES scratch space.