architecture-doc-creator
Architecture Doc Creator - Auto-activating skill for Technical Documentation. Triggers on: architecture doc creator, architecture doc creator Part of the Technical Documentation skill category.
35
Quality
3%
Does it follow best practices?
Impact
93%
1.01xAverage 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/architecture-doc-creator/SKILL.mdQuality
Discovery
7%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 placeholder with no substantive content. It repeats the skill name as trigger terms, provides no concrete actions or capabilities, and offers no meaningful guidance for when Claude should select this skill. The description fails on all core dimensions needed for effective skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates architecture decision records (ADRs), generates system diagrams, documents component relationships and dependencies'
Replace the redundant trigger terms with natural user language like 'system architecture', 'technical design doc', 'ADR', 'component diagram', 'system documentation'
Add an explicit 'Use when...' clause describing scenarios, e.g., 'Use when the user needs to document system architecture, create design documents, or record architectural decisions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Architecture Doc Creator') without describing any concrete actions. There are no specific capabilities listed like 'generates diagrams', 'documents system components', or 'creates architecture decision records'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague category label, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('architecture doc creator, architecture doc creator'). No natural user language like 'system design', 'architecture diagram', 'technical documentation', or 'ADR' is included. | 1 / 3 |
Distinctiveness Conflict Risk | While 'architecture doc' provides some specificity within the documentation domain, the lack of concrete actions means it could overlap with general documentation skills or diagram creation skills. | 2 / 3 |
Total | 5 / 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 an empty template with no actual content. It contains only generic placeholder text that describes what a skill should do without providing any concrete guidance, examples, or actionable instructions for creating architecture documentation. The content adds nothing to Claude's capabilities.
Suggestions
Add concrete examples of architecture document structures (e.g., C4 model diagrams, system context, component diagrams) with actual templates or code blocks
Include a step-by-step workflow for creating architecture docs: gather requirements → identify components → document relationships → validate completeness
Provide executable examples such as Mermaid diagram syntax, PlantUML templates, or markdown structure for common architecture doc sections
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with specific, actionable guidance
| 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 explained. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no specific commands, and no actual instructions for creating architecture documentation. The content only describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined whatsoever. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials, no references to other files, and no organization beyond superficial section headers. | 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.