CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

content-gap-analysis

Use when the user asks to "find content gaps", "竞品写了什么", or "还应该写什么"; builds a competitor-relative coverage map of missing topics, keyword gaps, and editorial-calendar opportunities. Not for raw keyword demand discovery — use keyword-research. 内容缺口/选题规划

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-structured, lean instruction skill: concrete connector commands, explicit decision gates, a done-when checklist, and real one-level-deep reference files carrying the templates and worked example. The main improvement space is de-duplicating repeated links/sections, adding an explicit output-verification step, and making the external repo-relative references more self-contained.

Suggestions

Consolidate reference links: remove the duplicate Analysis Templates and Example Report links in 'Reference Materials' (or keep only that section and drop the inline ones) so each file is linked exactly once.

Add an explicit verification step after step 9 (e.g., 'Before delivering, re-check every gap entry names its competitor, its volume/traffic estimate, and its bucket') to close the workflow's validation loop.

Merge the 'Save Results' section with the Skill Contract's memory-promotion bullet to eliminate the repeated hot-cache/research-path guidance, or state the write path once with a pointer.

DimensionReasoningScore

Conciseness

The body is lean — one-line instruction steps, no explanations of concepts Claude already knows, and dense sections like Decision Gates and the quality bar. Minor trimmable redundancy remains: "Save Results" repeats the memory-promotion already stated in Skill Contract, and "Reference Materials" repeats links given inline earlier. Anchor 4 fits: efficient with minor instances that could be trimmed; anchor 5 would require every section to be irreducible.

4 / 5

Actionability

Concrete, executable commands are present (e.g., `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/firecrawl.py" map <competitor-domain> --search "<topic>" --limit 1000`) alongside a concrete "Done when" checklist and sample prompts. The 9 core steps are terse one-line directives whose executable detail is deferred to the referenced templates, which keeps them just short of fully copy-paste-ready.

4 / 5

Workflow Clarity

Nine clearly sequenced steps, explicit stop-and-ask / continue-silently decision gates, a "Done when" checklist, and a Measured/User-provided/Estimated/N/A provenance rule provide strong checkpoints. Not a batch or destructive skill, so no cap applies; an explicit post-draft verification loop is the missing piece versus anchor 5.

4 / 5

Progressive Disclosure

All three referenced bundle files (references/analysis-templates.md, references/gap-analysis-frameworks.md, references/example-report.md) exist, are one level deep, and each carries a clear purpose label; the body works as an overview. Minor gaps: the Reference Materials section duplicates two links already given inline, and several paths (../../../CONNECTORS.md, ../../../references/skill-contract.md, ../../../SECURITY.md, ../../implement/content-writer/SKILL.md) resolve outside this bundle.

4 / 5

Total

16

/

20

Passed

Description

87%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.

A strong description with explicit third-person capability statements, natural multilingual trigger phrases, and an explicit de-scoping clause against keyword-research. Its only weakness is trigger synonym coverage and slight under-reporting of what the skill's workflow actually produces.

DimensionReasoningScore

Specificity

"builds a competitor-relative coverage map of missing topics, keyword gaps, and editorial-calendar opportunities" names several concrete outputs in third person, but omits parts of the skill's coverage (prioritization, competitor audit), matching anchor 4 rather than the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both questions: "builds a competitor-relative coverage map of missing topics, keyword gaps, and editorial-calendar opportunities" (what) and "Use when the user asks to 'find content gaps'..." with concrete trigger phrases (when), plus an explicit negative boundary.

5 / 5

Trigger Term Quality

Triggers "find content gaps", "竞品写了什么", and "还应该写什么" are natural user phrases, but common English variations such as "what content am I missing" or "competitor analysis" are absent, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear competitor-relative niche with distinct triggers, and "Not for raw keyword demand discovery — use keyword-research" explicitly disambiguates the closest neighboring skill, minimizing conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 10 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 missing, 2 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

seo-geo/survey/content-gap-analysis/SKILL.md

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.