jsdoc-comment-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill jsdoc-comment-generatorJsdoc Comment Generator - Auto-activating skill for Technical Documentation. Triggers on: jsdoc comment generator, jsdoc comment generator 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 only of a skill name, duplicate trigger terms, and a category label. It provides no information about what the skill actually does, what specific capabilities it offers, or when Claude should select it. The description would be nearly useless for skill selection among multiple options.
Suggestions
Add specific capabilities: 'Generates JSDoc comments for JavaScript/TypeScript functions, classes, and modules including @param, @returns, @throws, and @example annotations.'
Add explicit trigger guidance: 'Use when the user asks to document JavaScript code, add JSDoc comments, generate function documentation, or mentions @param/@returns annotations.'
Include natural trigger terms users would say: 'document this function', 'add comments to my code', 'JavaScript documentation', 'TypeScript docs', '.js files', '.ts files'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Jsdoc Comment Generator') and category ('Technical Documentation') without describing any concrete actions. No specific capabilities like 'generates JSDoc comments', 'documents function parameters', or 'creates type annotations' are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('jsdoc comment generator, jsdoc comment generator'). Missing natural variations users would say like 'document my code', 'add comments', 'function documentation', 'JavaScript docs', '@param', '@returns'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'JSDoc' is somewhat specific to JavaScript documentation, the generic 'Technical Documentation' category and lack of specific triggers could cause overlap with other documentation skills. The JSDoc mention provides some distinctiveness. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about JSDoc comment generation. It contains only generic boilerplate text that could apply to any skill, with no executable examples, no JSDoc syntax, no tag documentation, and no practical guidance whatsoever.
Suggestions
Add concrete JSDoc syntax examples showing @param, @returns, @typedef, @example and other common tags with proper formatting
Include executable code snippets showing before/after: a function without JSDoc and the same function with complete JSDoc comments
Provide a clear workflow: 1) Identify function signature, 2) Document parameters with types, 3) Document return value, 4) Add description and examples
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with actual JSDoc-specific content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about JSDoc. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance on how to generate JSDoc comments. No code examples, no syntax patterns, no actual JSDoc tags or formatting rules. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is provided. There are no steps for generating JSDoc comments, no validation approach, and no process to follow. The skill merely states it 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure for discovery. No references to detailed documentation, examples, or related resources. The sections present are organizational theater without substance. | 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.