Skip to content
SkillModel-led100 tokens in use

Release It!

Michael Nygard-inspired rules for timeouts, retries, circuit breakers, bulkheads, back pressure and observability.

3,324 stars on the repository MIT Licenseciembor/agent-rules-books · release-it
npx skills add ciembor/agent-rules-books --skill release-it
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Release It! costs

33tokens idle
100tokens in use
4,018tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Needs attention
  • Frontmatter11/15
  • Structure0/25
  • Examples0/15
  • Output2/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Fair
  • Development activity44
  • Maintenance72
  • Community52
  • Maturity28
  • Momentum40

This skill loads a compact rule set inspired by Michael T. Nygard’s Release It!. It tells a coding agent that a passing happy path is not production readiness, and to design failure semantics, demand limits, isolation and diagnosis up front.

It applies to services, APIs, jobs, queues, deployment paths and control tooling that must survive latency, overload, bad data and operational mistakes.

What You Get

  • A mini rule set with decision rules, trigger rules and a closing checklist for production reliability
  • A nano version for tight context budgets and a full version for reference
  • A skill description that makes the agent load the rules for failure handling, capacity and deployment tasks

Common Use Cases

  • Adding an outbound call with a timeout, retry limits and a degraded mode
  • Bounding a queue, buffer, cache or result set and defining behavior when it is full
  • Making migrations and one-time jobs restartable, auditable and reversible
  • Reviewing an incident for the failure chain and the missing defenses

What Makes It Unique

It is the production-failure rule set in the repository. Each trigger, such as a new queue, cache, health check or API contract, lists what must be defined before the change goes ahead, including timeout, retry eligibility, capacity, full-queue behavior and rollback. It includes hostile traffic, control tooling and chaos testing with stop conditions, which the design-focused rule sets do not.

Under The Hood

The skill is a SKILL.md with a name and description, plus Markdown files holding the mini, nano and full versions of the rules. The SKILL.md tells the agent to read the mini file before design or code decisions and the full file only for harder tradeoffs. It contains no scripts. It does not fetch web pages, call APIs, run commands or write files; the agent only reads the rule text.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers