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.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill design-doc-templateActivation
22%This description is severely underdeveloped, functioning more like a metadata stub than a useful skill description. It fails to explain what the skill actually does (create templates? fill templates? review design docs?) and lacks explicit guidance on when Claude should select it. The duplicate trigger term suggests incomplete or auto-generated content.
Suggestions
Add concrete action verbs 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 with trigger scenarios, e.g., 'Use when the user asks to create a design doc, technical specification, RFC, or architecture document'
Expand trigger term coverage to include natural variations: 'design document', 'tech spec', 'RFC', 'architecture doc', 'technical specification', 'system design'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Technical Documentation' and 'design doc template' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'creates', 'generates', 'structures', etc. | 1 / 3 |
Completeness | The 'what' is essentially missing - we don't know what this skill does beyond vaguely relating to design doc templates. The 'when' is weakly implied through trigger terms but not explicitly stated with a 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | Includes 'design doc template' as a trigger term which users might naturally say, but the term is duplicated and lacks variations users might use like 'technical design', 'architecture doc', 'design document', 'RFC', or 'spec template'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'design doc template' provides some specificity, but 'Technical Documentation' is broad and could overlap with other documentation skills. Without clear capability boundaries, it may conflict with general documentation or template skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill is an empty placeholder that provides zero actionable content about design doc templates. It consists entirely of generic boilerplate text that could apply to any skill topic, with no actual template, structure, examples, or guidance for creating design documents.
Suggestions
Add an actual design doc template with sections (Problem Statement, Proposed Solution, Alternatives Considered, Technical Design, etc.) that Claude can use directly
Include a concrete example of a filled-out design doc to demonstrate the expected format and level of detail
Provide specific guidance on when to use different sections and what content belongs in each
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with actionable instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about design doc templates. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no template structure, no examples, no code, no specific instructions. The skill describes what it claims to do rather than actually providing any actionable content for creating design docs. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no process, no validation checkpoints. The content merely lists vague 'capabilities' without explaining how to actually create or use a design doc template. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed materials, no examples file, no actual template file. The content is a shallow placeholder with no depth or navigation to useful resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.