code-documentation-analyzer
Code Documentation Analyzer - Auto-activating skill for Technical Documentation. Triggers on: code documentation analyzer, code documentation analyzer Part of the Technical Documentation skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill code-documentation-analyzerOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no substantive content. It fails on all dimensions by providing only the skill name and a generic category without describing any capabilities, use cases, or natural trigger terms. The repeated trigger term is the skill's own name, which users would never naturally say.
Suggestions
Add specific actions the skill performs (e.g., 'Analyzes code comments, generates docstrings, evaluates documentation coverage, identifies undocumented functions').
Include a 'Use when...' clause with natural trigger terms like 'document my code', 'add docstrings', 'check documentation', 'README', 'API documentation', 'JSDoc', 'comments'.
Specify what types of code or documentation formats this handles (e.g., Python docstrings, JSDoc, markdown READMEs) to distinguish it from other documentation skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Code Documentation Analyzer' and category 'Technical Documentation'. There are no verbs describing what the skill actually does (e.g., generates, analyzes, extracts). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states the skill name and category without explaining capabilities or providing explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'code documentation analyzer' repeated twice, which is the skill's own name rather than natural keywords users would say. Missing terms like 'docstrings', 'API docs', 'comments', 'README', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'Technical Documentation' is extremely broad and could conflict with many documentation-related skills. No specific file types, formats, or unique capabilities are mentioned to distinguish this skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual content. It describes what a code documentation analyzer skill might do but provides zero actionable guidance, no examples, no code, and no concrete instructions for analyzing or generating code documentation.
Suggestions
Add concrete examples of code documentation analysis, such as extracting docstrings, identifying missing documentation, or generating documentation from code
Include executable code snippets showing how to parse and analyze documentation in common formats (JSDoc, docstrings, Javadoc, etc.)
Define a clear workflow for documentation analysis: e.g., 1) Scan codebase, 2) Identify undocumented functions, 3) Generate coverage report, 4) Suggest improvements
Replace generic capability descriptions with specific techniques and tools for documentation analysis
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | The skill contains zero concrete guidance, no code examples, no commands, and no specific instructions. It only describes what the skill supposedly does without showing how to actually analyze code documentation. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all. The content mentions 'step-by-step guidance' but provides none. No sequence of steps, no validation checkpoints, no actual process for analyzing code documentation. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples or advanced content, and no meaningful organization beyond generic section headers. | 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.