Documentation

Docs, README files, API references, tutorials, specs, and changelogs

skills in category: 13,978
pages available: 583

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 browser

Browse documentation skills

Showing 73–96 of 13,978 skills

Create Svg ImageACreate great looking SVG diagrams, images, and visualizations as hand-authored SVG following a bundled style guide. Use when the user says "svg", "create an svg image", "svg diagram", "draw this as svg", "architecture diagram in svg", or asks for a figure that needs pixel-level control over layout, color, or branding that Mermaid cannot express. For Mermaid-rendered diagrams use create-mermaid-visualization instead.documentationgobashVotes: 0GitHub stars: 10
Create SkillAAuthor a new skill by discovering similar skills, studying their strengths and weaknesses, and synthesizing the best single skill from them. Use when the user says /create-skill, "create a skill", "build a skill", "make a skill for X", or wants a new skill grounded in the best existing examples rather than written from scratch.documentationgobashVotes: 0GitHub stars: 10
Create ReadmeAGenerate a README.md for a project using a structured template with badges, feature lists, roadmap, and setup instructions.documentationpythongoVotes: 0GitHub stars: 10
Create QuestionARecord an open question with its context, who can answer it, what it blocks, and when the answer is needed.documentationdatabaseVotes: 0GitHub stars: 10
Create Placeholder IssueACreate a placeholder GitHub issue for a pending SDLC feature (one created without an issue, with a p-prefixed directory) and promote it to issue-driven form by renaming its directory and rewriting FEAT- cross-references. Use when the user says /create-placeholder-issue, wants to promote a pending feature, wants to back an existing SDLC feature with a GitHub issue, or wants to convert a p-prefixed feature directory into an issue-numbered one. For starting top-down from a feature request, use c...documentationgitVotes: 0GitHub stars: 10
Create Needs AssessmentAEvaluate whether a proposed feature addresses a genuine need before investing in feasibility or requirements, examining the problem, stakeholders, alternatives, and cost of inaction.documentationgogitVotes: 0GitHub stars: 10
Create LifecycleADocument how resources evolve over time and what causes them to change, covering states, transitions, invariants, and retention.documentationgoapiVotes: 0GitHub stars: 10
Create FeasibilityAAssess technical, financial, and operational viability of a feature before committing to requirements.documentationgogitVotes: 0GitHub stars: 10
Create Existing SolutionsASurvey existing solutions (libraries, products, internal code, standards, prior art) that address the requirements, evaluate their fit, and recommend whether to adopt, extend, or build.documentationgoapiVotes: 0GitHub stars: 10
Create DocumentationACreate documentation for a feature or component following the Divio documentation framework (tutorials, how-to guides, reference, explanation).documentationgitapiVotes: 0GitHub stars: 10
Check Issue StatusADetermine whether a GitHub issue is already addressed in the codebase by extracting its requested behavior and verifying it against the code. Works for feature requests and bug reports in any format, with or without formal acceptance criteria. Use before starting work on an issue, or to triage stale issues, to avoid implementing or fixing something that is already present. Triggers on "is this issue already done", "is this already implemented", "is this bug already fixed", "check issue status...documentationgobashVotes: 0GitHub stars: 10
Check DuplicatesACheck a GitHub issue for duplicate issues and existing fix PRs before investing effort.documentationbashgitVotes: 0GitHub stars: 10
Analyze Test CoverageAAnalyze a set of code changes (diff or files) and produce a structured test coverage report with three parts: introduced tests, change coverage, and uncovered code. Called by review-pr-full as the first step of its review chain (before validate-pr, verify-pr, and review-pr), and delegated to by review-pr, review-implementation, and verify-pr; can also be invoked directly on any diff.documentationgobashVotes: 0GitHub stars: 10
Yaml JazzAYAML is sheet music. The LLM is the jazz musician. Comments are soul.documentationpythongoVotes: 0GitHub stars: 56
VisualizerAI see what you describe. Let me show it to others.documentationgobashVotes: 0GitHub stars: 56
TiesAA manifest file type and authoring discipline for making a directory tree legible to an orchestrator without opening it. TIES.yml carries a semantic pyramid from emoji through label, name, one-paragraph definition, description and body, plus synonyms for name resolution, typed links, costs and read conditions for children, and foreign schemas attached as isolated organelles. Descends from HyperTIES (HCIL, 1988), whose articles were required to carry a previewable definition. Use when deciding...documentationpythongoVotes: 0GitHub stars: 56
Thoughtful CommitmentAGit commits that capture context and intentdocumentationpythongoVotes: 0GitHub stars: 56
SummarizeACompress without losing truth. Backlink to sources.documentationgodocumentationVotes: 0GitHub stars: 56
Soul ChatAEverything is alive. Everything can speak.documentationdocumentationVotes: 0GitHub stars: 56
Sniffable PythonAHow to mark and sniff Python (and other files) at multiple depths. Moo and other tools use this convention. ---documentationpythongoVotes: 0GitHub stars: 56
SkillAA skill is documentation that learned to do things.documentationpythonrustVotes: 0GitHub stars: 56
Simulator EffectAImplication beats simulation — imagination renders (Will Wright)documentationgoangularVotes: 0GitHub stars: 56
Session LogAHuman-readable markdown session logs for characters and adventures.documentationgorailsVotes: 0GitHub stars: 56
Plain TextAText files are forever. No lock-in. No corruption. No transformation.documentationpythonbashVotes: 0GitHub stars: 56