Comments
Code comments and annotations
wp-block-markup
by bph
Convert Markdown files to WordPress block markup (Gutenberg serialized HTML). Use whenever the user wants to produce content that can be pasted into the WordPress Code Editor or used in block theme HTML templates. Also use for the reverse direction (block markup to markdown).
use-the-index-luke
by wottpal
Postgres query and index optimization workflow based on use-the-index-luke principles. Use for EXPLAIN analysis, index design, predicate rewrites, joins, sorting, and pagination tuning.
backlog-state
by zheref
Render the current backlog as one gate-oriented table — every open issue with its associated PRs, for one repo or all of them, showing the human gate each item sits at, what it needs next, and which session is driving it. Use when the maintainer asks what the state is, what needs them, what is at a gate, or invokes $backlog-state <repo all>@<G1 G1-M G2 G3 G4 G5 all>. Strictly read-only — it never labels, merges, pushes, comments or opens anything.
finality
by nitedani
"The finality pass, for code that has drifted through many patches, or a design thread that has drifted over many rounds: map, imagine, hunt phantom fixes, converge, and Owner-Safe closure."
SKILL: harn-forgejo-connector
by burin-labs
60 req/min token bucket, or rate_limit = { disabled = true } to bypass it.
slim-review
by sirmaelstrom
"Run the slim PR-review loop — two external reviewers (GPT-6 Sol and Astra, plan-covered) at a PR boundary, findings posted as line-anchored GitHub review comments, then confirm or refute each and reply. Trigger on '/slim-review', 'slim review', 'review this PR before merge', or at any PR boundary in a burn-down. The LIGHT tier: two lenses, no synthesis. NOT for converging a reviewed PR (babysit), in-session multi-reviewer passes ('/review'), or complex PRs (review-council)."
security-reviewer
by magfrump
Review code changes for security vulnerabilities using structured cognitive moves that go beyond what static analysis tools catch. This is not a linter — it focuses on design-level security flaws, trust boundary violations, implicit assumptions about input safety, and patterns that create exploitable conditions. Produces a structured Markdown critique of code diffs. Use this skill when the user asks to "review for security", "check for vulnerabilities", "security audit this PR", "what could an attacker do with this", or "is this safe". Also trigger when code touches authentication, authorization, input handling, cryptography, file I/O, network calls, or serialization. Also trigger when the diff includes changes to dependency manifests (package.json, requirements.txt, go.mod, Cargo.toml, pyproject.toml, Gemfile, pom.xml, build.gradle, etc.) or their lockfiles. 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.
llms-build
by The-Interdependency
Self-declaring LLM instructions file (llms.txt) built on msdmd. Modules or central files declare LLMS blocks with project overview, key definitions, architecture summary, and agent usage rules. A runner aggregates them into a standardized root llms.txt and surfaces drift/gaps. Load this when creating, updating, or maintaining llms.txt for any repo consumed by LLMs or agents.
librarian
by broskmenmi
Persist approved playlist decisions in GitHub by maintaining the canonical ledger, discoveries log, rejected list, revisit queue, listener-feedback discussions, structural notes, and journey-map annotations. Use only after audit approval.
contract-review
by zqm0779
"Contract review skill that adds comment-based issue annotations without changing original text. Enforces a three-layer review (basic, business, legal), writes structured comments (issue type, risk reason, revision suggestion) with risk level encoded via reviewer name, and generates a contract summary, consolidated opinion, and Mermaid business flowchart (with rendered image). Output language must follow the contract’s language."
github-issue-post
by woahwhattheheck
Post to Commons through the open GitHub issue road. Use when issue creation is a reachable road; Pages or ntfy availability is irrelevant.
worktrees-hives Skill
by rmems
Defense in depth: all three layers enforce the same rules. A failure in one layer is caught by another.
implement-isolation
by SjB
"Implement a piece of work based on a spec or set of tickets in isolation."
rewrite
by jimrand
This skill should be used when the user asks to "rewrite my resume", "fix my resume", "humanize my resume", "make my resume sound human", "clean up my resume bullets", "reword my resume", or wants AI-sounding text in their resume rewritten with annotations explaining each change. Works for all resume and CV types: standard US, federal, academic, legal, medical, consulting, tech, executive, military transition, education, nonprofit, trades, creative, investment banking, and EU/Europass formats. Entry-level through executive.
CLAUDE_SKILL_API_QE_PLATFORM.md
by carthikl
The k6 layer is built into this skill. Use Prompt 8 as written. Key reminder when adapting: cron schedule in performance-stress.yml must be a literal string ('PERF_SCHEDULE'), not a GitHub Actions expression — expressions are not evaluated in on.schedule.cron. Threshold syntax must use p(95) not p95 — the shorthand form throws a runtime parse error in k6.
tp-bd-factsheet-filler
by Harshiv15
Extracts company information from an Annual Report (AR)/financial statements PDF - and, when the AR doesn't have it, the company's website/LinkedIn - to populate a TP Business Development Fact Sheet Excel template (headquarters, business description, standalone/consolidated financials, AE revenue split, shareholding, related-party transactions, litigation, website/LinkedIn). Use whenever the user provides an AR/financial statements and a BD Fact Sheet template and asks to fill, draft, or prepare a BD, fact sheet, or company profile for TP purposes. Always flag extracted figures for human review - never treat output as final.
last30days
by louayham6956
"Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web."
playwright-cli
by MarBlanco
Automate browser interactions, test web pages and work with Playwright tests.
odt
by sungkhum
"OpenDocument Text (.odt) creation, editing, and analysis. Supports tracked changes, styles, annotations, and language/locale handling. Use for: creating new ODT documents, editing existing ODT content, working with tracked changes (redlining), adding comments/annotations, or extracting/analyzing ODT content."
walk-pr-review-findings
by Hallmanac
Walk a pr-review task's findings report (or a mention follow-up's addendum) with the owner, finding by finding, and post exactly what they direct — a batched GitHub review, a plain comment, or a reply to a tagged comment — only on their explicit go. Use when a pr-review task (h9k task add --type pr-review --from-pr, or one auto-pr-review minted from a review request or a GitHub mention) is parked NeedsHuman with a report or addendum.
clarify
by paulbryantbaker-art
Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.
bbc-skill
by Analliseamicable382
Fetch Bilibili (哔哩哔哩) video comments for UP主 self-analysis. Use when the user asks to collect, download, export, or analyze comments on a Bilibili video (BV号 / URL / UID). Produces JSONL + summary.json suitable for further Claude Code analysis (sentiment, keywords, audience trends). Read-only; does not post/edit/delete.
documentation-and-adrs
by MGallo-Code
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
worker-scoped-session
by simnova
Run delegated headless/--yolo workers with OPENCLINXR_WORKER=1 so SessionStart docs hygiene and CEO coord hooks NO-OP. Use when spawning worktree workers, deepseek execute sessions, or any non-CEO agent that must not mutate registries/PROJECT_STATUS.