development
AllBeads development process. Use when planning features, creating documentation, tracking work with beads, or understanding the documentation system.
80
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/development/SKILL.mdQuality
Discovery
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.
This description has good structure with an explicit 'Use when...' clause that covers multiple scenarios, earning high marks for completeness. However, it relies on project-specific terminology ('AllBeads', 'beads') without explaining what these mean, and the listed capabilities are fairly generic development activities that could benefit from more concrete, specific actions.
Suggestions
Add more specific concrete actions beyond generic terms like 'planning features' - e.g., 'Creates bead tracking entries, generates feature specifications, maintains changelog documentation'
Include natural trigger terms users might actually say, such as 'roadmap', 'feature request', 'project planning', 'work items', or file extensions if applicable
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AllBeads development) and mentions some actions (planning features, creating documentation, tracking work), but these are fairly generic development activities rather than concrete, specific capabilities. | 2 / 3 |
Completeness | Clearly answers both what (development process, planning, documentation, tracking) and when (explicit 'Use when...' clause with multiple trigger scenarios including planning features, creating documentation, tracking work with beads). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'planning features', 'documentation', 'tracking work', and 'beads', but 'beads' is project-specific jargon that users may not naturally use, and common variations are missing. | 2 / 3 |
Distinctiveness Conflict Risk | The 'AllBeads' project name and 'beads' terminology provide some distinctiveness, but 'planning features' and 'creating documentation' are generic enough to potentially overlap with other development or documentation skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong skill document with excellent workflow clarity and actionability. The multi-step development process is clearly sequenced with validation checkpoints, and concrete bash commands make guidance immediately executable. Minor verbosity in the anti-patterns section (which largely restates earlier guidance) and some redundancy around quality gates prevent a perfect conciseness score.
Suggestions
Consolidate the anti-patterns section by removing items already covered in the main workflow (e.g., quality gates, issue lifecycle) to reduce redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some redundancy (anti-patterns section repeats guidance from earlier sections, quality gates mentioned twice). The tables and structured format help, but some sections could be tightened. | 2 / 3 |
Actionability | Provides concrete, executable bash commands throughout (bd create, bd update, cargo commands). Clear copy-paste ready examples for beads management, quality gates, and workflow steps. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing (Steps 1-5), explicit validation checkpoints (quality gates before commits), and clear issue lifecycle rules with explicit ordering. The 'CRITICAL: Follow this order' section demonstrates proper feedback loops. | 3 / 3 |
Progressive Disclosure | Well-organized with quick reference at top, clear section headers, and appropriate references to external specs (specs/PRD-00.md, etc.). Content is appropriately split between overview and detailed guidance without deep nesting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- thrashr888/AllBeads
- Commit
e85caf1
- 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.