CtrlK
BlogDocsLog inGet started
Tessl Logo

rank-tracker

Track keyword rankings and SERP feature changes in traditional search and AI responses over time. 排名追踪/SERP监控

57

Quality

67%

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 ./.cursor/skills/rank-tracker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is well-organized and actionable, with a clear sequenced workflow, validation checklists, a worked example, and clean one-level-deep references to real bundle files; its main weakness is conciseness redundancy between the overview and instructions sections.

Suggestions

Merge or remove the duplicated trigger-intro sentences in "When This Must Trigger" (the two consecutive "Use this when…/Use this whenever…" lines).

Drop the "What This Skill Does" 7-item list since the "Instructions" 7-step list covers the same ground, or repurpose it as a one-line summary.

Tighten the "Data Sources" section, which repeats the optional-integrations note across two blockquotes and a bulleted manual list.

DimensionReasoningScore

Conciseness

Mostly efficient and well-structured, but it includes redundancy — two back-to-back overlapping trigger-intro sentences and a "What This Skill Does" 7-item list that restates the later 7-step "Instructions" — so it could be tightened rather than earning the lean anchor 3.

2 / 3

Actionability

For an instruction/analysis skill it gives concrete 7-step specifications, a complete worked example output with real markdown tables, and a rank-change response-protocol table, with full templates deferred to references — fully actionable guidance.

3 / 3

Workflow Clarity

A clear 7-step numbered sequence is paired with explicit Input Validation and Output Validation checklists; no destructive/batch operations are involved, so the missing-feedback-loop cap does not apply and it matches the checklists-for-complex-processes anchor 3.

3 / 3

Progressive Disclosure

The body is an overview with well-signaled, one-level-deep references to two real local files (ranking-analysis-templates.md, tracking-setup-guide.md) plus clearly separated external repo links, giving easy navigation and matching the clear-overview anchor 3.

3 / 3

Total

11

/

12

Passed

Description

50%

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 specific to its niche and bilingual, but it stops at anchor 2 across the board: it lacks a "Use when…" trigger clause, offers only a couple of actions, and carries modest overlap risk within a large SEO skill family.

Suggestions

Add an explicit "Use when…" clause naming triggering situations (e.g., "Use when tracking keyword positions over time or detecting ranking drops") to lift completeness to 3.

Expand the action list beyond "track…changes" to concrete verbs (e.g., record, compare, alert, report) to improve specificity.

Add more natural user-phrased trigger variations ("keyword positions", "where do I rank", "ranking changes") alongside the existing terms.

DimensionReasoningScore

Specificity

Names the domain and a couple of concrete actions ("Track keyword rankings and SERP feature changes"), but it is not a comprehensive list of multiple distinct actions, so it sits at anchor 2 rather than 3.

2 / 3

Completeness

The description answers "what" clearly but contains no "Use when…" clause; per the rubric guideline a missing explicit trigger caps completeness at 2, and it is not 1 because the what is concrete.

2 / 3

Trigger Term Quality

Relevant natural terms appear ("keyword rankings", plus multilingual "排名追踪/SERP监控"), but "SERP feature" is jargon-leaning and common variations like "keyword positions" or "where do I rank" are absent from the description.

2 / 3

Distinctiveness Conflict Risk

Rank tracking plus GEO/AI monitoring is a recognizable niche, but within a 20-skill SEO library the phrase "track keyword rankings" could still overlap with sibling SEO skills, matching the somewhat-specific anchor 2.

2 / 3

Total

8

/

12

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

16

Passed

Repository
MODSetter/SurfSense
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.