decision-record
The artifact this agent leaves behind — findable, dated, revisitable.
$ npx -y skills add vanara-agents/skills --agent claude-codeHow it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
The artifact this agent leaves behind — findable, dated, revisitable.
Agent definition
decision-record.mdDecision record — build vs buy for feature flags
The artifact this agent leaves behind — findable, dated, revisitable.
Question
Adopt a flags SaaS or build on our config system? (Team: 9 eng. Flags needed for one product area now, likely three within a year.)
Criteria and weights (agreed before scoring)
Delivery speed 35% · reliability blast-radius 25% · cost over 3y 20% · flexibility 20%
Scores
- **Buy (SaaS)**: 8.1 weighted — wins on speed and reliability (their outage
≠ our outage, kill-switch semantics battle-tested).
- **Build**: 6.2 — wins flexibility, loses 6-8 weeks of a senior engineer and
becomes an unowned internal product (the graveyard pattern).
Decision
Buy. Wrap it behind our own `flags.isOn()` facade so the vendor is swappable and the flexibility loss is contained to the facade.
Revisit triggers
Vendor price doubling · >3 incidents/year attributable to the vendor · flag evaluation needed in the hot path (<1ms budget).
🐒 Free agents, skills & packs for Claude Code One subscription. An army of Claude Code agents. 30 production-grade agents, skills, and packs for Claude Code — free, Apache-2.0, install with one command.
Repo: vanara-agents/skills
Other agents on vanara-agents-skills.
- AGENT
Use when designing a new HTTP/GraphQL API or changing an existing one — modeling resources, defining endpoint contracts, choosing status codes, pagination, filtering, error envelopes, versioning, and idempotency. Produces a reviewable API contract plus an OpenAPI snippet, not
Open agent - review-notes
This shows how the api-designer agent reviews a flawed draft. Findings are severity-ranked so the implementer fixes the contract-breakers first. Severity legend: **CRITICAL** (breaks clients / data risk), **HIGH** (real bug or inconsistency), **MEDIUM** (maintainability),
Open agent - contract-and-openapi
The contract is the deliverable. Express it as an **OpenAPI 3.1** document so it is human-readable *and* machine-checkable. This reference covers how to structure that document and what `scripts/lint-openapi.mjs` enforces.
Open agent - design-checklist
Run through this before declaring an API contract done. It is ordered the way you should *design*: resources first, cross-cutting rules last. Every box is a place real APIs go wrong in production.
Open agent - versioning-and-evolution
APIs are forever once published: a consumer you've never met may depend on any field you expose. Design so you can **add without breaking**, and version explicitly when you must break.
Open agent - pr-comment-template
Copy-paste templates for leaving review comments. Keep each comment to one finding: an anchor, the problem, and the fix.
Open agent