Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- Dygo DocumentationWrite or update dygo instructions, reference documentation, task descriptions, CLI help, metadata examples, or architecture notes. Use when documentation quality and contract accuracy are central to the task.Votes: 0GitHub stars: 16
- Documentapply documentation philosophy — explain why, not what. use for jsdocs, READMEs, inline comments.Votes: 0GitHub stars: 64
- Common DocumentationAssumption: each TODO represents a real follow-up rather than intentionally deferred work. 1. Inventory every TODO and assign an owner. 2. Create or link a ticket for each actionable item. 3. Rewrite comments using the required format: ```ts // TODO(alice): Explain why retry jitter is required to prevent the thundering herd. // Ticket: PROJ-123 ``` 4. Make comments explain `why`, not mechanics or obvious code behavior. 5. Convert public API comments to JSDoc, including `Args`, `Returns`, and ...Votes: 0GitHub stars: 549
- Common DocumentationWrite effective code comments, READMEs, and technical documentation following intent-first principles. Use when adding comments, writing docstrings, creating READMEs, or updating any documentation.Votes: 0GitHub stars: 549
- Common DocumentationWrite effective code comments, READMEs, and technical documentation following intent-first principles. Use when adding comments, writing docstrings, creating READMEs, or updating any documentation.Votes: 0GitHub stars: 549
- DocumentationThis skill should be used when the user mentions keywords related to documentation.Votes: 0GitHub stars: 5
- DocumentationTechnical documentation specialist. Maintains API docs, architecture documentation, developer guides, JSDoc, README updates, and Storybook stories. Use when creating or updating documentation, writing guides, documenting APIs, or maintaining project documentation. Triggers on "document", "documentation", "README", "API docs", "developer guide", "JSDoc", "architecture docs", "write docs".Votes: 0GitHub stars: 2
- Files<%= description %>Votes: 0GitHub stars: 76
- DocsGenerate and update living documentation — tech docs, user guides, philosophy overview. Composable building block for CLOSE and other skills.Votes: 0GitHub stars: 3
- Doc ThisCapture a code-viz finding, technique, decision or proposed feature in this repository's documentation system. Use when asked to document a discussion or preserve engineering knowledge.Votes: 0GitHub stars: 3
- Documentation As CodeJSDoc/docstrings on exports, README sync, API documentation, architecture decision records, and changelog entries.Votes: 0GitHub stars: 7
- What To DocumentSub-skill of fe-analyst: What to Document.Votes: 0GitHub stars: 17
- Skill DocumentationThis skill should be used when the user mentions keywords related to documentation.Votes: 0GitHub stars: 4
- DocumentationUse for PLANNING documentation with phased analysis (4 phases), gap identification, and structured knowledge modeling. Best for documentation audits, completeness analysis, and documentation strategy planning. NOT for writing actual docs (use tasks-documentation instead).Votes: 0GitHub stars: 18
- DocumentationCommunicating the intended behavior and context of code through clear documentation and comments, and sharing knowledge with the team.Votes: 0GitHub stars: 207
- Document FeatureGenerate technical and user documentation for a featureVotes: 0GitHub stars: 76
- Documentation GuideGuide documentation structure, content requirements, and project documentation best practices. Use when: creating README, documentation, docs folder, project setup, technical docs. Not for: generating docs mechanically from source — use /docgen; changelog entries — use /changelog. Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, ARCHITECTURE, API docs.Votes: 0GitHub stars: 75
- Documentation As CodeTreating documentation as a first-class engineering artifact with docs-in-repo workflows, automated generation, living documentation, testing, and continuous publishing pipelines. Use when the user asks about documentation as code, documentation as code best practices, or needs guidance on documentation as code implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.Votes: 0GitHub stars: 595
- Api DocumentationDocument interfaces so a caller can use them without reading the source.Votes: 0GitHub stars: 3
- DocumentTechnical documentation expert for creating clear, comprehensive documentation including API docs (OpenAPI), ADRs, system architecture docs, developer guides, and runbooks. Use when creating or improving technical documentation.Votes: 0GitHub stars: 2