Interactive wizard that guides you through creating a comprehensive agentic development scaffold. Use when starting a new project or adding AI capabilities to an existing codebase. Asks about project goals, tech stack, team size, and workflows, then generates custom instructions, skills, agents, and MCP configurations.
71
60%
Does it follow best practices?
Impact
89%
3.17xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/project-scaffold/SKILL.mdQuality
Discovery
85%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 a strong description that clearly communicates both what the skill does and when to use it, with specific outputs enumerated. The main weakness is the use of second person voice ('guides you through') which violates the third-person guideline, and some trigger terms lean toward jargon ('agentic development scaffold') rather than natural user language. Overall it would effectively help Claude select this skill in the right context.
Suggestions
Replace second person 'guides you through' with third person voice like 'Guides users through' or 'Interactive wizard for creating...'
Add more natural trigger terms users might say, such as 'setup', 'initialize', 'bootstrap', 'project template', or 'configure workspace'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: guides through creating a scaffold, asks about project goals/tech stack/team size/workflows, generates custom instructions/skills/agents/MCP configurations. | 3 / 3 |
Completeness | Clearly answers both what ('interactive wizard that guides through creating a comprehensive agentic development scaffold, generates custom instructions, skills, agents, and MCP configurations') and when ('Use when starting a new project or adding AI capabilities to an existing codebase'). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'new project', 'AI capabilities', 'scaffold', 'MCP configurations', but misses common user phrasings like 'setup', 'initialize', 'bootstrap', 'project template', or 'getting started'. Terms like 'agentic development scaffold' are somewhat jargon-heavy. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'interactive wizard', 'agentic development scaffold', and the specific outputs (instructions, skills, agents, MCP configurations) creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable high-level framework for scaffolding agentic projects but suffers from significant verbosity, embedding large templates and questionnaires inline while simultaneously instructing generated content to avoid this pattern. The workflow phases are clear but lack validation checkpoints critical for a generator that creates many files. Actionability is hampered by placeholder-heavy templates that don't give Claude enough concrete guidance on what quality output looks like.
Suggestions
Reduce the inline questionnaire to a compact table or bullet list — Claude can present multiple-choice options without being shown the exact format for each question.
Add explicit validation checkpoints after Phase 2 and Phase 3 (e.g., 'Present generated file list to user for confirmation before writing' and 'Verify no file exceeds size limits').
Move the testing skill template, size limits table, and progressive disclosure tier diagram into bundle files (e.g., templates/testing.template.md, reference.md) to practice the progressive disclosure pattern the skill itself mandates.
Replace placeholder text like '[Language-specific test template]' and '[project-specific command]' with concrete examples for at least one stack (e.g., TypeScript + Jest) so Claude has a quality reference for generation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~150+ lines. It includes extensive multiple-choice question lists that Claude could generate dynamically, explains concepts like progressive disclosure tiers in detail Claude already understands, and embeds large template examples inline despite its own rules saying not to. The size limits table and tier diagram add bulk without proportional value. | 1 / 3 |
Actionability | The skill provides a structured questionnaire and describes what to generate, but the actual generation guidance is incomplete — Phase 2 says 'create language-specific best practices' and 'common gotchas' without specifying what those are. The testing skill template uses placeholders like [PROJECT_STACK] and [Language-specific test template] rather than executable content. It's a framework, not a fully actionable recipe. | 2 / 3 |
Workflow Clarity | The three-phase workflow (Discovery → Core Config → Skills) is clearly sequenced, but there are no validation checkpoints. After generating potentially dozens of files, there's no step to verify correctness, check for conflicts, or confirm with the user before proceeding. For a scaffold generator that creates many files, missing validation/feedback loops is a significant gap. | 2 / 3 |
Progressive Disclosure | The skill describes a progressive disclosure pattern and mandates it for generated content, but ironically violates it in its own body — the full testing skill template, the tier diagram, the complete questionnaire, and the size limits table are all inlined rather than split into supporting files. No bundle files are provided despite the skill's own rules requiring templates/ subdirectories and separate reference files. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
a5309ae
Table of Contents
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.