architecture-doc-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill architecture-doc-creatorArchitecture Doc Creator - Auto-activating skill for Technical Documentation. Triggers on: architecture doc creator, architecture doc creator Part of the Technical Documentation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting primarily of the skill name repeated as trigger terms with no actual capability description. It fails to explain what the skill does, when to use it, or provide natural language triggers that users would actually say. The description appears to be auto-generated boilerplate rather than a thoughtful skill description.
Suggestions
Add specific concrete actions the skill performs, such as 'Generates system architecture diagrams, documents component relationships, creates API documentation, and produces technical design specifications'.
Replace the duplicate trigger terms with natural user phrases like 'document my architecture', 'system design docs', 'technical documentation', 'component diagram', 'design document'.
Add an explicit 'Use when...' clause describing scenarios like 'Use when the user needs to document system architecture, create technical design documents, or visualize component relationships'.
| 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 API specifications'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the generic title, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than describing actual use cases. | 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', 'technical architecture', 'document my codebase', or 'architecture diagram' is included. | 1 / 3 |
Distinctiveness Conflict Risk | While 'architecture doc' provides some specificity within the documentation domain, the lack of concrete details means it could overlap with general documentation skills, code documentation tools, or diagram generators. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about architecture documentation. It contains only generic boilerplate text that could apply to any skill topic, providing zero actionable guidance on creating architecture docs, no examples, no templates, and no workflows.
Suggestions
Add concrete templates or examples of architecture documentation (e.g., C4 diagrams, ADRs, system context diagrams) with actual content Claude can use
Define a clear workflow for creating architecture docs: gather requirements → identify components → document decisions → create diagrams → validate completeness
Include specific code/tool examples such as Mermaid diagram syntax, PlantUML templates, or markdown structures for common architecture doc sections
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with specific, actionable instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about architecture documentation. 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 code, no commands, no templates, no examples of actual architecture documentation. The 'Capabilities' section describes what it claims to do but provides zero executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for creating architecture documentation, no validation checkpoints, and no process to follow. The content is entirely descriptive rather than procedural. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed materials, templates, or examples. The content is a shallow placeholder with no depth or navigation to additional 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.