Tessl • The management layer for AI agent skills

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, sync beads data, recover from an empty local database, or choose between local planning and persistent project tracking.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%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.

A highly actionable, lean instruction skill with concrete executable commands, explicit validation checkpoints, error-recovery paths, and well-scoped cross-skill delegation. Its main weaknesses are repeated sync guidance across sections and reference-grade material (issue types, priorities, lifecycle commands) inlined that could be split out.

Suggestions

Consolidate pull/push sync guidance into the 'Sync Rules' section and reference it from the workflow steps instead of restating it four times.

Move the issue types/priorities definitions and the lifecycle/hygiene command list into a references/ file (e.g., references/issue-reference.md) to slim the main body.

Dimension	Reasoning	Score
Conciseness	Command-dense and free of concept explanations Claude already knows, but sync guidance (pull-before-read, push-after-mutation) is repeated across 'Preferred Route', 'Core CLI Workflow' step 6, 'Sync Rules', and 'Session completion' — efficient overall with minor instances that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases: `bd ready`, `bd show <id>`, `bd update <id> --claim`, a fully-flagged `bd create "Short title" --description=... --type=task --priority=2`, `bd close <id> --reason=...`, and bun sync scripts, plus a realistic discovered-work example with `--deps discovered-from:<parent-id>`.	5 / 5
Workflow Clarity	Clear numbered sequence with explicit checkpoints and feedback loops: inspect-before-edit (`bd show`), `--validate` for issue completeness, empty-`bd prime` recovery via `bd where`, empty-DB troubleshooting with a `git ls-remote` check, session-completion checklist with quality gates (`bun run verify`), and destructive-op guards (never force-push an empty DB; stop and report blocked syncs). Validation is present, so the destructive/batch cap does not apply.	5 / 5
Progressive Disclosure	No bundle files exist, and the single-file structure is well-sectioned with UI/Docker/permission detail correctly delegated to the `scotty` skill (clearly signaled, one level deep). However, sync rules are spread across four sections and the ~135-line body's issue-type/priority and lifecycle reference material could live in a separate file, leaving minor organization gaps versus the ideal split.	4 / 5
	Total	18 / 20 Passed

Description

88%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 that clearly states capabilities and explicit trigger conditions in third-person imperative voice, with concrete action phrases throughout. Its only weaknesses are a few missing natural synonyms and slight overlap risk with generic task-management phrasing.

Suggestions

Add one or two common synonyms users might say instead of 'beads' (e.g., 'todo', 'issue tracker') to the trigger clause to lift keyword coverage.

Tighten generic phrases like 'claim or close tasks' toward Beads-specific wording (e.g., 'claim or close beads') to further reduce overlap with non-Beads task-management requests.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capabilities spanning tracking, dependencies, blockers, multi-session handoff, shared memory, and recovery from an empty database — comprehensive coverage matching the top anchor rather than the 'minor gaps' of a 4.	5 / 5
Completeness	Explicitly answers both 'what' (durable project task tracking, issue dependencies, blocker management, multi-session handoff, shared work memory) and 'when' ('Use when working in a repository that uses bd or Beads... Trigger when the user asks to find ready work...'), matching the anchor requiring both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural phrases ('find ready work', 'claim or close tasks', 'inspect blockers', 'sync beads data') plus the tool names 'bd' and 'Beads', but common synonyms a user might say — 'todo', 'issue tracker', 'ticket' — are missing, keeping it below the comprehensive-synonyms anchor of 5.	4 / 5
Distinctiveness Conflict Risk	Scoped to repositories using bd/Beads with tool-specific triggers, but generic phrases like 'claim or close tasks' and 'create follow-up work' could overlap with ordinary task-management requests in non-Beads repos — mostly distinct with minor overlap risk rather than the minimal-risk niche of a 5.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: williamrjribeiro/bun-agentic-starter
Path: .agents/skills/beads/SKILL.md
Revision: 26f2eaa

Reviewed: 13 hours ago

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.

beads

Table of Contents

Is this your skill?