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 is an extremely weak description that fails on all dimensions. It reads as a placeholder or auto-generated stub rather than a functional skill description. It provides no information about what the skill does, what types of templates it generates, or when Claude should select it.
Suggestions
Replace the entire description with concrete actions the skill performs, e.g., 'Generates base project templates for [specific frameworks/languages], including directory structure, configuration files, and boilerplate 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 codebase.'
Specify the types of templates supported (e.g., React, Python, Node.js) to make the skill distinctive and reduce conflict risk with other template or code generation skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides 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 any specific capabilities. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's an agent skill and how to invoke it, providing no functional or contextual information. | 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. No domain-specific or task-specific trigger terms are present. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic that 'template generator' could overlap with any number of template-related skills. There are no distinct triggers or domain boundaries to differentiate it. | 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 persona prompt rather than an actionable skill document. It describes what the agent should be in abstract terms but provides zero concrete templates, code examples, commands, or specific workflows. Every section restates general software engineering principles that Claude already knows, wasting token budget without adding any novel, project-specific value.
Suggestions
Replace the abstract descriptions with actual template examples — include at least 2-3 concrete, copy-paste-ready templates (e.g., a React component template, an API endpoint template) with executable code.
Add a clear multi-step workflow with validation: e.g., 1) Identify template type, 2) Check project conventions in CLAUDE.md, 3) Generate template, 4) Validate against linting/type-checking, 5) Output with customization notes.
Remove all generic descriptions of concepts Claude already knows (what React components are, what error handling is, what TypeScript types are) and focus only on project-specific patterns and conventions.
Create supporting bundle files (e.g., TEMPLATES.md with detailed examples, PATTERNS.md with project-specific conventions) and reference them from the main skill for progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with information Claude already knows. Explains general concepts like 'React components with proper lifecycle management,' 'API endpoints with validation and error handling,' and lists broad categories of templates without adding any novel, project-specific knowledge. The entire content reads like a generic role description rather than actionable instructions. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples anywhere. The content is entirely abstract descriptions and vague directives like 'Generate comprehensive base templates' and 'Include proper TypeScript definitions.' There are no actual template examples, no specific file structures, no code snippets to follow. | 1 / 3 |
Workflow Clarity | The numbered 'template generation approach' steps are abstract and non-actionable (e.g., 'Analyze Requirements,' 'Apply Best Practices'). There are no validation checkpoints, no concrete sequencing, and no feedback loops. This is a description of a philosophy, not a workflow. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to supporting files, no structured navigation, and no separation of overview from detailed content. There are no bundle files to support the skill, and the content doesn't organize itself into discoverable sections with clear pointers. | 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
367cb82
- 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.