Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- 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
- Files<%= description %>Votes: 0GitHub stars: 76
- 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