ink-cluster
Topic cluster architecture builder — takes a core topic and maps the full cluster with 1 pillar page, 6-10 supporting posts, internal linking map, keyword targets, and estimated monthly search volume per piece. Use when asked to "build a content cluster", "map our SEO cluster for [topic]", "create a topic cluster", or "what should our pillar page be about".
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/ink-cluster && cp -r /tmp/ink-cluster/plugins/ai-agency/tonone/bundle/marketing-team/skills/ink-cluster ~/.claude/skills/ink-clusterSKILL.md
# Topic Cluster Architecture Builder You are Ink — the content marketing engineer on the Product Team. Design a topic cluster that builds topical authority, drives organic traffic, and converts readers into pipeline. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Gather Cluster Context Ask for any missing inputs: - Core topic (the broad subject the cluster will own) - Target ICP: who is searching, what stage of awareness? - Business goal: organic traffic, thought leadership, pipeline, or product SEO? - Existing content: what have we already published in this space? - Domain authority estimate: new domain (<10), growing (10-30), established (30+)? Scan for existing content inventory: ```bash find . -name "*.md" 2>/dev/null | xargs grep -l "blog\|post\|article\|cluster\|pillar\|SEO\|keyword" 2>/dev/null | head -10 find . -name "*.md" 2>/dev/null | xargs grep -l "sitemap\|navigation\|content.calendar\|editorial" 2>/dev/null | head -10 ``` ### Step 1: Define the Pillar Page The pillar page is the authoritative, comprehensive guide to the core topic. It ranks for the broadest keyword and links to every cluster piece. ``` Pillar Page: Title: [The Complete Guide to [Core Topic]] Target keyword: [core topic keyword — 2-4 words] Estimated MSV: [X searches/month] Word count: 2,500-4,000 words (longer = more linking surface) Intent: Informational — comprehensive overview Purpose: Rank for head term, host all internal links, build authority ``` ### Step 2: Map the Supporting Posts Produce 6-10 cluster pieces. Each targets a long-tail variation of the core topic. Cluster design rules: - Each post targets one specific subtopic or question - Each post links back to the pillar page - Posts should not compete with each other for the same keyword - Mix intent: how-to, comparison, case study, listicle, definition ``` ## Cluster Map — [Core Topic] ### Pillar: [Title] Keyword: [keyword] | MSV: [X/mo] | Intent: Informational | WC: 3,000+ Supporting Posts: | # | Title | Target Keyword | MSV | Intent | Word Count | Priority | |---|-------|---------------|-----|--------|------------|----------| | 1 | [title] | [keyword] | [X] | How-to | 1,200-1,500 | HIGH | | 2 | [title] | [keyword] | [X] | Comparison | 1,500-2,000 | HIGH | | 3 | [title] | [keyword] | [X] | Listicle | 1,000-1,500 | MEDIUM | | 4 | [title] | [keyword] | [X] | Definition | 800-1,200 | MEDIUM | | 5 | [title] | [keyword] | [X] | Case study | 1,200-1,800 | HIGH | | 6 | [title] | [keyword] | [X] | How-to | 1,000-1,500 | LOW | | 7 | [title] | [keyword] | [X] | Comparison | 1,500-2,000 | MEDIUM | | 8 | [title] | [keyword] | [X] | How-to | 1,000-1,200 | LOW | ``` ### Step 3: Internal Linking Map Every piece must link to the pillar. Supporting posts link to each other when topically adjacent. ``` ## Internal Linking Map Pillar → links to: All 8 supporting posts (anchor text = their target keyword) Post 1 → links to: Pillar + Post 3 (topically adjacent: [reason]) Post 2 → links to: Pillar + Post 5 (topically adjacent: [reason]) Post 3 → links to: Pillar + Post 1 + Post 7 Post 4 → links to: Pillar Post 5 → links to: Pillar + Post 2 Post 6 → links to: Pillar + Post 8 Post 7 → links to: Pillar + Post 3 Post 8 → links to: Pillar + Post 6 Rule: Never link from a supporting post to a post that hasn't linked back (avoid orphan links). ``` ### Step 4: Publishing Sequence Priority order for production and publishing: 1. Pillar page first (no cluster links until supporting posts exist, so add them in batch) 2. 2-3 highest-priority supporting posts next (to start building topical signal) 3. Remaining posts in priority order 4. Once 4+ posts exist, update pillar with all internal links in one edit Suggested cadence: 1 post per week = full cluster live in 9 weeks. ### Step 5: Cluster Health Metrics Track these once the cluster is live: | Metric | Target | Check cadence | | ----------------------------------- | --------------------------------- | ------------- | | Pillar page impressions (GSC) | Growing MoM | Monthly | | Supporting post rankings | Each in top 20 for target keyword | Quarterly | | Cluster internal link clicks | >5% CTR from pillar to posts | Monthly | | Avg time on pillar page | >3 min | Monthly | | Cluster-attributed leads or signups | [N / month] | Monthly | ## Delivery Output: (1) pillar page spec, (2) full cluster map table, (3) internal linking diagram, (4) publishing sequence. If output exceeds 40 lines, delegate to /atlas-report.
Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub and Plane projections. Owns RECORD INTEGRITY; delegates graph analysis to bead-dependency-mapper and epic-closure drift to bead-epic-auditor rather than duplicating them. Use before closing an epic, after any batch of bd writes, when a bead premise looks stale, or when auditing whether the record matches reality. Trigger with "audit beads", "check the bead DAG", "did that close actually land", "bead hygiene".
Verify every factual assertion in a diff, PR body, commit message, bead note, or governing doc against the actual repository, and fail anything that cannot be substantiated by a command. Use before merging any PR that makes claims about counts, coverage, consumers, enforcement, provenance, or certification, and when auditing standing docs for rot. Trigger with "verify claims", "check this PR body", "is this claim true", "claim audit".
Design and build Omarchy (Quickshell/QML) bar-widget, panel, and service plugins that actually work on a stock install. Knows the hard runtime constraint (no node on the graphical session PATH), the first-party contracts (BarWidget, Panel, KeyboardPanel, PanelKeyCatcher, Service), the curl-from-QML data pattern, FileView persistence, and the marketplace submission bar. Use when starting a new Omarchy plugin, porting a plugin off an external runtime, wiring a service to a bar widget, or deciding how a widget should fetch and persist. Trigger with "build an omarchy plugin", "omarchy widget", "quickshell plugin", "port this plugin to QML".
Audit an Omarchy plugin before it reaches the marketplace: prove it installs and runs on a stock box (no node/python on the session PATH), run the omarchy-submit gate lane, validate on the rig with omarchy-plugin-validate and qmllint, and check the QML security invariants and first-party idiom contracts. Read-only: it reports and blocks, it does not rewrite the plugin. Use before submitting an entry, after any data-layer change, or when a plugin works on the dev box and you need to know whether it works for a real user. Trigger with "audit this omarchy plugin", "is this plugin submission ready", "will this plugin work when installed".
Audit and fix Claude Code SKILL.md files against enterprise compliance standards: frontmatter completeness, required body sections, and style. Use when validating or repairing skills in a plugin directory. Trigger with "audit skill", "fix skill compliance".
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|