content-strategy

content-strategy is a skill for Claude Code from cogni-work/insight-wave. It costs 135 tokens per session (1,925 once invoked), scanned A, original, Apache-2.0.

A content-planning skill that maps markets, strategic themes, products, competitors, customers, and content formats into a content strategy.

In plain words
What is it for?
It helps build content matrices, connect marketing themes with product propositions, and recommend content types for each market.
Why use it?
It gives teams a structured view of what content to create instead of choosing topics and formats one by one.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the cogni-marketing plugin — 11 skills, 11 commands, 3 agents shipped together

Good fit It helps build content matrices, connect marketing themes with product propositions, and…

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add cogni-work/insight-wave
Claude Code
/plugin install cogni-marketing

Made for: Claude Code.

Or install cogni-marketing, the plugin that ships this one along with the rest of its 11 skills, 11 commands, 3 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for content-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/cogni-work/insight-wave/content-strategy.svg)](https://agentmods.dev/skills/cogni-work/insight-wave/content-strategy)
Your own site
<a href="https://agentmods.dev/skills/cogni-work/insight-wave/content-strategy"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/content-strategy.svg" alt="Measured on agentmods" height="20"></a>
Per session 135 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,925 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00135 $0.01925
Opus 5 $0.00068 $0.00962
Sonnet 5 $0.00027 $0.00385
Haiku 4.5 $0.00014 $0.00193

Measured 3d ago against content hash 093467f2a19b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

content-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

cogni-marketing/skills/content-strategy/SKILL.md · 182 lines

How it starts

The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Content Strategy

Purpose

Build a comprehensive content strategy by mapping TIPS strategic themes (GTM paths) to portfolio propositions per market, then recommending content types and formats for each cell in the 3D matrix: market × GTM path × content type.

Prerequisites

  • Marketing project initialized (marketing-project.json exists with sources, markets, gtm_paths)

Workflow

Step 0: Load Project Context

  1. Read marketing-project.json — extract markets, GTM paths, brand config, content defaults
  2. For each market's GTM paths, load the TIPS strategic theme data:
    • Read tips-value-model.json → find the theme by ID
    • Extract: theme name, value chains (T→I→P paths), solution templates, narrative angle
  3. For each market, load portfolio data:
    • Read propositions matching that market (propositions/*--{market}.json)
    • Read competitors (competitors/*--{market}.json)
    • Read customer profiles (customers/{market}.json)
  4. Build a lookup: which propositions connect to which GTM path (via solution template → portfolio anchor → feature → proposition)

Step 1: Narrative Angle Extraction

For each GTM path (TIPS strategic theme), extract the "WHY NOW" narrative:

  1. Trend hook: The most compelling trend from the theme's value chains (T layer) — this drives thought leadership
  2. Implication tension: The business implication that creates urgency (I layer) — this drives demand generation
  3. Possibility promise: The opportunity the buyer can capture (P layer) — this drives lead generation
  4. Solution proof: How the portfolio delivers it (S layer + propositions) — this drives sales enablement

Store as narrative_angle per GTM path:

{
  "trend_hook": "AI-driven predictive maintenance reduces unplanned downtime by 47%",
  "implication_tension": "Manufacturers without predictive capabilities face 3x higher maintenance costs by 2027",
  "possibility_promise": "Early adopters achieve 30% asset lifetime extension through continuous condition monitoring",
  "solution_proof": "Our IoT + ML platform delivers real-time anomaly detection across all asset types"
}

Read the full file on GitHub · 182 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 182 lines · 135 tokens per session scan A 093467f2a19b

Subscribe to this mod's changes

content-strategy is a skill published in the GitHub repository cogni-work/insight-wave (12 stars, last pushed today), licensed Apache-2.0. It adds 135 tokens to every session and 1,925 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens