claude-skills

In the author's own words, from each skill's SKILL.md — showing the first 30 of 57 files.

• ai-surface-discipline

  Apply input minimisation, output discipline, and a human-in-the-loop gate to every surface that sends data to an LLM. Triggers when building or editing any send-to-LLM path: an Edge Function calling a model, a draft-commentary or summary generator, an auto-resolver, a cash-allocation suggestion, a classification call, or any new AI-assist feature, especially in a RICS or UK GDPR regulated context.

  ai-surface-discipline/SKILL.md on GitHub (opens in a new tab)

• blast-radius-grep

  The unit of change is the action or the fact, never the named list of places someone handed you. Before shipping a gate, constraint, rename, drop, or a correction to any duplicated, mirrored, or denormalised value, grep the whole repo — app, tests, seeds, scripts, open branches, and the built or rendered output — and fix every occurrence in the same pass; back a value copied into a second store w…

  blast-radius-grep/SKILL.md on GitHub (opens in a new tab)

• checkpoint-log

  Keep a live, committed checkpoint log during any work unit expected to span multiple commits or sessions. Each commit ships with a short note in the log, what the commit did, the key decision and why, any deviation from plan; closing the unit requires an explicit walk of the checklist including the wiring steps. Triggers when starting multi-commit work, when resuming a unit after a crash or a gap…

  checkpoint-log/SKILL.md on GitHub (opens in a new tab)

• commission-the-roster

  Before spawning a fleet of agents, publish a roster for the operator's approval - role, model tier, token budget, scope and single artifact per agent - and brief each agent with pre-verified facts instead of questions. Triggers when appointing a lead agent, delegating a multi-agent wave, planning a commission whose shape is not yet known, choosing which model tier does which job, or when a usage…

  commission-the-roster/SKILL.md on GitHub (opens in a new tab)

• committee-review

  Run a three-lens committee review of a whole project or major subsystem: positive, adversarial, and neutral-chair reviewers over one shared evidence base, with attribution-stripped consolidation and item-by-item voting. Use when the user asks for a committee review, a multi-perspective audit, a "three Fable review", or wants findings that survive adversarial challenge before becoming a work progr…

  committee-review/SKILL.md on GitHub (opens in a new tab)

• confirm-before-push

  Always ask explicitly before pushing to a remote or fast-forwarding a protected branch. Per-action authorisation, not standing approval. Triggers on any git push, merge, or branch fast-forward operation, regardless of whether previous pushes in the same session were approved.

  confirm-before-push/SKILL.md on GitHub (opens in a new tab)

• constant-time-secret-compare

  Compare bearer tokens, API secrets, signatures, and password-equivalents with a constant-time comparison (hash both sides, then crypto.timingSafeEqual) — never == or short-circuiting string equality. Triggers when writing any code that checks a secret against a stored or expected value. Does not fire on comparing non-secret identifiers.

  constant-time-secret-compare/SKILL.md on GitHub (opens in a new tab)

• context-economy

  Keep the context window small and its prefix stable, because every token in it is re-sent on every later turn. Read slices instead of whole files, cap tool and log output before it lands, isolate high-volume work behind a summary, and clear rather than compact between unrelated tasks. Triggers when about to read a large file, log, dataset, transcript or search result into context; when a session…

  context-economy/SKILL.md on GitHub (opens in a new tab)

• contract-review

  Review a contract or lease for one named party, grading each risk against the exact clause it rests on. Every finding quotes its clause; caps, indemnities and exits are graded only with their interacting clauses; statutory points go to a verification list unless retrieved this session. Triggers on "review this lease from the tenant's side" or a contract audit. Does not fire on a neutral summary,…

  contract-review/SKILL.md on GitHub (opens in a new tab)

• cross-agent-review

  Adversarially review a specific change, design, or finding by having Claude debate one or more INDEPENDENT AI agents (Gemini via the agy CLI or GPT via the codex CLI, driven by Claude with no pasting; or a chat the user drives; several seats at once) over a shared file relay, with mandatory file:line citations, live read-only evidence, and a converge-or-two-positions outcome. Use when the user wa…

  cross-agent-review/SKILL.md on GitHub (opens in a new tab)

