Comments
Code comments and annotations
context-reset
by JeriC4o
"Handoff protocol for large tasks (≥5 subtasks) AND compaction-recovery re-entry. Prevents context degradation and compaction-related quality loss."
ddia-streaming-with-kinesis
by odewahn
Interactive modular learning guide for stream processing concepts from DDIA Chapter 11. Use when the user wants to learn about stream processing, messaging systems, event-driven architectures, Kafka, or needs help with the DDIA Chapter 11 curriculum. Provides 15 bite-sized modules (~45 min each) with flexible prerequisites, hands-on AWS Kinesis examples, progress tracking, and Socratic teaching. Topics include streams vs batch, messaging patterns, partitioned logs, databases & streams, and stream processing fundamentals.
conventional-commits
by devinschumacher
Generates git commit messages following Conventional Commits 1.0.0 specification with semantic types (feat, fix, etc.), optional scope, and breaking change annotations. Use when committing code changes or creating commit messages.
save-url-kb
by hraness
Capture public or signed-in web content into a local Markdown knowledge base as an auditable source bundle with local assets. Use when the user asks to clip, save, scrape, or archive an article, social post or thread, GitHub or Discourse discussion, feed, inbox, private document, WhatsApp conversation, YouTube page, or another page already visible in their browser. Supports URL capture, the current signed-in tab, temporary browser-profile snapshots, saved HTML, media, evidence, honest completeness, and knowledge-base linking.
fork-contributor-leaderboard
by Atrium-Hermes
Weekly ranking of developers contributing to the fork fleet and back upstream
pr-state
by zheref
Report one PR's CON-32 readiness as the deterministic gate's verdict, quoted, with the conjunct-by-conjunct reason it passed or failed. Use when the maintainer invokes hatsu:pr-state #<N>, or asks whether a PR is ready, G2-ready, G4-ready or mergeable. Strictly read-only — it never labels, merges, pushes, comments or opens anything. A readiness claim made any other way is not a readiness claim.
performance-reviewer
by magfrump
Review code changes for performance problems using structured cognitive moves that go beyond what profilers and benchmarks catch. This is not about micro-optimization — it focuses on algorithmic complexity issues, hidden N+1 patterns, unnecessary work in hot paths, resource lifecycle problems, and scaling bottlenecks that only appear under load. Produces a structured Markdown critique of code diffs. Use this skill when the user asks to "review for performance", "perf review", "will this scale", "check for bottlenecks", "is this efficient", "what happens under load", "find the N+1", or "hot path analysis". Also trigger when code touches database queries, ORM calls, loops over collections, caching, pagination, batch operations, request handling paths, background workers, or any code in a measured hot path. This is the performance critic — for security flaws use security-reviewer; for interface design use api-consistency-reviewer; for module/dependency structure use architecture-review. NOTE: This skill can be invoked standalone or by a code-review orchestrator. If a code-fact-check report is provided, use it as your foundation for understanding what the code actually does and do not re-verify documented behavior.
wiki-switch
by prateek
Switch between multiple Obsidian wiki vault profiles. Use this skill when the user says "/wiki-switch NAME", "switch to my work wiki", "switch vault", "change wiki", "which wiki am I on", "list my wikis", "show my vaults", "create a new vault config", or "add a new wiki profile". The skill manages named config files at <global config dir>/config.NAME and activates one by symlinking it to <global config dir>/config.
fastapi-patterns
by cuba6112
Advanced FastAPI patterns including hierarchical dependency injection, background task management, and type-safe dependency annotation. Triggers: fastapi, dependency-injection, background-tasks, annotated-dependency, permission-chain.
gstack
by deveshkumars
Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots.
docs
by loganmancuso-scout
Documentation writing standards and conventions. Covers inline code comments, JSDoc/docstrings, API docs, READMEs, changelogs, and markdown files. Load this skill when writing or updating any documentation — in code or in markdown.
adk-code-review-loop
by jiying2007
独立代码审查与反馈修复闭环，覆盖发现分级、真实性核验、修复验证和复审
Cloudflare Workers Runtime APIs & Best Practices
by hexamh
Last updated: May 2025 — based on official Cloudflare Workers documentation.
github-resource-access
by handlename
Use when accessing GitHub resources such as issues, PRs, repositories, or secrets. Enforces "use the gh CLI; reads are free, writes require explicit instruction".
language-style-guide
by BrotherPeng
强制在所有交互、代码注释和文档生成中严格使用中文，并遵循高级技术写作规范。Enforces strict adherence to Chinese language in all interactions, code comments, and documentation with high-quality technical writing standards.
handwriting-to-latex
by Amylalcoholfinance405
Use this skill whenever the user uploads handwritten notes, problem sets, scanned documents, or iPad handwriting PDFs and wants them converted into LaTeX format. Trigger phrases include: convert to LaTeX, transcribe to tex, handwriting to LaTeX, LaTeX this, typeset my notes, put this in Overleaf format. Activate proactively whenever the user uploads an image or PDF containing mathematical expressions or handwritten academic content.
Cite Requirements
by jankneumann
work plan this skill executes Track A of.
zora-cli
by sigma99000
The agent's full interface to Zora — the onchain social platform on Base — through the Zora CLI (npx @zoralabs/cli), for both first-time setup AND everyday use. Use it to stand up an identity (Zora profile, Coinbase Smart Wallet, creator coin, first post), and just as much to act on Zora afterward: buy and sell creator coins and post coins, browse what's trending, look up a coin's price, holders, or trades, check balances and holdings, send ETH or tokens, and read and reply to DMs. Trigger on anything Zora-on-Base — setup phrasings like "set me up on Zora", "make me a Zora account", "become an agent on Zora", but equally everyday ones like "buy this coin on Zora", "what's trending on Zora", "check my Zora balance", "look up on Zora", "sell half my Zora position", or "reply to my Zora DMs" — even when the user never names the CLI.
past-failures
by nitedani
"When a rule failed or the user names a failure: the table of past failures and the rule that covers each."
refactor
by CatPope
Behavior-preserving refactoring with a read-first, plan-approve, one-chunk-at-a-time workflow. Use for extracting god files/components, renaming at scale, splitting large services, and untangling legacy code.
codebase-inspection
by niyatna
"Inspect codebases w/ pygount: LOC, languages, ratios."
to-tickets
by surreptakos
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
backlog-synthesis
by zheref
Reconcile a long backlog into a smaller one — group open issues that target the same rule/clause, machinery file or root cause, propose a consolidation plan as an iterable Artifact, and on approval file one consolidated issue, attach the originals as sub-issues and close them with a reference. Use when the maintainer invokes /backlog-synthesis <critical high medium low all> [<repo>], or asks to consolidate, synthesize, dedupe or shrink a backlog.
docx
by saajunaid
"Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"