agentleFS
Sign inStart free
khadinakbarlabskhadinakbarlabs/vibeseo-plugin/skills/rank-tracking/SKILL.md

rank-tracking

Skill0 starsChanged 33 days agoMITView on GitHub

Establish or compare sampled Google keyword rankings using the owned Apify rank Actor or supplied snapshots. Use for keyword positions, rank baselines, competitor rank reviews and suspected ranking changes. Matches domain, keyword, geography, language, device, search depth and capture time; missing results are outside the sample or unknown, never rank zero.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. Ryze-AI-Adgent/open-seo-mcp-skills★ 8.4ksame name
    2. trysonar/skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Read shared rules, CLI guidance, and Actor contracts.

    line 8
  2. Very specific:

    Use supplied snapshots or plan keyword-rank-tracker with exact targetDomain, keywords, locationCode, languageCode, device, compatible os, …

    line 11

≈ “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

Comparable ranking snapshots

Read shared rules, CLI guidance, and Actor contracts.

  1. Reuse the target domain, exact keyword panel and requested market/device. Define what is being measured: organic position within an explicit search depth. No scheduled runs are created by this skill.
  2. Use supplied snapshots or plan keyword-rank-tracker with exact targetDomain, keywords, locationCode, languageCode, device, compatible os, small depth and maxKeywords. Check optional provider access. Approve the input/build/budget before starting.
  3. Collect the run and interpret its actual output shape. Save keyword, matched URL, sampled rank/null, source, market/device/depth, time and completeness. Distinguish organic rank from ads or unrelated SERP features. Don't reconstruct a position from arbitrary row order.
  4. Compare only equivalent panels: domain canonicalization, keyword, country/location, language, device, provider/method and depth. Retain new/removed keywords separately. Incompatible snapshots can be shown side by side but yield Not comparable for a change calculation.
  5. “Not found” means no match in the sampled depth or an unknown/failed capture as described by evidence. It isn't rank zero, deindexing, or proof of lost visibility. Within matched valid observations, calculate change with a documented sign convention: previous position minus current position; positive means a better numerical position.
  6. Report meaningful observed changes and their uncertainty, coverage and next check. Do not attribute a ranking shift to a content/link change without stronger evidence. A proposed follow-up date doesn't create a scheduler or approve future spending.

Deliver the rank table in report template, plus next actions. Recurring monitoring requires a separately available scheduler and explicit authorization for timing, budget and notifications.

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.

Check your setup, free