Agent skill · Content & Marketing

dora-check

Assess delivery health metrics. For software: DORA + APEX. For content/AI/service products: product-type-appropriate metrics.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill dora-check-haabe-mycelium --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 14 KB
Bundled scripts: none
Path: skills/analysis/dora-check-haabe-mycelium/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Delivery Metrics Check Assess delivery health using product-type-appropriate metrics. Check `product_type` from `.claude/diamonds/active.yml` to determine which assessment to run. **Product type routing** (v0.11.0): - **software**: Full DORA + APEX assessment (Parts 1-3 below) - **content_course, content_publication, content_media**: Content Delivery Assessment (Part 4 below) - **ai_tool**: AI Tool Assessment (Part 5 below) + DORA/APEX if code components exist - **service_offering**: Service Delivery Assessment (Part 6 below) --- ## Preflight: Read target canvas file(s) before any Write/Edit **Hard rule.** Before issuing `Write` or `Edit` against any `.claude/canvas/*.yml`, use the **Read tool** on that file in this session. Claude Code's Read-before-Write check requires the `Read` tool specifically — `cat`/`head`/`grep` via Bash do NOT satisfy it. **Edit vs Write — different cost profiles** (verified 2026-05-14): - **`Edit`** (exact-string replacement): `Read` with `limit: 1` satisfies the check at ~50 tokens. State-tracking is per-file, not per-byte — subsequent `Edit` calls work anywhere in the file. Use this for partial updates against large canvas files (e.g., `purpose.yml`

What's inside
Steps it walks through
  1. Preflight: Read target canvas file(s) before any Write/Edit
  2. Software Products
  3. Part 1: DORA Metrics (Forsgren)
  4. Part 2: APEX Metrics (LinearB)
  5. A — AI Leverage
  6. P — Predictability
  7. E — Flow Efficiency (The Shifting Bottleneck)
  8. X — Developer Experience
  9. Output
  10. Part 3: SRE Metrics (Error Budgets)
  11. Decision Log (MANDATORY)
  12. Canvas Output
  13. Part 4: Content Delivery Assessment (v0.11.0)
  14. Producer-Side (how well we make it)
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the dora-check skill do?

Assess delivery health metrics. For software: DORA + APEX. For content/AI/service products: product-type-appropriate metrics.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill dora-check-haabe-mycelium --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going