agentleFS
opencueopencue/cuecards/.agents/skills/rank-tracker/SKILL.md

rank-tracker

Skill6 starsChanged 3 months agoMITView on GitHub

Use when the user asks to "track rankings"; monitors keyword/SERP changes from provided exports or connected tools, including AI response checks. 排名追踪/SERP监控

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All integrations optional (see CONNECTORS.md).

    line 90
  2. Distinctive:

    When a user requests rank tracking or analysis:

    line 94
  3. Very specific:

    Ask "Save these results?" If yes, write memory/monitoring/YYYY-MM-DD-<topic>.md with headline finding, actions, and open loops.

    line 130

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Rank Tracker

Tracks keyword positions, SERP feature ownership, and AI visibility over time.

Quick Start

Set up rank tracking for [domain] targeting these keywords: [keyword list]
Analyze ranking changes for [domain] over the past [time period]

Skill Contract

Expected output: a ranking report or delta summary plus the standard handoff summary for memory/monitoring/.

  • Reads: current metrics, baselines, alert thresholds, and reporting context from AGENTS.md and the shared State Model when available.
  • Writes: a user-facing monitoring deliverable and reusable summary.
  • Promotes: significant changes, confirmed anomalies, follow-up actions, and pending decisions to memory/open-loops.md.
  • Primary next skill: alert-manager when recurring monitoring should become automated.

Handoff Summary

Emit the standard shape from skill-contract.md §Handoff Summary Format.

Data Sources

All integrations optional (see CONNECTORS.md). With tools, pull rankings from ~~SEO tool, impressions from ~~search console, traffic from ~~analytics, and AI citations from ~~AI monitor. Without tools, ask for positions, volumes, competitor data, and SERP feature status.

Instructions

When a user requests rank tracking or analysis:

  1. Set Up Keyword Tracking — configure domain, market, device, language, update frequency, priorities, and competitor watchlist.
  2. Record Current Rankings — summarize position ranges, detailed rankings, ranking URLs, feature ownership, and movement.
  3. Analyze Ranking Changes — highlight biggest wins, declines, stable terms, new rankings, lost rankings, likely causes, and recovery ideas.
  4. Track SERP Features — compare ownership of snippets, PAA, image/video packs, local packs, and related feature shifts.
  5. Track GEO / AI Visibility — monitor AI Overview presence, citation rate, citation position, and trend.
  6. Compare Against Competitors — report share of voice, head-to-head comparisons, and threat levels.
  7. Generate Ranking Report — summarize overall trend, key wins, concerns, opportunities, SERP feature changes, GEO visibility, and recommendations.

Reference: See references/ranking-analysis-templates.md for the complete output templates for all seven steps.

Example

Sample outcome: average position improves from 15.3 to 12.8, top-10 keywords rise from 12 to 17, and the report highlights the biggest winners, biggest drops, and next actions.

Tips for Success

Track consistently, segment by intent, watch competitors, and include SERP feature plus GEO signals.

Rank Change Quick Reference

Response Protocol

ChangeTimeframeAction
Drop 1-3 positionsWait 1-2 weeksMonitor — may be normal fluctuation
Drop 3-5 positionsInvestigate within 1 weekCheck technical issues and competitor changes
Drop 5-10 positionsInvestigate immediatelyRun a full diagnostic: technical, content, links
Drop off page 1Emergency responseComprehensive audit + recovery plan
Position gainedDocument and learnIdentify what worked and replicate

Reference: See references/tracking-setup-guide.md for tracking setup, root-cause taxonomy, CTR benchmarks, SERP feature impact, and algorithm-update assessment.

Save Results

Ask "Save these results?" If yes, write memory/monitoring/YYYY-MM-DD-<topic>.md with headline finding, actions, and open loops.

Reference Materials

Next Best Skill

Initial setup (no baseline) → alert-manager. Subsequent runs (baseline exists) → Terminal. Visited-set rule applies per skill-contract.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.