sdk-documentation-generator
Sdk Documentation Generator - Auto-activating skill for Technical Documentation. Triggers on: sdk documentation generator, sdk documentation generator Part of the Technical Documentation skill category.
33
Quality
0%
Does it follow best practices?
Impact
97%
0.98xAverage 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/sdk-documentation-generator/SKILL.mdQuality
Discovery
0%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 triggers, provides no concrete actions or capabilities, lacks any 'Use when' guidance, and would be indistinguishable from other documentation skills. Claude would have no basis to select this skill appropriately.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates SDK reference documentation, creates code examples in multiple languages, produces quickstart guides and API endpoint descriptions.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user needs SDK docs, API documentation, library references, developer guides, or mentions generating documentation for code libraries.'
Differentiate from general documentation skills by specifying the SDK/developer focus: 'Specifically for software development kit documentation including method signatures, parameter descriptions, and integration examples.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the skill name repeated. 'Sdk Documentation Generator' names a domain but provides zero information about what specific actions it performs (e.g., generate API docs, create code examples, format reference pages). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill name repeated twice ('sdk documentation generator'). No natural user keywords like 'API docs', 'library documentation', 'code reference', or 'developer docs' are included. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'Technical Documentation' is extremely generic and would conflict with any documentation-related skill. Nothing distinguishes SDK documentation from API docs, user guides, or other technical writing skills. | 1 / 3 |
Total | 4 / 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 could apply to any skill, with no specific guidance on SDK documentation generation. The skill fails on all dimensions because it provides no actionable information, no examples, and no concrete instructions.
Suggestions
Add concrete, executable examples showing how to generate SDK documentation (e.g., using tools like Sphinx, TypeDoc, or Doxygen with actual code snippets)
Define a clear workflow with specific steps: analyze SDK structure, extract API signatures, generate documentation, validate output
Include specific output formats and templates for SDK documentation (e.g., method signatures, parameter tables, code examples)
Remove all generic boilerplate text and replace with domain-specific guidance that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about SDK documentation generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual documentation generation steps. The content only describes what the skill supposedly does without providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. 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 flat, uninformative structure with no references to detailed materials, no links to examples, and no organization beyond generic section headers that contain no useful content. | 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.