Agent skill
content-strategy
Define an author's content pillars, topics, subtopics and funnel roles from their audience, evidence, goals and offer.
Filed under Content and SEO.
From timscheuerai/gtm-architecture-template · 51 skill entries · 13 · pushed 2026-09-17
What it does when it runs
Define an author's content pillars, topics, subtopics and funnel roles from their audience, evidence, goals and offer.
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/timscheuerai/gtm-architecture-template.git /tmp/gtm-architecture-template git -C /tmp/gtm-architecture-template sparse-checkout set ".agents/skills/content-strategy" mkdir -p ~/.claude/skills/content-strategy cp -R "/tmp/gtm-architecture-template/.agents/skills/content-strategy/." ~/.claude/skills/content-strategy/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from timscheuerai/gtm-architecture-template/blob/2c312c9398064ad3730c786647293458cb89632c/.agents/skills/content-strategy/SKILL.md, which is licensed MIT (repository). 394 words, 5 headings.
Workspace: all context paths below (identity, audience, strategy, voice, brand, raw, output, index, log, workspace preferences and context scripts) resolve from context/ in the kit root. Read both the root AGENTS.md and context/AGENTS.md. Skill-local references/ and flowchart scripts/ resolve from this skill directory.
Define content strategy
Read AGENTS.md, index.md, identity/positioning.md, identity/proof.md, audience/ideal-follower.md, strategy/goals.md, strategy/pillars.md and strategy/funnel.md. Read the three stage pages when mapping the funnel.
Establish the job
Identify the intended reader, the problem the author can credibly address, the public material they can draw on and the next step they can actually offer. Distinguish an audience that spreads content from a qualified buyer. A missing offer can remain unresolved while educational content is planned.
Build the taxonomy
Propose or refine pillars around recurring reader needs and the author's experience. Each pillar needs a promise and a boundary; split overlapping pillars or explain the overlap. Topics are recurring questions within a pillar. Subtopics are specific angles supported by source material.
The empty scaffold offers four pillars, four topics each and four subtopics per topic. Use that as a starting point, not a requirement to manufacture 64 ideas. Mark suggested names as proposals until the user adopts them. Preserve an existing taxonomy unless revision is requested.
Connect content to conversion
For each topic, define its likely job:
- Top: make the right reader recognize a problem or perspective.
- Middle: explain a method, tradeoff or piece of evidence that earns trust.
- Bottom: make a relevant offer and a clear next step.
Specify inbound routes such as a direct reply, registration, signup or requested resource. If signal-based outbound is part of the brief, specify the signal source, buyer-fit check, exclusions, routing and intended conversation. A reaction is evidence of engagement, not consent or buying intent. Separate qualification from messaging and leave provider selection to the actual setup.
Define the events to measure and the attribution limits. Do not turn reach into claimed revenue. Write unverified targets as targets, not results.
File and apply
Update strategy pages with rationale and sources. For an authorized Notion taxonomy setup, follow strategy/notion-schema.md, use the configured data sources and page-body templates, and keep pillar option names synchronized between the two databases. Query before creating rows.
Return the proposed or adopted taxonomy, funnel paths and unresolved decisions. Planning outbound does not run enrichment or send messages.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- content-strategy by coreyhaines31 · 54,316
- content-strategy by OpenClaudia · 714
- content-strategy by shawnpang · 350
- suede-content-strategy by JasonColapietro · 127
- content-strategy-and-planning by manojbajaj95 · 106
- seo-content-strategy by 0xF4ng · 6
- linkedin-content-strategy by Ad-Superpowers · 5
- linkedin-content-planner by sergebulaev · 4,557
Need help setting it up?
This page tells you what content-strategy does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.