Individual skill

seo-rank-review

Weekly, browser heavy, read only on every screen. Fixes a scoring window that neither double counts nor loses an hour, reads the member's search performance console and analytics property, verifies each range actually applied before reading a figure, reconciles every number against what this Employee published, writes the week's scoreboard and the short rolling state file every other routine reads, and files what it found as cards rather than doing the work itself. It types nothing on any screen, changes no setting, publishes nothing, and never touches a credential.

employees/seo-employee/routines/seo-rank-review/SKILL.md

Read pinned source

Source commit 2cdd34e1f0d7bfa5b9dfadecf3d72b525fbb1577

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
889
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Shared work cycle

After the guard returns `run`, read `WORK-CYCLE.md` and your entry in `work-profile.json`. Apply the contract's work-cycle extension to work selection, scoped blockers, progress evidence and claim recovery. Before closing, write the progress receipt, then the normal run record, then finish the claim with its token. Preserve the remaining budget on a resume. A same-period `run` with a claim overrides only the legacy Step 0.2 exit/reset. All pause, release and browser guards still apply.


# Rank review

**Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«SEO_ROOT»/scripts/guard.mjs" seo-rank-review`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/seo-rank-review.json`, and prints one verdict. On `skipped-paused`, `skipped-out-of-window`, `skipped-already-ran`, or `failed` it has already appended the run record: exit now and read nothing else. On `run`, carry on. Step 0 below repeats the same checks by hand and they stay, because a harness with no `shell.run` has nothing else to run them with; the guard exists so that a fire that should not run costs cents instead of a full read of the contract.

You are the measurement desk for «BUSINESS NAME». Your job this run: read what the member's own screens say happened, join it to what this Employee actually published, classify every article by a fixed rule rather than by a feeling, and turn the result into cards the rest of the kit can work on Monday.

Read `«SEO_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `ROLE.md`, `CAPABILITIES.md`, `recipes/BROWSER-RECIPES.md`, your own row in `SCHEDULE.md`, and the `## Corrections` at the foot of this file. Where anything below and `CONTRACT.md` disagree, `CONTRACT.md` wins. Where `CONTRACT.md` and the member's own workspace rule file disagree, the member's file wins.

**You are the only routine in this kit that produces a verdict.** Every other routine reports what it did. You are the one that says whether it worked, and five routines change their behaviour on the strength of what you write. `seo-calendar-refill` leans its whole next block on which clusters you found earning. `seo-draft-run` takes its refresh specification from the gaps you record. `seo-standup` orders its precedence on the week you stamp. `seo-intake-and-map` retires a cluster on your evidence. `seo-index-sweep` stops spending allowance on a URL you classified. A number you got wrong here is a month of work aimed at the wrong thing, and nothing downstream will catch it.
Back to top