CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rank-tracker

Use when the user asks to "track rankings" or "查排名"; measures keyword and SERP-position deltas over time from provided exports or connected tools, including AI-response checks. Not for multi-metric stakeholder reports or setting alerts — use performance-monitor (report or alert mode). 排名追踪/SERP监控

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

81%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 tightly engineered, contract-style body: lean prose, executable ledger commands, threshold tables, and a well-gated seven-step workflow with genuine validation checkpoints. The gaps are operational rather than structural — several referenced files (scripts/connectors, cross-skill contracts) are missing from the bundle as shipped, and a redundant reference section costs a few tokens.

Suggestions

Ship or stub the referenced scripts/connectors/ledger.py and scripts/connectors/README.md inside the bundle (or remove the zero-dependency ledger loop from the body) so the copy-paste commands actually resolve.

Drop the standalone 'Reference Materials' section and consolidate the three inline citations of tracking-setup-guide / the evidence profile into one place to remove redundancy.

Verify the out-of-bundle cross-references (../../../references/skill-contract.md, ../../../CONNECTORS.md, ../performance-monitor/SKILL.md) resolve from the skill's installed location, since three of them are load-bearing for the handoff and save-results steps.

DimensionReasoningScore

Conciseness

The body is dense and lean — contract-style tables, labeled lists, and exact commands with zero explanation of concepts Claude already knows (no SEO primer, no library overviews). Not 5 because of minor redundancy: the 'Reference Materials' section repeats the tracking-setup-guide and evidence-profile links already cited inline, and the performance-monitor link appears in three places.

4 / 5

Actionability

Gives copy-paste-ready commands (`python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/ledger.py" record <domain> --source rank --data '{...}'` plus diff/trend invocations), concrete Quick Start invocations, and a threshold decision table (drop 1-3 → wait 1-2 weeks, etc.). Not 5 because several executable targets are absent from the actual bundle — the referenced scripts/connectors/ledger.py, scripts/connectors/README.md, and the cross-skill evidence-and-cycle-control profile do not resolve — leaving the ledger loop and step 1 partially unexecutable as shipped here.

4 / 5

Workflow Clarity

Seven clearly sequenced steps (setup → record → analyze → features → GEO → competitors → report) wrapped in explicit validation scaffolding: Decision Gates with stop-and-ask options and silent-continue rules, a 'Done when' checklist, evidence labels (Measured/User-provided/Calculated/Estimated/Proxy/Unknown), and NEEDS_REFRESH staleness handling — feedback loops for every ambiguity the workflow can hit.

5 / 5

Progressive Disclosure

The two in-bundle references (references/ranking-analysis-templates.md, references/tracking-setup-guide.md) exist, are one level deep, and are clearly signaled with purpose statements ('complete output templates for all seven steps'; 'tracking setup, root-cause taxonomy, CTR benchmarks'), keeping the body an overview. Not 5 because numerous referenced paths do not resolve within the bundle (../../../references/skill-contract.md cited three times, ../../../CONNECTORS.md, ../performance-monitor/..., scripts/connectors/*), and the duplicate Reference Materials section adds mild navigation noise.

4 / 5

Total

17

/

20

Passed

Description

80%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 well-constructed description with explicit what/when structure, quoted bilingual triggers, and an unusually strong negative boundary routing a sibling skill's territory to performance-monitor. The main weakness is thin trigger-term coverage: only one natural English phrase plus its Chinese equivalent, leaving common variations ('monitor rankings', 'SERP tracking', 'keyword positions') unclaimed.

Suggestions

Add natural trigger variations to the 'Use when' clause — e.g. 'track rankings', 'monitor keyword positions', 'SERP tracking', 'ranking changes or drops' — so users phrasing the need differently still surface this skill.

Optionally name one or two more concrete capabilities (SERP feature ownership, competitor share-of-voice) to round out the what-clause beyond delta measurement.

DimensionReasoningScore

Specificity

Names concrete capabilities — "measures keyword and SERP-position deltas over time from provided exports or connected tools, including AI-response checks" — listing several specific measurement actions. Not 5 because coverage stays within a single 'measures deltas' verb family and omits actions the skill body actually covers (SERP feature ownership, competitor comparison); not 3 because more than 1-2 distinct concrete actions are explicitly stated.

4 / 5

Completeness

Explicitly answers both parts: what ("measures keyword and SERP-position deltas over time from provided exports or connected tools, including AI-response checks") and when ("Use when the user asks to 'track rankings' or '查排名'") with concrete quoted trigger phrases, plus an exclusion clause. This matches the anchor-5 pattern of concrete triggers for both what and when.

5 / 5

Trigger Term Quality

The quoted triggers "track rankings" and "查排名" are natural phrases a user would say, supplemented by "排名追踪/SERP监控". Not 4 because common variations and synonyms are missing — no 'keyword rankings', 'SERP tracking', 'monitor rankings', 'position tracking', or 'ranking changes/drops' as trigger phrasings; not 2 because the existing triggers are genuinely natural rather than generic jargon.

3 / 5

Distinctiveness Conflict Risk

Clear niche (keyword/SERP position delta tracking) with a distinct, narrow trigger set, and the negative boundary "Not for multi-metric stakeholder reports or setting alerts — use performance-monitor (report or alert mode)" explicitly de-conflicts against the one closely related sibling skill. Conflict risk is actively minimized, matching or exceeding the anchor-5 example.

5 / 5

Total

17

/

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, 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

seo-geo/evaluate/rank-tracker/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.