• date-parse-utc-safe

  In a UTC server or serverless runtime, new Date("YYYY-MM-DD") is UTC midnight and renders as the previous day in western timezones. Parse date-only strings into explicit local components (new Date(y, m-1, d)) anywhere a date becomes a display string or a day-of-week. Triggers when parsing a date-only string server-side or computing a printed day from one. Does not fire on full ISO timestamps carr…

  date-parse-utc-safe/SKILL.md on GitHub (opens in a new tab)

• db-migration-verification

  Every database migration plan ships with a post-apply verification query that reads catalog state directly, separate from any runtime tests. Triggers on any work involving a database migration, schema change, RLS policy change, trigger change, or constraint change.

  db-migration-verification/SKILL.md on GitHub (opens in a new tab)

• deliverable-integrity

  Three gates for AI-rewritten claims, owner-only facts, and machine-parsed output in any generated document, plus the structural assertions a text diff cannot see, such as a document that opens on a blank page. Claims: diff an AI rewrite claim by claim against the source — the original wins unless the owner confirms. Gaps: facts the generator does not hold render as loud allowlisted placeholder to…

  deliverable-integrity/SKILL.md on GitHub (opens in a new tab)

• dependency-upgrade-verification

  When a dependency major-bump could silently change on-disk formats or behaviour and runtime data cannot distinguish success from failure, answer the question from the dependency's own source: npm pack both versions and diff the file that decides the behaviour, offline, before hunting for a device repro. Triggers on major version bumps of storage, crypto, or serialisation dependencies. Does not fi…

  dependency-upgrade-verification/SKILL.md on GitHub (opens in a new tab)

• earn-every-line

  Nothing enters a file without a present need. Code earns its place by a caller that exists, a comment by saying what the code cannot, flexibility by a stated requirement. Triggers on over-engineered, over-commented, YAGNI, speculative, gold-plating, "just in case", "future-proofing", "flexibility", and on "simplify" / "keep it simple" (both over-correction ditches are fenced); more generally when…

  earn-every-line/SKILL.md on GitHub (opens in a new tab)

• email-delivery-verification

  A 2xx from a transactional email API means accepted, not delivered. Verify actual delivery in the provider's dashboard or webhooks, check the account-level suppression list, verify every recipient leg of a multi-recipient flow, and confirm a mailbox exists before pointing a send at it. Triggers when adding or changing any transactional email send or recipient address, and when diagnosing "the ema…

  email-delivery-verification/SKILL.md on GitHub (opens in a new tab)

• enforce-invariants-in-build

  A rule asserted only in prose — "single source of truth", "never auto-X", "these must match" — is a comment, not a control; if a violation can exist without failing the build, one eventually will and it will look official. Triggers when writing or encountering any comment, doc, or convention that asserts an invariant nothing enforces. Does not fire on deferral markers (flag-deferred-items) or on…

  enforce-invariants-in-build/SKILL.md on GitHub (opens in a new tab)

• env-change-verification

  An environment variable change is not live until the artifact that reads it is rebuilt, redeployed, or re-reads it — and a wrong-but-present value fails silently. Know for each variable whether it is baked at build time or read at request time. Triggers when adding or editing any env var, CI secret, or hosted config value, and when a CI or cloud build consumes build-time env. Does not fire on dat…

  env-change-verification/SKILL.md on GitHub (opens in a new tab)

• findings-are-evidence

  A subagent, reviewer, or scout report is evidence, not findings — and so is your own first-hand defect analysis. Re-derive every Critical or High claim, everything touching a regulatory anchor, and the reasoning about the fix from the primary source before acting or writing it into a durable artifact. Triggers when consuming any agent or reviewer output and when recording a defect or fix analysis…

  findings-are-evidence/SKILL.md on GitHub (opens in a new tab)

• fixtures-from-reality

  A test is only as true as what it feeds the code. Build fixtures from what the real dependency sent on the pinned version, not from its documentation; give a fake the service's failure behaviour (expiry, a lost answer after the effect, what it saves against a key) and its comparison rules; reach a ride's state by the path production takes; feed one half's real output to the other half; and name t…

  fixtures-from-reality/SKILL.md on GitHub (opens in a new tab)

• flag-deferred-items

  When proposing anything as deferred, out of scope, or "for a later phase", plant a grep-able flag at the place where the deferred work will land. Triggers whenever the words "deferred", "out of scope", "later commit", "later phase", "future work", or similar appear in plans, commits, or design discussions.

  flag-deferred-items/SKILL.md on GitHub (opens in a new tab)

