RankRentAI Classroom
Lessons (8)

0/8 complete

  1. What actually makes a local site rank (and why "just write 50 articles" is wrong)
  2. Getting found without Search Console (and why we skip it)
  3. Citations: buy them, but check every one before you pay
  4. IndexNow — re-indexing when you add pages (and when it fails)
  5. Mining expert YouTube channels for ranking and selling playbooks
  6. Folding a distilled playbook into the skill so it actually gets used
  7. Folding in a source whose tactics are mostly rejected
  8. Building your own SEO skill — blue links, AI Overviews, and ChatGPT answers in one playbook
← All modules

Folding a distilled playbook into the skill so it actually gets used

  • C:\Users\61479\.claude\skills\rank-and-rent\references
  • docs/handover/2026-07-28-buildinpublic-youtube-playbook.md

What you're doing and why

A research doc nobody reads changes nothing. After we distilled the Edward Show channel into a playbook, the last step was folding its findings into the rank-and-rent skill itself — the same reference files the agent actually consults when picking niches, building sites, and selling leads — so the new tactics show up at the moment of work, not in a forgotten handover doc. The rule: every addition is dated, names its source, and never silently overrides the existing playbook — where the guest research disagrees with our doctrine, the doctrine stays and the conflict is written down next to it.

The exact steps

  1. Open the skill's references/ folder and find which file owns each topic (local SEO, measurement, site build, AI search, selling). Read each file's existing dated updates section first — the new material must not repeat what's already there.
  2. Append one dated section per file (ours is "Edward Show … layer (2026-07-29)"), with one bolded mini-heading per tactic and a source pointer back to the playbook doc.
  3. Where the new research CONTRADICTS an existing rule, keep the old rule and add a one-line note that the conflict exists and who decides (the owner). Example: a mentor links his own sites together; our footprint-isolation rule says never — the rule stands, the note records the disagreement.
  4. Update the skill's main SKILL.md with a one-paragraph source note so future sessions know the new material exists and where it came from.
  5. Log the fold-in in the ROADMAP the same day.

What it looked like for us

Five reference files updated from the Edward Show playbook: local-seo (open hours and review recency are now measured ranking factors; NAP consistency and GBP posts are measured non- factors), measurement (rank-grid sizing rule; competitor review-cadence benchmark; organic- pages beats DA), microsite-build (case studies on service pages; the 1–2-pages-then-scale gate that prevents mass-launch penalties; "trust content" as a new page type), seo-ai-search (press releases as an AI-visibility channel; the awards play for "best X" AI answers), and selling-leads (the warm-handoff script; "the leads follow whoever pays" as the close).

Gotchas

  • Read the file's existing updates before appending. Two findings we were about to add (weekly billing, review velocity) were already doctrine from an earlier fold — repeating them would dilute the file, so they became one-line confirmations instead of new sections.
  • Dedupe is the whole job. The raw playbook had ~50 candidate tactics; only the ones that were new, measured, and non-contradicting earned a place in the skill. The rest stay in the handover doc with a "rejected / already covered" label.
  • Contradictions get recorded, not resolved. Never edit the old rule to match the new guru — flag it and let the owner rule. Tomorrow's guru will disagree with today's.
  • Date every section. Undated "updates" become impossible to audit once three or four sources have been folded in; the date is what lets you trace a rule back to its evidence.