CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

keyword-mapping

Maps keyword clusters to existing website assets and recommends reuse, improvement, consolidation review or a new page.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/keyword-mapping/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body is an exemplary lean instruction-only skill: concrete decision rules, a specified output schema, and explicit verification checkpoints with no wasted tokens. Its main gaps are high-level mechanics for URL acquisition and page verification, and a lack of headers or lists that would make the decision rules easier to scan.

Suggestions

Add a short worked example of one cluster mapped to a URL with action and rationale so the output format is unambiguous.

Break the decision rules in the second paragraph into a bulleted list (Reuse when... / Improve when... / New page only when...) for scannability.

Briefly specify what 'open the page to verify' should check (e.g., supported action, search intent match, internal linking) or point to where that checklist lives.

DimensionReasoningScore

Conciseness

At roughly 230 words the body is lean and assumes Claude's competence, with zero padding or explanation of known concepts ('Defer unsupported or uncertain tasks', 'Keep redirects, publishing and content production as separate decisions'). Every sentence carries decision-relevant instruction, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Decision rules are concrete and conditional ('Recommend a new page only for a distinct supported task with no adequate asset') and the output format is specified field-by-field ('cluster, current URL (or proposed asset type), action, rationale and required verification'). Not score 5 because some mechanics remain high-level, e.g. how to obtain candidate URLs from 'a sitemap, navigation, crawl or user inventory' and what page verification should concretely check.

4 / 5

Workflow Clarity

The sequence is clear across paragraphs (inputs -> candidate URLs -> open and verify pages -> decide -> return map) with checkpoints present ('Open the page to verify the action it supports', 'If inventory is incomplete, mark coverage unknown'). Not score 5 because there is no explicit error-recovery or re-verification loop, only the single incomplete-inventory conditional; not score 3 because validation checkpoints are explicitly stated rather than missing.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files, ordered logical paragraphs, and one clearly signaled conditional reference to the site-structure-inventory skill. Not score 5 because there are no section headers and the dense paragraphs (especially the decision rules) are less scannable than well-organized sections; not score 3 because nothing that belongs in a separate file is inlined and the single reference is clearly signaled with its trigger condition.

4 / 5

Total

17

/

20

Passed

Description

58%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 names a clear niche and several concrete recommendation actions, but it entirely lacks a 'when to use' trigger clause, which both limits discoverability and caps completeness. Adding natural trigger phrases would resolve the main weaknesses.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases such as 'Use when doing keyword research, SEO content planning, or deciding whether a keyword needs a new page versus an existing one.'

Include common user vocabulary and synonyms (SEO, keyword research, content audit, search intent mapping) to improve trigger term coverage.

Briefly state the output (e.g., 'Returns a cluster-to-URL map with an action and rationale per cluster') to round out the 'what' side of the description.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('maps keyword clusters to existing website assets and recommends reuse, improvement, consolidation review or a new page'), with minor gaps such as inputs and outputs left unspecified. It lists multiple specific actions but not at the comprehensive enumeration level of the 5 anchor.

4 / 5

Completeness

Has a clear 'what' (mapping keyword clusters to assets and recommending an action) but no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not score 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

'Keyword clusters' is a relevant natural term, but common user phrasings like 'SEO', 'keyword research', or 'content planning' are missing. Not score 2 because the language is domain-specific rather than generic; not score 4 because most natural trigger variations are absent.

3 / 5

Distinctiveness Conflict Risk

'Keyword clusters', 'website assets', and 'consolidation review' establish a fairly distinct SEO-mapping niche with low conflict risk. Not score 5 because without explicit triggers it could still overlap with general content-audit or SEO skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

kostja94/marketing-skills

Path

skills/keyword-mapping/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.