[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79MXYM9AH6RQB37TZCZGKB4":3,"skill-same:01M79MXYM9AH6RQB37TZCZGKB4":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M79MXYM9AH6RQB37TZCZGKB4","pillar-content",null,"Hub-and-cluster authority content. OmniSkill Social crew — builds a comprehensive pillar page with supporting cluster articles and the internal linking that makes the structure work.","IPedrax\u002FOmniSkill","IPedrax","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64429409?v=4","01M79MSCRSKESGTTRZMGK54KW0","01M79MSCSDY16CNNHW0VRGZFHF",9,"MIT","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fpillar-content\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pillar-content\ndescription: Hub-and-cluster authority content. OmniSkill Social crew — builds a comprehensive pillar page with supporting cluster articles and the internal linking that makes the structure work.\ndisable-model-invocation: true\n---\n\n# Pillar Content\n\n> Hub-and-cluster authority · OmniSkill Social crew\n\nOne comprehensive pillar page on a broad topic, surrounded by cluster articles covering sub-topics in depth, all deliberately interlinked.\n\n## Why the structure works\n\nThree effects compound:\n\n1. **Demonstrated coverage.** A site with a pillar and fifteen supporting pieces on a subject visibly knows that subject better than a site with one post.\n2. **Internal link equity.** Clusters link to the pillar, concentrating authority where it competes for the hardest term.\n3. **Query coverage.** The pillar catches broad head terms; clusters catch specific long-tail ones. Together they cover a topic's full search surface.\n\nThe structure is the point. A pillar page with no clusters is just a long article; clusters with no pillar are scattered posts.\n\n## 1. Choose the pillar topic\n\nIt must be:\n- **Broad enough** to support 10+ genuine sub-topics\n- **Narrow enough** to actually cover comprehensively\n- **Commercially relevant** — connected to what the business sells\n- **Winnable** at current domain authority\n\n\"Marketing\" is too broad. \"Email subject lines\" is too narrow. \"Email marketing for e-commerce\" is a pillar.\n\nSource topics from `\u002Fomniskill:content-strategy` rather than brainstorming.\n\n## 2. Build the pillar page\n\n**Comprehensive, not exhausting.** Cover every major sub-topic well enough to be genuinely useful standalone, then link out to the cluster piece for depth. The pillar is a map with real terrain, not a table of contents.\n\nStructure:\n- Clear definition and scope up front — answer the head query in the first paragraph\n- A section per major sub-topic, each self-contained and useful\n- A contextual link from each section to its cluster article\n- Table of contents with anchor links for anything long\n- Original data, frameworks, or visuals that exist nowhere else\n\nLength follows coverage, not a target. Typically 2,000–5,000 words, but a 2,000-word pillar that covers the topic beats a padded 6,000-word one.\n\n**Make it linkable.** Original research, a useful framework, or a genuinely definitive resource earns external links. Pillars are the pages worth building links to.\n\n## 3. Build the clusters\n\nEach cluster article:\n- Covers **one** sub-topic in real depth\n- Stands alone as useful — never a stub existing only to link\n- Links **back to the pillar** with descriptive anchor text\n- Links **sideways to sibling clusters** where genuinely relevant\n- Targets a specific long-tail query\n\nAim for 8–15 clusters per pillar. Publish the pillar first, then clusters steadily.\n\n## 4. Get the internal linking right\n\nThis is where most implementations fail.\n\n- **Every cluster links up to the pillar.** Non-negotiable — this is the mechanism.\n- **The pillar links down to every cluster.** Update it as each publishes; a pillar that never gets updated leaves clusters orphaned.\n- **Clusters link to relevant siblings**, not to all of them indiscriminately.\n- **Descriptive anchor text** — the target's topic, not \"click here\" and not the same exact-match phrase every time.\n- **Contextual placement** in the body, which carries more weight than a footer link block.\n\n## 5. Maintain\n\nPillars decay. Review quarterly: refresh statistics and dates, add clusters as new sub-topics emerge, update links, consolidate clusters that have started competing with each other for the same query.\n\nA well-maintained pillar compounds for years. An abandoned one slides steadily.\n\n## 6. Measure at cluster level\n\nJudge the cluster as a unit, not article by article. Track combined organic traffic, pillar ranking for the head term, cluster rankings for long-tail, internal link flow, and conversions.\n\nExpect 3–6 months before the structure shows its effect. Judging at week four kills strategies that were working.\n\n## Output\n\nPillar outline with sections, the cluster list with target queries, the internal linking map, the publication sequence, and the maintenance schedule.\n\n## Checks before delivering\n\n- Pillar is broad enough for 10+ sub-topics and narrow enough to cover.\n- Every cluster is independently useful.\n- Every cluster links to the pillar; the pillar links to every cluster.\n- Anchor text is descriptive and varied.\n- Something on the pillar is genuinely original.\n- Maintenance cadence is scheduled.\n","# Pillar Content\n\n> Hub-and-cluster authority · OmniSkill Social crew\n\nOne comprehensive pillar page on a broad topic, surrounded by cluster articles covering sub-topics in depth, all deliberately interlinked.\n\n## Why the structure works\n\nThree effects compound:\n\n1. **Demonstrated coverage.** A site with a pillar and fifteen supporting pieces on a subject visibly knows that subject better than a site with one post.\n2. **Internal link equity.** Clusters link to the pillar, concentrating authority where it competes for the hardest term.\n3. **Query coverage.** The pillar catches broad head terms; clusters catch specific long-tail ones. Together they cover a topic's full search surface.\n\nThe structure is the point. A pillar page with no clusters is just a long article; clusters with no pillar are scattered posts.\n\n## 1. Choose the pillar topic\n\nIt must be:\n- **Broad enough** to support 10+ genuine sub-topics\n- **Narrow enough** to actually cover comprehensively\n- **Commercially relevant** — connected to what the business sells\n- **Winnable** at current domain authority\n\n\"Marketing\" is too broad. \"Email subject lines\" is too narrow. \"Email marketing for e-commerce\" is a pillar.\n\nSource topics from `\u002Fomniskill:content-strategy` rather than brainstorming.\n\n## 2. Build the pillar page\n\n**Comprehensive, not exhausting.** Cover every major sub-topic well enough to be genuinely useful standalone, then link out to the cluster piece for depth. The pillar is a map with real terrain, not a table of contents.\n\nStructure:\n- Clear definition and scope up front — answer the head query in the first paragraph\n- A section per major sub-topic, each self-contained and useful\n- A contextual link from each section to its cluster article\n- Table of contents with anchor links for anything long\n- Original data, frameworks, or visuals that exist nowhere else\n\nLength follows coverage, not a target. Typically 2,000–5,000 words, but a 2,000-word pillar that covers the topic beats a padded 6,000-word one.\n\n**Make it linkable.** Original research, a useful framework, or a genuinely definitive resource earns external links. Pillars are the pages worth building links to.\n\n## 3. Build the clusters\n\nEach cluster article:\n- Covers **one** sub-topic in real depth\n- Stands alone as useful — never a stub existing only to link\n- Links **back to the pillar** with descriptive anchor text\n- Links **sideways to sibling clusters** where genuinely relevant\n- Targets a specific long-tail query\n\nAim for 8–15 clusters per pillar. Publish the pillar first, then clusters steadily.\n\n## 4. Get the internal linking right\n\nThis is where most implementations fail.\n\n- **Every cluster links up to the pillar.** Non-negotiable — this is the mechanism.\n- **The pillar links down to every cluster.** Update it as each publishes; a pillar that never gets updated leaves clusters orphaned.\n- **Clusters link to relevant siblings**, not to all of them indiscriminately.\n- **Descriptive anchor text** — the target's topic, not \"click here\" and not the same exact-match phrase every time.\n- **Contextual placement** in the body, which carries more weight than a footer link block.\n\n## 5. Maintain\n\nPillars decay. Review quarterly: refresh statistics and dates, add clusters as new sub-topics emerge, update links, consolidate clusters that have started competing with each other for the same query.\n\nA well-maintained pillar compounds for years. An abandoned one slides steadily.\n\n## 6. Measure at cluster level\n\nJudge the cluster as a unit, not article by article. Track combined organic traffic, pillar ranking for the head term, cluster rankings for long-tail, internal link flow, and conversions.\n\nExpect 3–6 months before the structure shows its effect. Judging at week four kills strategies that were working.\n\n## Output\n\nPillar outline with sections, the cluster list with target queries, the internal linking map, the publication sequence, and the maintenance schedule.\n\n## Checks before delivering\n\n- Pillar is broad enough for 10+ sub-topics and narrow enough to cover.\n- Every cluster is independently useful.\n- Every cluster links to the pillar; the pillar links to every cluster.\n- Anchor text is descriptive and varied.\n- Something on the pillar is genuinely original.\n- Maintenance cadence is scheduled.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","cc238b48e3c4fe0061cad0b0475142fbff5b183d","skills\u002Fpillar-content",0,"https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill","https:\u002F\u002Fgithub.com\u002FIPedrax","2026-10-14 10:26:53",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":23},[33,36,39],{"tool":34,"command":35},"npx","npx skills add IPedrax\u002FOmniSkill --skill pillar-content",{"tool":37,"command":38},"bunx","bunx skills add IPedrax\u002FOmniSkill --skill pillar-content",{"tool":40,"command":41},"pnpm","pnpm dlx skills add IPedrax\u002FOmniSkill --skill pillar-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fpillar-content\u002FSKILL.md",[],[45,52,59,66,73,79],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M79N058MCJZPHNFYZCPJG3ZZ","xlsx","Excel with live formulas. OmniSkill Operations crew — adapter for the xlsx skill, which installs separately.","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fxlsx\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M79N01GR5C5EK22CKGG38VYH","webapp-testing","Browser-test a web app. OmniSkill Developers crew — drives a real browser to verify user flows, catches console and network errors, and writes tests that do not flake.","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M79MZZSJHFKJRE46BNEHCYZ3","web-artifacts","shadcn HTML artifacts. OmniSkill Design crew — bundled copy of the Web Artifacts skill.","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M79MZXFMCV0QSQ2WN316JKGZ","video","Script and produce video. OmniSkill Social crew — structures short-form and long-form video around retention, with shot lists, captions, and platform-specific delivery.","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M79MZV8SR0N02YX539Z5PS5E","vgpu","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fvgpu\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M79MZS7JG9X0T4T5TGA4MMJS","uisfx","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fuisfx\u002FSKILL.md",[],[]]