Loading...
Loading...
Found 21 Skills
Provides templates, standards, and best practices for writing clear, comprehensive technical documentation
Write meaningful documentation that explains why not what; focus on complex business logic and self-documenting code
Maintain a clear and informative changelog for software releases. Use when documenting version changes, tracking features, or communicating updates to users. Handles semantic versioning, changelog formats, and release notes.
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
Best practices for documenting APIs and code interfaces, eliminating redundant documentation guidance per agent.
Evaluate a README file text, score it out of 100, and provide specific, actionable improvement suggestions.
Document architectural decisions. Use when making significant technical decisions that should be recorded. Covers ADR format and decision documentation.
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.
Use when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI writing patterns that signal inauthenticity
Master markdown formatting, GitHub Flavored Markdown, README files, and documentation formatting. Use when writing markdown docs, READMEs, or formatting documentation.
Plain text formatting that's readable raw AND rendered
Expert knowledge of research grant compliance requirements, deliverables tracking, and funder expectations. Use when reviewing work against grant specifications, preparing progress reports, or ensuring alignment with funding requirements from NSF, NIH, EU, and other agencies.