A template skill that turns 600+ word drafts into a magazine-style long-form article page.
Spins up (or reuses) a self-contained local web gallery for browsing images generated by Codex.
Stand up a Technical Advisory Board and run repeatable developer discovery interviews that feed your positioning, roadmap, and homepage copy.
A GTM skill that sharpens a vague "for developers" target into a specific ICP with exclusions plus a map of every persona in the sale.
Analyzes your recent Claude Code chat history to surface coding patterns and skill gaps, then delivers a personalized growth report with curated resources to Slack.
A step-by-step skill for listing tables, describing columns and types, and mapping foreign-key relationships in a database.
Turns your Git history into a categorized CHANGELOG.md with a Semantic Versioning bump suggestion.
Turns a one-line topic, link, or product blurb into a confirmable creative brief covering audience, core claim, evidence, and per-platform angles.
Saves content milestones to files with version rules, path verification, publish packages and a content registry.
Turns raw git commit history into polished, customer-friendly changelogs and release notes.
An output-style skill that reshapes Claude's replies into a rundown brief: TL;DR, status checklist, and numbered next moves.
Compresses a document, thread, transcript, or pasted text into a scannable TL;DR briefing.
Writes a design manifesto first, then expresses it as a museum-grade poster or artwork in PDF/PNG.
Turns Claude into a policy-aware MATLAB tutor that coaches with a hint ladder instead of handing over graded homework solutions.
A one-shot quick-reference card listing every Chisle command, rule and safety boundary.
Defines how the agent should interpret and act on blocking warnings from the comment-checker hook that runs after file edits.
A routing skill that points first-time users to NanoClaw's single end-to-end install script.
A one-line skill that asks Claude to re-explain anything technical as the who, what, where, why, and when in plain English.
An 8-phase, approval-gated pair programming workflow: understand requirements, write a spec, implement in vertical slices, review, then keep spec and code in sync.
A one-shot reference card listing every genshijin mode, sub-skill trigger and off-switch for the ultra-terse Japanese output style.