design-doc-template
Design Doc Template - Auto-activating skill for Technical Documentation. Triggers on: design doc template, design doc template Part of the Technical Documentation skill category.
41
11%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/17-technical-docs/design-doc-template/SKILL.mdQuality
Discovery
22%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 metadata stub rather than a functional skill description. It names the skill category and repeats the trigger term but provides no information about what actions the skill performs or what outputs it produces. The description would fail to help Claude choose this skill appropriately among alternatives.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates structured design document templates with sections for problem statement, proposed solution, alternatives considered, and implementation plan.'
Include an explicit 'Use when...' clause, e.g., 'Use when the user asks to create a design doc, RFC, technical specification, or architecture document.'
Expand trigger terms to include natural variations: 'design document', 'tech spec', 'RFC', 'architecture doc', 'technical specification template'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Technical Documentation' and 'design doc template' without describing any concrete actions. There are no verbs indicating what the skill actually does (e.g., creates, generates, formats). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and while it lists triggers, there's no explicit 'Use when...' clause explaining when Claude should select this skill or what problem it solves. | 1 / 3 |
Trigger Term Quality | Includes 'design doc template' which is a natural term users might say, but the trigger terms are duplicated and missing common variations like 'design document', 'technical design', 'architecture doc', or 'RFC template'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'design doc template' trigger is somewhat specific, but 'Technical Documentation' is broad and could overlap with other documentation skills. The lack of specific capabilities makes it harder to distinguish from general documentation tools. | 2 / 3 |
Total | 6 / 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 placeholder with no substantive content. It describes what a design doc template skill should do without providing any actual templates, examples, structure, or actionable guidance. The entire content could be replaced with a single actual design doc template that would be infinitely more useful.
Suggestions
Replace the abstract descriptions with an actual design doc template structure (sections like Problem Statement, Proposed Solution, Alternatives Considered, etc.)
Add a concrete, copy-paste ready markdown template that users can immediately use for their design documents
Include at least one filled-out example showing what good design doc content looks like in each section
Remove all meta-descriptions about what the skill does and replace with the actual actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is no concrete guidance, code, commands, or specific instructions. The skill describes what it does in abstract terms but never shows how to actually create or use a design doc template. | 1 / 3 |
Workflow Clarity | No workflow is provided. The skill claims to provide 'step-by-step guidance' but contains zero actual steps, sequences, or processes for creating design documentation. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic descriptions with no references to detailed materials, examples, or templates. There's no structure pointing to actual design doc templates or related resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.