All categories
Documentation
Docs, README files, API references, tutorials, specs, and changelogs
- 15,624
- 651
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse documentation skills
Showing 10,465–10,488 of 15,624 skills
- Planning And Task BreakdownDecompose specs into small, verifiable tasks with acceptance criteria and dependency ordering. Use when you have a spec and need implementable units.Votes: 0GitHub stars: 8
- Docs CanvasRender a documentation-style Cursor Canvas that organizes architecture notes, API references, walkthroughs, and how-tos into a navigable layout with sections, tables of contents, and cross-references. Use when the user asks for a docs canvas, documentation overview, architecture walkthrough, API reference page, or wants to render structured documentation as an interactive canvas.Votes: 0GitHub stars: 8
- Doc ReviewStructured document review for structure, clarity, and technical accuracy. Use for \"review this doc\", feedback, critique, or /doc-review.Votes: 0GitHub stars: 8
- Text CleanupComprehensive patterns and techniques for removing AI-generated verbosity and slopVotes: 0GitHub stars: 8
- Text CleanupComprehensive patterns and techniques for removing AI-generated verbosity and slopVotes: 0GitHub stars: 8
- Text CleanupComprehensive patterns and techniques for removing AI-generated verbosity and slopVotes: 0GitHub stars: 8
- Source Driven DevelopmentGround every framework decision in official documentation. Use when you want authoritative, source-cited code for any framework or library.Votes: 0GitHub stars: 8
- Pr Review CanvasGenerate an interactive PR review walkthrough as an HTML page. Fetches PR data via gh API, categorizes files into core vs mechanical changes, adds reviewer annotations, and renders diffs with moved-code detection. Use when the user pastes a GitHub PR URL and asks for a review, walkthrough, or summary, or says \\\"review this PR\\\".Votes: 0GitHub stars: 8
- Planning And Task BreakdownDecompose specs into small, verifiable tasks with acceptance criteria and dependency ordering. Use when you have a spec and need implementable units.Votes: 0GitHub stars: 8
- Multimodal Corpus IngestionNormalize mixed inputs like code, docs, PDFs, screenshots, diagrams, audio, and transcripts into a structured corpus. Use when the task depends on combining multiple artifact types before analysis or retrieval.Votes: 0GitHub stars: 8
- Knowledge ArchitectureBuild a static-first knowledge architecture using file-backed domain maps, rules, hypotheses, and durable references. Use for knowledge architecture, learning systems, decision context, and long-lived team memory without runtime memory tooling.Votes: 0GitHub stars: 8
- Docs CanvasRender a documentation-style Cursor Canvas that organizes architecture notes, API references, walkthroughs, and how-tos into a navigable layout with sections, tables of contents, and cross-references. Use when the user asks for a docs canvas, documentation overview, architecture walkthrough, API reference page, or wants to render structured documentation as an interactive canvas.Votes: 0GitHub stars: 8
- Doc ReviewStructured document review for structure, clarity, and technical accuracy. Use for \"review this doc\", feedback, critique, or /doc-review.Votes: 0GitHub stars: 8
- ReweaveBackward pass over existing knowledge when new information arrives. Finds older content that should be updated, corrected, or enriched in light of new data. Detects staleness, generates update suggestions, and optionally applies them. Triggers on: "reweave", "update stale", "backward pass", "refresh context"Votes: 0GitHub stars: 229
- Spine ReconBackend reconnaissance — map all routes, middleware, models, dependencies, auth, and assess code quality for project takeover. Use when asked to "understand this backend", "map the API", or "assess code quality".Votes: 0GitHub stars: 71
- Wire ReconAudit existing design documentation — find gaps in specs, missing states, and handoff debt. Use when asked to "audit our design docs", "find missing component states", or "assess handoff debt".Votes: 0GitHub stars: 71
- Guide WriteWrite API reference documentation for an endpoint or SDK method. Use when asked to "document this endpoint", "write API reference docs", or "document this SDK method".Votes: 0GitHub stars: 71
- Guide ReconSurvey documentation coverage across an API or SDK — find undocumented endpoints and gaps. Use when asked "what is undocumented", "find docs coverage gaps", or "survey our API documentation".Votes: 0GitHub stars: 71
- Guide AuditAudit existing API documentation for completeness, accuracy, and developer experience. Use when asked to "audit our API docs", "are our docs accurate", or "review documentation quality".Votes: 0GitHub stars: 71
- AtlasKnowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports. Use when asked to "write an ADR", "map the architecture", "document this decision", "onboarding docs", or "what changed".Votes: 0GitHub stars: 71
- Atlas ReconDocumentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".Votes: 0GitHub stars: 71
- Atlas PresentGenerate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".Votes: 0GitHub stars: 71
- Atlas OnboardGenerate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".Votes: 0GitHub stars: 71
- Atlas ChangelogMaintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".Votes: 0GitHub stars: 71