agent-base-template-generator
Agent skill for base-template-generator - invoke with $agent-base-template-generator
38
6%
Does it follow best practices?
Impact
94%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-base-template-generator/SKILL.mdQuality
Discovery
0%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 is essentially a label with an invocation command, providing no useful information about what the skill does, when to use it, or what triggers should activate it. It fails on every dimension of the rubric, offering neither concrete actions, natural trigger terms, completeness, nor distinctiveness.
Suggestions
Describe the specific actions the skill performs, e.g., 'Generates boilerplate project templates for [specific framework/language], including directory structure, configuration files, and starter code.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to scaffold a new project, create a starter template, set up boilerplate, or initialize a new [framework] application.'
Clarify the domain and type of templates to distinguish this skill from other template or code generation skills, e.g., specify whether it handles React templates, API templates, documentation templates, etc.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for base-template-generator' is entirely vague—it doesn't describe what the skill actually does, what templates it generates, or what domain it operates in. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | There are no natural keywords a user would say. 'base-template-generator' is an internal tool name, not a term users would naturally use in requests. The invocation syntax '$agent-base-template-generator' is technical jargon, not a trigger term. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish from any other template-related or generation-related skill. 'Base template generator' could overlap with countless other skills involving templates, scaffolding, or code generation. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a persona description rather than an actionable skill. It tells Claude to be a 'Base Template Generator' and lists abstract qualities and categories but provides zero concrete templates, code examples, or executable guidance. The content is verbose, explaining general software engineering concepts Claude already knows, while failing to provide the specific, novel information that would make this skill useful.
Suggestions
Replace abstract descriptions with concrete, executable template examples (e.g., a complete React component template, an API endpoint template) that Claude can directly use as starting points.
Remove the lists of general software engineering principles (error handling, TypeScript types, documentation) that Claude already knows, and instead focus on project-specific patterns or conventions that are unique to this codebase.
Add specific file paths, commands, or references to project configuration files (e.g., 'See CLAUDE.md for project conventions' or 'Use the template in templates/component.tsx as a base') to make the skill actionable.
Structure the content with a quick-start section showing one complete template generation example, then reference separate files for additional template categories.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of general concepts Claude already knows. Lists of responsibilities, categories, and quality standards are largely redundant descriptions of good software engineering practices rather than specific, novel instructions. The content could be reduced by 70%+ without losing actionable information. | 1 / 3 |
Actionability | No concrete code examples, no executable commands, no specific templates or snippets. The entire skill is abstract descriptions like 'Generate comprehensive base templates' and 'Include proper TypeScript definitions' without showing what any of these look like in practice. | 1 / 3 |
Workflow Clarity | There is a numbered 5-step workflow (Analyze Requirements → Apply Best Practices → Structure Foundation → Include Essentials → Enable Extension → Provide Context), but it lacks any validation checkpoints, concrete commands, or feedback loops. The steps are abstract directives rather than actionable procedures. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files, no clear navigation structure, and no separation of overview from detailed content. Everything is dumped into a single flat document with bold headers but no meaningful progressive disclosure. | 1 / 3 |
Total | 5 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ruvnet/ruflo
- Commit
398f7c2
- 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.