CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

beads

Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is beads in gastownhall/beads

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

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

An exemplary lean, command-driven skill body: every command is executable with realistic flags, the workflow is sequenced with an inspect-first checkpoint and mutation guardrails, and the single-file organization fits the content's size. The only gap is a missing post-action verification step in the core workflow.

DimensionReasoningScore

Conciseness

The body is lean and efficient — every section (First Step, CLI workflow, what belongs in Beads, Rules) adds non-obvious operational knowledge with zero padding or explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Fully executable, copy-paste-ready commands with realistic arguments (e.g., 'bd create "Short title" --description=… --type=task --priority=2', 'bd update <id> --claim', 'bd close <id> --reason="Completed"') covering the common cases, matching the top anchor.

5 / 5

Workflow Clarity

A clear numbered sequence (find → inspect → claim → create follow-ups → close) with a first-step fallback ('bd prime' then 'bd where' if it prints nothing) and guardrails ('Inspect before editing', 'Do not auto-close or mutate tasks unless the work is actually complete'), but no explicit post-action verification step (e.g., re-running 'bd show' after an update), fitting anchor 4 rather than 5.

4 / 5

Progressive Disclosure

A single-file skill with no bundle files and no need for any: the content is compact and well-organized into clear sections with nothing that belongs in a separate reference file, so the structure is fully appropriate for one-level navigation.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

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

A strong description with explicit use/trigger clauses, concrete lifecycle actions, and both the CLI name and its synonym. The only weakness is that a few common natural phrasings users might use (TODO, tickets, issues) are not covered as trigger terms.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions spanning the full task lifecycle — 'find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context' — matching the comprehensive-coverage anchor; no gaps warrant the level-4 'minor gaps' anchor.

5 / 5

Completeness

It explicitly answers 'when' with both 'Use when working in a repository that uses bd or Beads…' and 'Trigger when the user asks to…' clauses containing concrete trigger phrases, and states the 'what' ('durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory'), matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural coverage including the tool name and synonym ('bd or Beads'), 'task tracking', 'blockers', 'handoff', and 'claim or close tasks', but a few natural variations users might say (e.g., 'TODO', 'tickets', 'issues') are absent, fitting anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

'Repository that uses bd or Beads' plus tool-specific operations (claim tasks, inspect blockers, bd prime context recovery) define a clear niche with minimal overlap risk against generic planning or TODO skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

branben/school-core

Path

.agents/skills/beads/SKILL.md

Reviewed

Table of Contents

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.