Greatest hits on the topic wheel and money tree

Skill packs › Skill

Greatest hits on the topic wheel and money treeIN EVERY PACK

Highlight the top 3 money pages on the money tree and the top 3 topics or articles on the topic wheel. Use when building those pages, when Dennis asks for greatest hits, or when a site is amplifying everything equally.

Skill file greatest-hits-on-wheel-and-tree.md · last updated Aug 18, 2026

How to run it. Download any pack from the skill-pack directory, unzip it into your Claude project folder, and this skill is one of the files inside. You do not paste it anywhere — the agent reads it when the job calls for it. This one ships in every pack.

Use this when a personal brand or company site has a topic wheel or money tree (or is about to), when the calendar boosts every new post the same, or when someone asks what the three things are. Companion to topic-wheel-on-personal-brand (the map) and Task Library content-strategy-90-greatest-hits-10-new (the 90/10 split). This skill is which three.

The trio

  • Topic wheel = what they talk about.
  • Money tree = which URLs collect that talk into money.
  • Greatest hits = the three on each map you actually amplify.

Two lists. Money hits are conversion URLs (quote, book, coaching, product, audit). Topic hits are stories or articles people already remember. Do not mash them into one row of “best content.”

Canonical method: blitzmetrics.com/greatest-hits

How to identify (this order)

  1. Conversion (forms, calls, invoices attributed to a URL).
  2. Dollar-a-Day amplification (comments, CTR, cost per result).
  3. Organic (Search Console clicks, GA4 engaged sessions on that URL).
  4. Inbound that names the piece.
  5. Only if 1–4 are missing: the article that existed before this week’s factory run.

Do not rank by recency, word count, or founder boredom. Do not invent revenue. One evidence sentence per card. Same-day stubs are experiments.

Steps

  1. Probe /topic-wheel/ and /money-tree/ (Chrome UA + gzip).
  2. Write Topic-Wheel/hits/{stem}.json with money and topics arrays (max 3 each). href must be HTTP 200. why is the evidence sentence.
  3. Generated wheel: python3 Topic-Wheel/publish.py --site {domain} — gold cards + starred chips.
  4. Hand-drawn wheel (dennisyu.com): python3 Topic-Wheel/inject_hits.py --site {domain} — cards only, do not replace the SVG.
  5. Money tree: same inject; if /money-tree/ 404 and hits exist, inject creates a page of the three closes (do not invent extra branches).
  6. Verify data-greatest-hits="topics" on the wheel and data-greatest-hits="money" on the tree. Spot-check three hrefs 200.

Definition of done

  • [ ] Method article is https://blitzmetrics.com/greatest-hits/
  • [ ] Three topic hits on /topic-wheel/, each a real page
  • [ ] Three money hits on /money-tree/, each a real page
  • [ ] Evidence sentence on every card
  • [ ] Same-day factory stubs are not in the three

Publish rails

  • Specs: Topic-Wheel/hits/{stem}.json
  • Generator: Topic-Wheel/greatest_hits.py · inject_hits.py · publish.py
  • Store: .credentials.json → wp_sites[domain].app_pass. Chrome nonce if missing.
  • Unknown flags exit 2.

Worked examples

  • George: https://georgepaladichuk.com/topic-wheel/
  • Dennis: https://dennisyu.com/topic-wheel/
  • Cam: https://camhazzard.com/topic-wheel/
  • Marko: https://markosipila.com/topic-wheel/

Other skills: ai-search-visibility · always-reply · boil-the-ocean · client-access-checklist · client-relationship-cadence · content-agent

Public URL is /skills-greatest-hits-on-wheel-and-tree/, never /skills/greatest-hits-on-wheel-and-tree/. The rule: canonical skill rule.

The full run order is on the skill-pack directory. Every skill here is one task from the Task Library — the library is the catalogue of what can be done; a pack is the subset you install; an agent is who runs it.

Where this sits in the system

Context is what the worker knows. A skill is the method it follows. A pack is a folder of methods. None of them does any work alone. Work happens when a job runs the right skill against the right context on a schedule, checks its output, and leaves a receipt the next worker can inspect.

  1. Context — the verified facts, goals, evidence, decisions, and working state kept in user-owned Markdown, Obsidian, Drive, or Git so any authorized model can pick up the same work.
  2. Skill — one task, written down to a standard, so an agent can run it without you in the room. There are 243 of them.
  3. PackYOU ARE HERE — those skills bundled into a download you install in one paste.
  4. Agent — a named role with a job description — not a chat window you retype every morning.
  5. Job — a schedule, a QA cycle, and somewhere to keep working files. Miss any of the three and nothing runs twice.
  6. Proof — every finished run written up in public, and the lesson pushed back into the skill.

The map: The System · every asset: Asset Tracker · next door: Asset Tracker.

Scroll to Top