CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-monitoring

Compatibility pointer for recurring SEO monitoring; maintained in Open Analytics.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/analytics/seo/seo-monitoring/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

As a relocation stub, the body is exemplary: lean, concrete, and unambiguous, with a direct link and an executable install command plus an honest disclaimer that no rules live here. The only minor gap is the absence of an explicit instruction for what Claude should do when the skill is invoked.

DimensionReasoningScore

Conciseness

The body is two sentences plus a heading with zero padding: it states where the maintained instructions live, gives the install command, and explicitly disclaims independent rules. Every token earns its place and it assumes Claude's competence, matching the top anchor.

5 / 5

Actionability

The body provides a concrete, copy-paste-ready install command (`npx skills add kostja94/open-analytics --skill seo-monitoring`) and a direct link to the maintained SKILL.md. It falls short of 5 only because it never explicitly instructs what Claude should do on invocation (fetch and follow the successor versus direct the user to install).

4 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines whose single action — redirect to the maintained instructions at the given URL/command — is unambiguous, so it qualifies for the simple-skill exception. No destructive or batch operations are involved, so no validation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/, scripts/, assets/ are absent) and is well organized as a heading plus one paragraph. Its single reference is an external URL that is clearly signaled and exactly one level deep, so nothing is nested or buried.

5 / 5

Total

19

/

20

Passed

Description

48%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 is honest and accurate for a relocated skill, clearly stating its pointer role and where maintenance continues, but it provides no capability description and no explicit trigger guidance. As a discovery description it is functional yet thin, leaving both completeness and trigger coverage below what the good examples demonstrate.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for recurring SEO monitoring, scheduled rank tracking, or periodic SEO checks' — the missing 'Use when' guidance currently caps completeness at 3.

Include natural synonyms users would say, such as 'rank tracking', 'SERP positions', or 'search rankings', to improve trigger-term coverage.

Briefly state what the skill covers (e.g., which monitoring rules or checks the successor performs) so the 'what' describes capabilities, not just the entry's pointer status.

DimensionReasoningScore

Specificity

The description names the domain ("recurring SEO monitoring") but the only stated action is being a "Compatibility pointer"; no concrete monitoring capabilities or actions are described. It is not a 1 because it is not pure abstraction — the pointer role and maintenance location are explicitly stated — and not a 3 because it lists no concrete actions of the skill itself.

2 / 5

Completeness

The 'what' is clear — this entry is a compatibility pointer with the maintained instructions elsewhere — but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is explicitly and accurately stated rather than vague.

3 / 5

Trigger Term Quality

"SEO monitoring" and "recurring" are relevant, natural keywords a user might say, but common variations and synonyms (e.g., rank tracking, SERP, search rankings) are absent. It sits between anchor 2 (only generic keywords) and anchor 4 (good coverage with a few missing), fitting anchor 3's 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

"SEO monitoring" names a clear, fairly distinct niche with minor overlap risk only against closely related analytics/marketing skills, matching 'mostly distinct; minor overlap risk'. It is not a 5 because no distinct trigger phrases are given, and not a 3 because 'SEO' is more specific than the broad domain examples at that anchor.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

kostja94/marketing-skills

Path

skills/analytics/seo/seo-monitoring/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.