revive-old-pages
Skill0 starsChanged 4 months agoMITView on GitHub
Classify every URL with search history into refresh, rewrite, consolidate or kill, excluding anything still inside its own shipped verification window so a fix is never judged before it has had time to work.
In this repository26 other files it gives its agents.
- beat-my-competitorsSkill
- brief-my-writerSkill
- can-i-actually-rankSkill
- check-before-i-publishSkill
- explain-this-numberSkill
- find-my-quick-winsSkill
- follow-the-moneySkill
- get-cited-elsewhereSkill
- get-mentioned-by-aiSkill
- know-my-buyerSkill
- make-it-sound-humanSkill
- make-me-quotableSkill
- map-my-siteSkill
- pick-my-battlesSkill
- put-it-on-autopilotSkill
- rainmakerSkill
- say-it-their-waySkill
- show-me-progressSkill
- show-up-in-communitiesSkill
- spread-one-piece-everywhereSkill
- stop-losing-visitorsSkill
- unblock-my-money-pagesSkill
- what-actually-workedSkill
- what-changed-in-searchSkill
- what-to-target-nextSkill
- write-the-pageSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are 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.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Run rainmaker context --check first.
- Very specific: line 30
Only the data/ files listed in this skill's Consumes table.
- Very specific: line 32
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
- Very specific: line 38
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context.
- Very specific: line 67
Prefer refreshing a cluster below 80 percent completeness (per map-my-site) over starting a new one, when both are viable options for the …
- Distinctive: line 71
Every URL gets exactly one classification.
- Very specific: line 72
Never classify a page still inside its verification window.
- Distinctive: line 98
Every URL with history has exactly one classification or sits in "pending", every kill names a redirect target, and nothing inside its own …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
revive-old-pages
Context load
Run rainmaker context --check first. It prints what exists, what is stale, and exits 1 if anything this skill requires is missing.
Then read, in this order:
context/business.mdin full. If absent, stop: "No business context. Runrainmaker audit, then theknow-my-buyerskill."context/voice.mdif this skill writes prose. If absent, stop and say so.context/glossary.mdif this skill names products, features or competitors.data/strategy.jsonif this skill reads or writes strategy.- Only the
data/files listed in this skill's Consumes table. Never crawl or call an API the core already covers.
If strategy.json.context_hash does not match the current hash of context/business.md, say exactly:
"Business context was edited after the strategy was written. Re-run know-my-buyer, or run rainmaker context --sync to accept the prose as authoritative."
Then stop.
If context/business.md carries confidence: stub, continue, and stamp every output with: "Built on a stub context. Nothing in it came from a buyer. Run know-my-buyer to replace it."
Consumes
| File | Why | If missing |
data/snapshots/<latest>/gsc.json (2+ snapshots) | position and impression history | "Need at least two Search Console snapshots. Run rainmaker fetch --source gsc again after 28 days." |
data/snapshots/<latest>/crawl.json | word count, links, canonical status | run rainmaker audit |
data/ledger.jsonl | what was already shipped and its verification window | run rainmaker ledger --rebuild |
data/blueprint.json | cluster completeness, to prioritise refreshing under-covered clusters | optional |
Produces
Classification report; keyword_plan[].slot (shared owner with what-to-target-next).
Refuses when
Fewer than two GSC snapshots exist. A single snapshot has no movement to classify against.
Procedure
- Classify every URL with GSC history into exactly one of:
- refresh: position declined 3 or more places, impressions still above 100, tier 0 to 2, over 600 words.
- rewrite: impressions fell 50 percent or more across two windows, cluster still
validated. - consolidate: competes with another URL on a query, per the shared overlap detector, holding the smaller impression share.
- kill: tier 3 or 4, zero clicks across two consecutive windows, no inbound links from tier 0 to 2, no proof cited on the page.
- Join to
ledger.jsonl: exclude any page shipped inside its own verification window fromsrc/ledger/types.ts VERIFICATION_WINDOWS. Judging a fix before its window closes manufactures noise, and this is the same rule the ledger itself enforces onshippedtoverified. - Rank by the score of the corresponding cluster.
- For every
kill, state the proposed redirect target. A kill without a redirect target is a broken link, not a cleanup. - Prefer refreshing a cluster below 80 percent completeness (per
map-my-site) over starting a new one, when both are viable options for the same effort budget.
Decision rules
- Every URL gets exactly one classification. A page that could plausibly be two things is resolved, not left ambiguous.
- Never classify a page still inside its verification window; report it separately as "pending", matching the ledger's own
pendingVerification. - A
killalways names its redirect target.
Output
## Content decay report
refresh (<n>):
<url>: position <before> to <after>, <impressions> impressions
rewrite (<n>):
<url>: impressions down <n>%, cluster status <validated|hypothesis>
consolidate (<n>):
<url>: competes with <url>, keep the larger impression share
kill (<n>):
<url>: 0 clicks over 2 windows, redirect to <target>
pending verification (<n>, excluded from the above):
<url>: shipped <date>, window closes <date>Done when
Every URL with history has exactly one classification or sits in "pending", every kill names a redirect target, and nothing inside its own verification window was judged.
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
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.

