adb-skill-generator
Meta-tool for rapid adb-* skill creation from templates
70
26%
Does it follow best practices?
Impact
100%
1.88xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/adb-meta-automation/adb-skill-generator/SKILL.mdQuality
Discovery
17%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 too terse and jargon-heavy to serve as an effective skill selector. It lacks a 'Use when...' clause, concrete action verbs, and natural trigger terms that a user would employ. While the domain (adb-* skill creation) provides some distinctiveness, the description needs significant expansion to be useful in a multi-skill selection context.
Suggestions
Add an explicit 'Use when...' clause with natural trigger phrases like 'create a new adb skill', 'scaffold a skill', 'add a new skill from template', 'generate skill boilerplate'.
List specific concrete actions such as 'generates YAML frontmatter, creates skill markdown files, sets up directory structure, populates template fields'.
Replace jargon like 'meta-tool' with plain language and include natural keyword variations users might say, such as 'new skill', 'skill template', 'skill scaffolding'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (adb-* skill creation) and a general action (rapid creation from templates), but doesn't list specific concrete actions like 'generates boilerplate', 'configures YAML frontmatter', 'sets up test scaffolding', etc. | 2 / 3 |
Completeness | It partially addresses 'what' (rapid skill creation from templates) but completely lacks any 'when' clause or explicit trigger guidance, which per the rubric caps completeness at 2 at best, and the 'what' is also quite thin, placing this at a 1. | 1 / 3 |
Trigger Term Quality | The terms 'meta-tool', 'adb-* skill creation', and 'templates' are technical jargon unlikely to match natural user queries. Users would more likely say 'create a new skill', 'add a skill', 'scaffold a skill', or 'new adb skill'. | 1 / 3 |
Distinctiveness Conflict Risk | The 'adb-* skill creation' niche is fairly specific and unlikely to conflict with most other skills, but the term 'meta-tool' and 'templates' could overlap with other scaffolding or template-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is significantly over-engineered for what is essentially a scaffolding tool. It suffers from extreme verbosity—explaining design philosophy, TOON format basics, and ecosystem integration at length when the core value is just 'run this command to generate a skill directory.' The actionable CLI examples are its strongest element, but they're buried in unnecessary context that wastes token budget.
Suggestions
Cut the document by 60%+: remove 'Design Philosophy', 'What is TOON?', 'Benefits' list, emoji capability bullets, and the 'Related Skills' section—none add actionable information Claude needs.
Add a validation step after skill generation (e.g., verify SKILL.md frontmatter is valid, check generated scripts are syntactically correct) to create a proper feedback loop in the workflow.
Move 'Common Customization Patterns', 'Troubleshooting', and 'Creating New Workflows' to separate reference files and link to them from a concise overview.
Show the actual template content that gets generated (at least a truncated SKILL.md and one script) instead of just describing the 9-section structure abstractly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Contains extensive sections that don't add value: 'Design Philosophy' explaining obvious principles, 'What is TOON?' explaining a format Claude doesn't need explained, 'Related Skills' listing without actionable content, emoji-laden capability lists, and a 'Benefits' section stating the obvious ('Easy to understand and maintain'). The 9-section template structure description and workflow template structure could be drastically shortened. | 1 / 3 |
Actionability | Provides concrete CLI commands with parameters and examples, which is good. However, the actual generated script content is not shown (just a numbered section outline), the TOON template is pseudocode-level YAML, and customization patterns show only small snippets without full context. The skill describes what gets generated but doesn't show the actual template content that would be most useful. | 2 / 3 |
Workflow Clarity | The 4-step 'Integration with Ecosystem' section provides a reasonable workflow sequence, but lacks validation checkpoints. There's no step to verify the generated skill is correct before proceeding to implementation, no validation of generated SKILL.md frontmatter, and no feedback loop for when generation partially fails (exit code 1). The troubleshooting section partially compensates but doesn't integrate into the workflow. | 2 / 3 |
Progressive Disclosure | References workflow/ directory and related skills, but the main document is monolithic with too much inline content. The 'Design Philosophy', 'Common Customization Patterns', 'Troubleshooting', and 'Workflows' sections could be separate files. The TOON explanation section is particularly misplaced—it belongs in the workflow orchestrator skill, not here. Multiple sections repeat information about running workflows. | 2 / 3 |
Total | 7 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- majiayu000/claude-skill-registry
- Commit
d156cd1
- 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.