agent-base-template-generator
Agent skill for base-template-generator - invoke with $agent-base-template-generator
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-base-template-generator41
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 94%
↑ 1.01xAgent success when using this skill
Validation for skill structure
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 critically deficient across all dimensions. It functions only as an invocation reference rather than a skill description, providing no information about capabilities, use cases, or trigger scenarios. Claude would have no basis for selecting this skill appropriately from a skill library.
Suggestions
Add concrete actions describing what templates are generated (e.g., 'Generates boilerplate project structures for Python packages, React apps, or API services')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to scaffold a new project, create starter code, or set up a boilerplate')
Specify the domain or template types to distinguish from other template-related skills (e.g., 'project templates', 'code scaffolding', specific frameworks or languages supported)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only states it's an 'agent skill' and how to invoke it. 'base-template-generator' hints at functionality but doesn't describe what it actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only provides invocation syntax without explaining the skill's purpose or use cases. | 1 / 3 |
Trigger Term Quality | No natural user keywords are present. Users wouldn't naturally say 'agent-base-template-generator' or 'invoke with $agent'. The technical invocation syntax is not how users describe their needs. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'template generator' could conflict with any template-related skill. No specific domain, file types, or use cases are mentioned to distinguish it from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
20%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 actionable guidance. It tells Claude what kind of agent to be but provides zero concrete templates, code examples, or executable instructions. The content explains concepts Claude already understands (best practices, TypeScript, error handling) without providing the actual templates that would make this skill useful.
Suggestions
Replace abstract descriptions with actual template examples - show 2-3 concrete, copy-paste ready templates for common use cases (React component, API endpoint, config file)
Remove the persona framing ('You are a Base Template Generator, an expert architect...') and replace with direct instructions and examples
Add specific file paths or references to template files that contain the actual boilerplate code
Include validation steps for generated templates (e.g., 'After generating, verify TypeScript compiles with: npx tsc --noEmit')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of concepts Claude already knows (what templates are, what best practices mean, general software architecture principles). The content is padded with unnecessary context like 'Your expertise lies in...' and 'Your core responsibilities' that don't add actionable value. | 1 / 3 |
Actionability | No concrete code examples, no executable commands, no actual templates shown. The entire skill describes what the agent should do abstractly ('Generate comprehensive base templates') without providing any specific, copy-paste ready examples of actual templates or generation patterns. | 1 / 3 |
Workflow Clarity | The 5-step 'template generation approach' provides a sequence, but lacks validation checkpoints, concrete actions, or feedback loops. Steps like 'Analyze Requirements' and 'Apply Best Practices' are too abstract to guide actual execution. | 2 / 3 |
Progressive Disclosure | Content is a monolithic block with no references to external files for detailed templates or examples. The structure uses headers but everything is inline. For a template generator, actual template files should be referenced rather than described. | 2 / 3 |
Total | 6 / 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.
- 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.