Loading...
Loading...
Found 20 Skills
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
Review and improve documentation with parallel evaluation and iterative improvement loop.
Reviews and proofreads blog posts, articles, documentation, communications, emails, and any other write-ups to improve conciseness, legibility, clarity, and tone. Fixes typos, grammar issues, redundancies, run-on sentences, and punctuation errors. Use when the user asks to proofread, review, edit, or improve a piece of writing, or when they share text and ask for feedback, corrections, or a revised version.
Detect and flag AI-generated content markers in documentation and prose. Use when reviewing documentation for AI markers, cleaning up LLM-generated content, or auditing prose quality. Do not use when generating new content (use doc-generator) or learning writing styles (use style-learner).
Audit claude-skills repository documentation with systematic 9-phase review: standards compliance, official docs verification via Context7/WebFetch, code examples accuracy, cross-file consistency, and version drift detection. Auto-fixes unambiguous issues with severity classification. Use when: investigating skill issues, major package updates detected (e.g., v1.x → v2.x), skill not verified >90 days, before marketplace submission, or troubleshooting outdated API patterns, contradictory examples, broken links, version drift.
Evidence-first research, architecture discovery, vendor documentation review, benchmark reading, and unknown-system analysis.
Core technical documentation writing principles for voice, tone, structure, and LLM-friendly patterns. Use when writing or reviewing any documentation.
Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase