technical-specification
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill technical-specification93
Quality
89%
Does it follow best practices?
Impact
100%
1.21xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/technical-specification/skills/technical-specification/SKILL.mdDiscovery
92%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 well-crafted skill description that clearly articulates specific capabilities and includes explicit trigger guidance. The description uses proper third-person voice and covers concrete deliverables. Minor weakness is potential overlap with general documentation or planning skills due to some broader trigger terms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'requirements, architecture, APIs, and testing strategies' - these are distinct, concrete deliverables rather than vague language. | 3 / 3 |
Completeness | Clearly answers both what ('Creates detailed technical specifications...covering requirements, architecture, APIs, and testing strategies') AND when ('Use when planning features, documenting system design, or creating architecture decision records'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'technical specifications', 'planning features', 'system design', 'architecture decision records' - these are terms developers naturally use when requesting this type of work. | 3 / 3 |
Distinctiveness Conflict Risk | While 'technical specifications' and 'architecture decision records' are fairly specific, terms like 'planning features' and 'system design' could overlap with general project planning or documentation skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong skill with excellent actionability and conciseness. The template is immediately usable with concrete examples and specific metrics. The main weakness is the lack of explicit workflow guidance for the spec creation/review process itself, though for a template-focused skill this is a minor gap.
Suggestions
Add a brief workflow section (3-5 lines) describing the spec creation process: draft → internal review → stakeholder review → approval, with checkpoints for when to proceed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing a complete template without unnecessary explanation. It assumes Claude understands what technical specifications are and jumps directly into actionable structure. | 3 / 3 |
Actionability | Provides a fully copy-paste ready template with concrete examples including SQL schemas, API request/response formats, and specific metrics (200ms, 99.9% uptime). The tables and code blocks are immediately usable. | 3 / 3 |
Workflow Clarity | While the template includes an implementation plan with phases, there are no explicit validation checkpoints or feedback loops for the spec creation process itself. Missing guidance on when to validate the spec or iterate based on review feedback. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise inline template for quick use, then clear reference to a comprehensive template in references/template.md for advanced needs. One-level-deep reference is well-signaled with a clear list of what the full template contains. | 3 / 3 |
Total | 11 / 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.
- 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.