agent-base-template-generator
Agent skill for base-template-generator - invoke with $agent-base-template-generator
34
0%
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 frameworks/languages], scaffolds directory structures, and creates starter configuration files').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to scaffold a new project, create a starter template, set up boilerplate code, or initialize a project structure').
Remove the invocation syntax from the description and replace it with domain-specific keywords that distinguish this skill from other generation or templating tools.
| 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 this skill from any other template-related or generation-related skill. 'Base template generator' could overlap with countless other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%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 system prompt / persona description rather than an actionable skill document. It contains no concrete code examples, no executable templates, no specific commands, and no validation steps. The entire content describes what the agent should do in abstract terms that Claude already understands, wasting token budget without providing any novel, project-specific guidance.
Suggestions
Replace abstract descriptions with concrete, executable template examples (e.g., an actual React component template, an actual API endpoint template) that Claude can directly use or adapt.
Add a clear workflow with validation steps: e.g., 1) identify template type, 2) check project's existing patterns via specific file paths, 3) generate template, 4) validate against linting/type-checking.
Remove generic knowledge Claude already has (what React components are, what error handling is) and focus only on project-specific conventions, patterns, and constraints.
Add references to external files for detailed template catalogs (e.g., 'See TEMPLATES/react-component.md for the standard React component template') instead of listing categories abstractly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows well—what a template is, what best practices are, general categories of templates, and generic quality standards. Nearly every bullet point restates common knowledge without adding project-specific or actionable detail. | 1 / 3 |
Actionability | There are no concrete code examples, executable commands, or specific templates. The entire skill is abstract description ('Generate comprehensive base templates', 'Include proper TypeScript definitions') without any actual template code, file structures, or copy-paste-ready snippets. | 1 / 3 |
Workflow Clarity | The 6-step 'template generation approach' is vague and abstract (e.g., 'Analyze Requirements', 'Apply Best Practices') with no validation checkpoints, no concrete sequencing, and no feedback loops. It reads as a generic process description rather than an actionable workflow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of text with no references to external files, no clear navigation structure, and no separation of overview from detailed content. Lists of categories and quality standards are inlined without any organizational hierarchy. | 1 / 3 |
Total | 4 / 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
ccb062f
- 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.