rank-tracker

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

Quality

68%

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 ./.cursor/skills/rank-tracker/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 content is well-structured with actionable steps, explicit validation checklists, and real one-level-deep reference files. Its main weakness is mild verbosity and a duplicated trigger-clause sentence that could be trimmed for token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and actionable, but it contains redundancy — the 'When This Must Trigger' section opens with two overlapping sentences ('Use this when the conversation involves...' followed immediately by 'Use this whenever the task needs...') — plus some boilerplate that could be tightened.	3 / 5
Actionability	The 7-step instructions specify concrete deliverables (position ranges #1/#2-3/#4-10, SERP feature ownership tables, GEO citation rates) and the example output shows copy-ready markdown tables, with only minor gaps filled by the reference templates.	4 / 5
Workflow Clarity	A clear 7-step sequence is paired with explicit Input/Output validation checklists and a rank-change response protocol table, but the steps read more as a component checklist than a strict validate-fix-retry pipeline, leaving minor checkpoint gaps.	4 / 5
Progressive Disclosure	The body is a well-organized overview with clearly signaled, one-level-deep references to references/ranking-analysis-templates.md and references/tracking-setup-guide.md, both of which exist as real bundle files, making navigation easy.	5 / 5
	Total	16 / 20 Passed

Description

66%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 specific and bilingual with a clear niche, but it omits an explicit 'Use when...' trigger clause from the description field itself, which caps completeness. Trigger-term coverage is good but not exhaustive.

Suggestions

Append a 'Use when...' clause to the description field (e.g., 'Use when tracking keyword positions, monitoring SERP changes, or comparing ranking snapshots over time.') so trigger guidance lives inside description.

Add a few more natural trigger synonyms to the description such as 'position tracking' or 'where do I rank' to broaden keyword coverage.

Trim the bilingual tag ('排名追踪/SERP监控') or fold it into the when-clause to keep the description lean while preserving discoverability.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'Track keyword rankings and SERP feature changes in traditional search and AI responses over time' — covering rankings, SERP features, traditional search, AI/GEO, and time-series tracking, with only minor coverage gaps.	4 / 5
Completeness	The description clearly states what the skill does but contains no 'Use when...' trigger clause; per the judging guidelines, a missing explicit trigger guidance caps completeness at 3 even though a separate when_to_use field exists.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ('keyword rankings', 'SERP feature changes', 'AI responses') plus bilingual synonyms ('排名追踪/SERP监控'), but a few common variations like 'position tracking' or 'where do I rank' are absent from the description itself.	4 / 5
Distinctiveness Conflict Risk	The rank-tracking / SERP-monitoring niche is clearly distinct, but the description could overlap with other SEO/GEO skills in the same 20-skill library, leaving minor conflict risk.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: .cursor/skills/rank-tracker/SKILL.md
Commit: d96e29d

Reviewed: 8 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.