• guard-the-spend-paths

  When creating or reviewing any endpoint or control that touches money or shared state, two rules apply together. Every endpoint that spends money (LLM, email, SMS, payment) or writes shared state (bookings, slots) gets a per-IP volume cap the day it is created — anyone can POST directly, bypassing the UI. And any guardrail on that path written to fail open (origin allowlist defaulting to permit,…

  guard-the-spend-paths/SKILL.md on GitHub (opens in a new tab)

• handover

  Produce a structured handover note when the context window fills or the user asks to wrap up. Take the real percentage from /context or, in the Claude desktop app, the get_usage tool; never estimate, and where neither exists record the gap verbatim rather than inventing a figure. Triggers when the context band reaches amber or red, when the user says "wrap up", "handover", or "hand off", or befor…

  handover/SKILL.md on GitHub (opens in a new tab)

• honest-failure-surfacing

  Playbook for the always-on norm "one message per failure mode; error level is for terminal states only". Load when writing a catch block, a user-facing error string, a disabled control, a progress indicator, or choosing telemetry levels. Does not fire on content loss through filters (no-silent-data-drop) or on test skip semantics (prove-it-can-fail).

  honest-failure-surfacing/SKILL.md on GitHub (opens in a new tab)

• legal-citation-integrity

  Audit every citation in a finished or received legal document (statute, regulation, case, quoted authority, internal cross-reference) before anyone relies on it. A citation is Confirmed only with a retrieval behind it; every citation in the document appears in the audit table. Triggers on "check every citation in this opinion", "are these cases real", "does this quote say that". Does not fire on…

  legal-citation-integrity/SKILL.md on GitHub (opens in a new tab)

• legal-notice-handling

  Draft, reply to, or analyse a legal notice (rent or service-charge demand, forfeiture or breach notice, statutory notice, letter before action). Every deadline is a calendar date with its arithmetic; every threatened consequence is confirmed and lawfully available; an admitted fact never concedes a legal conclusion. Triggers on "draft a demand", "reply to this notice". Does not fire on a whole-co…

  legal-notice-handling/SKILL.md on GitHub (opens in a new tab)

• live-data-surgery

  Any ad-hoc destructive operation against a shared or production-adjacent database outside a test harness — bulk delete, cleanup sweep, re-baseline — follows a fixed protocol: read-only inventory first, BEGIN-ROLLBACK dry run, complement-count proof with NULL-collapsed predicates, a self-check that re-runs every predicate, confirmation the markers sit on disposable rows, and explicit gating of any…

  live-data-surgery/SKILL.md on GitHub (opens in a new tab)

• live-state-first

  Playbook for the always-on norm "probe live state before building from any described state". Load when about to write code, SQL, config, or a fixture from a handover, memory note, README, audit tracker, or code comment, or when two documents disagree. Does not fire on repo/PR/branch state (parallel-work-recon owns repo probes) or on state you observed yourself this session.

  live-state-first/SKILL.md on GitHub (opens in a new tab)

• lock-at-the-chokepoint

  Serialise shared operations at the single module-level chokepoint every caller passes through, never in per-instance state — and cap fan-out there too. A check-then-act idempotency guard protects sequential retries but loses the race under concurrency. Triggers when adding a lock, in-flight guard, dedupe check, or rate cap where multiple callers, component instances, or loops can invoke the same…

  lock-at-the-chokepoint/SKILL.md on GitHub (opens in a new tab)

• mass-red-triage

  When a test suite goes from green to broadly red, classify before debugging. Find the first root failure (cascades multiply one fault), check for rate-limit walls, truncated runs, and environment defects, and bound the change's blast radius via the lockfile and diff before attributing blame. Triggers whenever a suite or CI run turns broadly red, or a run's failure count looks implausible in eithe…

  mass-red-triage/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 431k stars · 5 skills
• ECCby affaan-m The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Cod… 297k stars · 30 skills
• andrej-karpathy-skillsby multica-ai A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls. 230k stars · 1 skill
• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 185k stars · 6 skills
• difyby langgenius Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-h… 160k stars
• ui-ux-pro-max-skillby nextlevelbuilder An AI skill that provides design intelligence for building professional UI/UX across multiple platforms. 145k stars · 7 skills