agent-base-template-generator

Agent skill for base-template-generator - invoke with $agent-base-template-generator

1.01x

Quality

Does it follow best practices?

Impact

94%

1.01x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-base-template-generator/SKILL.md

Quality

Content

0%Scale 1-3

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 prompt rather than an actionable skill document. It describes what the agent should be good at in abstract terms but provides zero concrete examples, executable code, actual templates, or specific workflows. The content explains concepts Claude already understands and would be almost entirely replaced by a few concrete template examples with clear instructions.

Suggestions

Replace the abstract descriptions with 2-3 concrete, executable template examples (e.g., a React component template, an API endpoint template) that Claude can directly use as starting points.

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 project conventions.

Remove the persona description and category listings entirely — Claude already knows what React components and API endpoints are. Focus only on project-specific patterns, conventions, and concrete code.

Add references to external files for detailed template variants (e.g., 'See REACT_TEMPLATES.md for component patterns' or 'See API_TEMPLATES.md for endpoint scaffolding') to enable progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanations of concepts Claude already knows (what templates are, what best practices are, listing generic categories). The content reads like a persona description rather than actionable instructions, and most of the text is padding that doesn't add operational value.	1 / 3
Actionability	No concrete code examples, no executable commands, no specific templates or snippets. The entire content is abstract description ('Generate comprehensive base templates', 'Include proper TypeScript definitions') without any actual template code or copy-paste-ready guidance.	1 / 3
Workflow Clarity	The 'template generation approach' lists 6 high-level steps but they are vague and abstract ('Analyze Requirements', 'Apply Best Practices'). There are no validation checkpoints, no concrete sequencing, and no feedback loops for error recovery.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files, no structured navigation, and no separation of overview from detailed content. Everything is dumped into a single unstructured document with no bundle files to support it.	1 / 3
	Total	4 / 12 Passed

Description

0%Scale 1-3

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 is an extremely weak description that essentially only states the skill's internal name and invocation command. It provides no information about what the skill does, what actions it performs, what domain it applies to, or when it should be selected. It would be nearly impossible for Claude to correctly choose this skill from a list of available skills.

Suggestions

Add concrete actions describing what the skill does, 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 create a new project, scaffold a codebase, generate starter templates, or set up boilerplate files.'

Specify the type of templates (e.g., React, Python, API) to make the skill distinctive and reduce conflict risk with other template-related skills.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for base-template-generator' is entirely vague — it doesn't explain what templates are generated, what domain it applies to, or what operations it performs.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no meaningful explanation of functionality.	1 / 3
Trigger Term Quality	The only potentially relevant term is 'base-template-generator', which is a technical/internal name, not a natural keyword a user would say. There are no natural trigger terms like 'template', 'scaffold', 'boilerplate', or any domain-specific language.	1 / 3
Distinctiveness Conflict Risk	The description is so generic that it could conflict with any template-related skill. Without specifying what kind of templates, what format, or what context, it provides no distinguishing characteristics.	1 / 3
	Total	4 / 12 Passed

Validation

100%

Warnings & errors only

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/claude-flow
Path: .agents/skills/agent-base-template-generator/SKILL.md
Commit: 913f9ea

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.