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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill sdk-documentation-generatorOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no substantive content. It lacks any concrete actions, natural trigger terms, explicit usage guidance, and distinguishing characteristics. The repeated trigger term and generic category label provide no useful information for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates API reference documentation, creates code examples, formats SDK guides with proper syntax highlighting'
Include a 'Use when...' clause with natural trigger terms users would say, e.g., 'Use when the user asks for API docs, SDK documentation, library references, developer guides, or code documentation'
Specify what types of SDKs or programming languages this skill handles to distinguish it from general documentation skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Sdk Documentation Generator' and 'Auto-activating skill for Technical Documentation' are abstract labels without any explanation of what the skill actually does (e.g., generates API references, creates code examples, formats documentation). | 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 explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'sdk documentation generator' repeated twice, which is technical jargon users are unlikely to naturally say. Missing common variations like 'API docs', 'library documentation', 'code documentation', 'developer docs', or 'reference guide'. | 1 / 3 |
Distinctiveness Conflict Risk | 'Technical Documentation' is extremely generic and could conflict with many documentation-related skills. There are no distinguishing features that would help Claude select this skill over other documentation or writing skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill content is essentially an empty template with no actual instructional value. It describes what an SDK documentation generator skill might do but provides absolutely no concrete guidance, code examples, or actionable steps. The content fails on every dimension by being verbose yet content-free.
Suggestions
Add concrete, executable code examples showing how to generate SDK documentation (e.g., using tools like Sphinx, TypeDoc, or custom scripts)
Define a clear workflow with specific steps: analyze SDK structure → extract API signatures → generate documentation → validate output
Include specific input/output examples showing what SDK code looks like and what the generated documentation should contain
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual technical instructions
| 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. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual instructions on how to generate SDK documentation. The content only describes what the skill supposedly does without showing how. | 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 monolithic block of vague descriptions with no references to detailed materials, no links to examples, and no structured 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.