Topic wheel on every personal brand site

Skill packs › Skill

Topic wheel on every personal brand siteIN EVERY PACK

Put a colorful clickable topic wheel on every personal brand site and pair it to the money tree. Use when building or auditing a personal brand site, when Dennis asks for a topic wheel, or when /topic-wheel/ or /money-tree/ is missing.

Skill file topic-wheel-on-personal-brand.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 site is missing /topic-wheel/ or /money-tree/, when the wheel is text-only or not clickable, or when the two pages do not link to each other. Companion to personal-brand-website-agent (homepage facts) and the Content Factory topic-wheel skill (one-minute video ideas). This skill is the site pair.

The pair

  • Topic wheel = what this person talks about.
  • Money tree = which URLs on this domain collect that talk into money.
  • Every chip on the wheel is an <a href> to another page about that topic (a post or page with real detail). Do not leave chips as #anchors on the wheel itself.
  • The page H1 is the title. Do not draw THE {NAME} TOPIC WHEEL inside the SVG — it overlaps the 12-o’clock chips. Screen-reader <title> stays Topic wheel.
  • Both pages carry data-topic-wheel-pair="1" and link both ways.
  • Greatest hits sit on both pages: three topic/article cards on the wheel, three money-page cards on the tree. Spec: Topic-Wheel/hits/{stem}.json. Method: https://blitzmetrics.com/greatest-hits/

Rings (canonical — do not invert)

Match dennisyu.com/topic-wheel and blitzmetrics.com/topic-wheel:

Ring What it is Color language
WHAT (center) The offer / money page Navy disc, orange rim
HOW (middle) Methods / spokes Green ring
WHY (outer) Stories and topics Gold ring

Audience discovers outside-in (story → method → offer). We publish inside-out. The Task Library skill map-out-one-minute-video-topics-using-topic-wheel historically named the rings the other way; live dennisyu.com wins. Do not rewrite a live wheel to match the inverted doc.

Inputs

  • Person name, domain, money-page URL (how they actually make money — Quick Audit, coaching, connect, quote).
  • HOW spokes (3–5 methods). WHY chips (every topic you will film, write, or boost).
  • Live pages/posts so you do not invent topics. Topic-Wheel/from_site.py --site domain.com reads REST.

Steps

  1. Probe https://{domain}/topic-wheel/ and https://{domain}/money-tree/ with a full Chrome User-Agent and gzip. A 403 without gzip is not a 404.
  2. Write Topic-Wheel/wheels/{stem}.json (or generate with from_site.py). Center = offer. Do not put a blog index in WHAT if a real money page exists.
  3. Draw: python3 Topic-Wheel/draw_wheel.py wheels/{stem}.json. Inline SVG, one line (wpautop).
  4. Publish pages (not posts): python3 Topic-Wheel/publish.py --site {domain}. App-pass via republish_daily.call (full Chrome UA + browser headers). No app_pass → Chrome nonce (--chrome) on a logged-in wp-admin tab.
  5. If /money-tree/ is missing, the publisher creates a page at that slug in the mth5ilxt visual language. Do not create a post — some permalinks put posts at /blog/money-tree/ and the pair link 404s.
  6. Do not replace a hand-drawn wheel (dennisyu.com). Inject the pairing aside only.
  7. Verify anonymously: data-topic-wheel, at least one <svg> with <a href inside it, /money-tree/ 200, data-topic-wheel-pair on both. Spot-check three chips: they must 200 as their own URLs.

Definition of done

  • [ ] /topic-wheel/ HTTP 200, colorful SVG, every chip clickable
  • [ ] /money-tree/ HTTP 200 at that pretty permalink (not /blog/money-tree/)
  • [ ] Pair marker on both pages; each links to the other
  • [ ] WHAT is the real offer, not a placeholder
  • [ ] Every chip opens a real page (HTTP 200), not a # fragment on the wheel
  • [ ] SVG has no repeated all-caps title; H1 is Topic wheel
  • [ ] Greatest hits strip present (data-greatest-hits="topics") with three HTTP 200 cards

Publish rails

  • Store: .credentials.json → wp_sites[domain].app_pass. Name the store, never the value.
  • Full Chrome UA on every REST call. BM WAF 403s a minimal UA.
  • Unknown flags on these scripts exit 2.

Definitive articles

  • Method: https://blitzmetrics.com/topic-wheel/ · https://blitzmetrics.com/money-tree/ · https://blitzmetrics.com/greatest-hits/
  • Worked example: https://georgepaladichuk.com/topic-wheel/ (22 chips, NaiL in the center)
  • This standard’s meta: https://blitzmetrics.com/topic-wheel-on-every-personal-brand-site/
  • Fleet board: https://localservicespotlight.com/personal-brand-fleet/

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

Public URL is /skills-topic-wheel-on-personal-brand/, never /skills/topic-wheel-on-personal-brand/. 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