Would anyone notice if you stopped publishing?
The skill uses this question to separate a strategy from activity. A calendar lists what goes out and when. A topic list is only raw material. “Post on LinkedIn more” is a tactic. A strategy explains why these pieces, in this order, for this audience, through these channels, and it starts from the audience rather than the channel.
Foundation before topics
Four decisions come first. The audience has to be specific enough to picture, such as marketing managers at software companies who own demand generation. The problem has to be one they search for or ask about in communities. There is one primary goal, whether search traffic, trust, retention, or sales support. And your company needs a point of view that the usual advice does not state.
Pillars, clusters, and the funnel
The skill settles on three to five pillars, broad themes your customers think about at work. Only some of them touch your product, on purpose, because pillars serve the reader rather than the catalog. Each pillar becomes a cluster: a pillar page for the broad search and supporting pages for narrower ones, with internal links mapped before anyone writes.
Formats then follow the buyer’s stage. Guides and research reach people at the start, case studies and comparisons help during evaluation, and pricing explainers or migration guides remove the last objections. Tutorials and onboarding guides help after purchase. Your goal sets how much weight each stage gets.
A calendar sized to your team
Each entry carries a working title, keyword, pillar, stage, format, channel, author, date, and status. The skill works backward from capacity: two pieces a week means roughly eight a month to spread across pillars and stages. It publishes the pillar page before its cluster so the links exist on day one, and it mixes evergreen guides with timely pieces.
Distribution and the numbers that count
Every piece gets a path to your email list. LinkedIn gets the insight written natively, with the link in the comments. Communities get contributions before links, and paid promotion goes only to pieces that already earned attention without it.
For measurement, the skill tracks search growth, rankings, conversions and pipeline touched by content, and retention. It plays down pageviews, shares, and volume on their own. A monthly review of the last 30 days decides what to improve, redirect, or retire.
The whole method in the content-strategy file
The foundation, pillar examples, funnel formats, calendar fields, and metrics all come from the content-strategy skill file on GitHub. It is released under the MIT License, “Copyright (c) 2026 ScayverGraphix.” The skills follow the Agent Skills spec published by vercel-labs/skills.
Give it your real capacity.
Before it builds anything, the skill asks about your product and audience, the goal for content, your team size and publishing pace, and any archive you already have. It also wants existing keyword or analytics research, the channels you use, and whether you need a full strategy, a cluster map, a calendar, or all three.
Ask your agent to plan your content or build topic clusters, or install it directly with npx skills add scayver/marketing-skills --skill content-strategy.
Search results take patience.
The skill warns against judging a search-led plan after 60 days. It expects three to twelve months, depending on your domain, your competition, and how often you publish. It also starts with the archive you already have, because updating or redirecting old posts can matter more than adding new ones.
Decisions before a bigger calendar
Our Content Strategy service helps you decide what to keep, improve, combine, create, and retire before any calendar grows. Every page ends up with a reason to exist, a reader’s question to answer, and an owner who keeps it accurate.