beads

Use beads (bd) for persistent task tracking in coding projects. A git-backed issue tracker designed for AI agents with dependency graphs, hierarchical tasks, and multi-agent coordination.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, highly actionable, and provides a clear workflow with verification checkpoints; the main weakness is monolithic organization with no progressive disclosure into reference files.

Suggestions

Split the full command catalog and dependency/merge-conflict material into a references file (e.g. COMMANDS.md) referenced from the body to improve progressive disclosure.

Keep the most-used commands inline and move advanced edge cases (merge conflicts, MCP server) behind clearly signaled one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-focused — tables and copy-paste code blocks — assuming Claude's competence without explaining concepts it already knows, so it matches the lean-and-efficient anchor.	3 / 3
Actionability	Commands are fully executable and specific (e.g. `bd ready --json`, `bd create "Title" -p 1`), with a command table and copy-paste-ready blocks matching the executable-anchor.	3 / 3
Workflow Clarity	The "Land the Plane" section gives a numbered sequence with an explicit verification checkpoint (`git status` must show "up to date with origin"), matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	Sections are well-organized with clear headers, but the ~210-line body is monolithic with no bundle files or external references, and content like the full command catalog and merge-conflict handling is inline rather than split out.	2 / 3
	Total	11 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, clearly conveying what beads does, but it omits an explicit use-when trigger clause and its keywords are somewhat technical rather than natural user phrasing.

Suggestions

Add an explicit trigger clause, e.g. "Use when tracking tasks, managing work across sessions, or coordinating multi-agent coding projects."

Soften jargon with natural terms users would say (e.g. "to-do lists", "tickets", "track work") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "persistent task tracking", "dependency graphs, hierarchical tasks, and multi-agent coordination" — matching the multi-action anchor rather than the partial-coverage anchor at 2.	3 / 3
Completeness	Clearly states what beads does but lacks any explicit "Use when..." trigger guidance, which per the guidelines caps completeness at 2 even though the what is well covered.	2 / 3
Trigger Term Quality	Includes relevant terms like "task tracking" and "issue tracker" but leans technical; misses common user-facing variations (e.g. "to-do", "tickets", "track work") that would push it to 3.	2 / 3
Distinctiveness Conflict Risk	"git-backed issue tracker designed for AI agents" carves out a clear niche with distinct triggers unlikely to overlap with generic task or code skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: block/agent-skills
Commit: 329a55d

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.