Identify content gaps and organizational opportunities. Analyzes missing content areas, redundancies, and consolidation opportunities.
49
37%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/analyze-content-gaps/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description provides a reasonable overview of the skill's analytical capabilities but suffers from lack of explicit trigger guidance and insufficient specificity. It would benefit significantly from a 'Use when...' clause and more concrete action verbs to help Claude distinguish this skill from other content or documentation-related skills.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about missing documentation, duplicate content, content audit, or wants to reorganize/consolidate materials'
Include more specific concrete actions such as 'generates gap analysis reports', 'identifies duplicate sections', 'recommends content merges'
Add natural user terms like 'duplicate', 'overlap', 'what's missing', 'audit', 'reorganize' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (content analysis) and some actions ('Analyzes missing content areas, redundancies, and consolidation opportunities'), but lacks concrete specific actions like 'generates gap reports' or 'creates consolidation plans'. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also somewhat weak. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'content gaps', 'redundancies', 'consolidation', but missing common user phrases like 'duplicate content', 'what's missing', 'overlap', 'reorganize', or file type references. | 2 / 3 |
Distinctiveness Conflict Risk | The terms 'content gaps' and 'organizational opportunities' are somewhat specific but could overlap with documentation skills, content strategy skills, or general analysis skills without clearer domain boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable conceptual framework for content gap analysis but lacks the concrete, actionable guidance needed for execution. The workflow structure is clear but the actual techniques for performing each step are abstract descriptions rather than executable instructions. The skill tells Claude what to analyze but not how to analyze it.
Suggestions
Add concrete examples of how to identify gaps - e.g., specific patterns to search for, sample queries to run, or heuristics for detecting thin content
Include a sample output format showing what a GAP_ANALYSIS_REPORT should look like with example entries
Provide specific criteria or thresholds for categorizing content as 'thin' vs 'adequate' vs 'comprehensive'
Add validation steps - e.g., 'Verify at least 3 sources were consulted for needs analysis before proceeding to gap identification'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary structure like the 'Quick Reference' section that repeats information. The workflow steps could be more compact while retaining clarity. | 2 / 3 |
Actionability | The skill describes what to do at a high level but provides no concrete commands, code examples, or specific techniques for actually performing the analysis. Phrases like 'Analyze search logs' and 'Compare against competitor documentation' are vague without executable guidance. | 1 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-4) with logical progression, but there are no validation checkpoints or feedback loops. No guidance on how to verify the analysis is complete or accurate before proceeding to recommendations. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~60 lines), the structure is appropriate with clear sections. No unnecessary nesting or references to external files that would complicate navigation. Content is well-organized into logical sections. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
4d132c7
Table of Contents
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.