analyze-content-gaps

Identify content gaps and organizational opportunities. Analyzes missing content areas, redundancies, and consolidation opportunities.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/analyze-content-gaps/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a well-structured, concise instruction-only workflow for content gap analysis with clear sequencing and outputs. Its main weakness is actionability: the analysis and prioritization steps stay at a framework level without a concrete method to execute them.

Suggestions

Replace 'Prioritize gaps based on impact and effort' with a concrete scoring rubric (e.g., impact 1-3 x effort 1-3) so Claude can produce a ranked roadmap.

Specify how to obtain and weight user-need signals (e.g., ticket volume, search-query frequency) rather than just listing sources.

Tighten or remove the Quick Reference section since Purpose and Outcome duplicate the opening paragraph.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not explain concepts Claude already knows; the only trimming opportunity is the Quick Reference section, which restates Purpose and Outcome already covered by the intro.	4 / 5
Actionability	Concrete inputs and gap categories (Missing/Thin/Redundant/Outdated) give a usable framework, but prioritization guidance stays abstract ('Prioritize gaps based on impact and effort') with no method or rubric to execute.	3 / 5
Workflow Clarity	A clear four-step sequence (Baseline → Needs → Gaps → Recommendations) with well-defined sub-items; being a read-only analysis it needs no validation checkpoints, so the destructive-operation cap does not apply.	4 / 5
Progressive Disclosure	Under 50 lines with no bundle files and no need for external references; sections (Inputs, Workflow, Required Outputs, Quick Reference) are well-organized, satisfying the simple-skill exception.	5 / 5
	Total	16 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 states a clear purpose and niche in third person but omits any explicit 'Use when...' trigger guidance, leaving the 'when' half of completeness unanswered. It is serviceable yet reads more like a tagline than a trigger-rich invocation.

Suggestions

Add a 'Use when...' clause naming concrete trigger phrases users would actually say, e.g. 'Use when auditing a documentation set for missing, thin, or redundant pages.'

Swap 'organizational opportunities' for a concrete action verb phrase to lift specificity.

Include natural synonyms or artifacts (e.g., 'content audit', 'doc coverage', 'gap analysis') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the content-gap domain and several action targets ('missing content areas, redundancies, and consolidation opportunities'), but 'organizational opportunities' stays abstract, so coverage is not comprehensive.	3 / 5
Completeness	The 'what' is clear, but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant domain keywords appear (content gaps, redundancies, consolidation) but natural user phrasings like 'what content am I missing' or 'find gaps in my docs' and synonyms are absent.	3 / 5
Distinctiveness Conflict Risk	Content gap analysis is a clear niche with low conflict risk, though it could overlap slightly with general documentation-audit or content-strategy skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: dandye/ai-runbooks
Path: skills/analyze-content-gaps/SKILL.md
Commit: 72a6863

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.