marketing-content-strategy/SKILL.md
Use when planning a content strategy, defining content pillars, building a content calendar, deciding what to write about, or aligning content output with business goals. Produces a structured, actionable content plan.
npx skillsauth add paulund/skills marketing-content-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Every piece of content is one of two types. Most strategies need both.
People are already searching for this. It shows up in Google and AI search results.
People do not search for this, but it spreads when it resonates.
Content pillars are the 3-5 core themes your content is built around. Good pillars are:
How to define pillars:
Map content to where the buyer is in their journey:
| Stage | What they want | Keyword modifiers | | --- | --- | --- | | Awareness | Understand a problem or concept | "what is", "how to", "why does", "guide to" | | Consideration | Compare options, find the best approach | "best", "top", "vs", "comparison", "alternatives" | | Decision | Evaluate and choose a specific product | "pricing", "reviews", "demo", "free trial" | | Implementation | Learn to use what they chose | "tutorial", "setup", "templates", "examples" |
A balanced strategy has content at every stage. Most companies over-index on awareness and ignore decision-stage content.
Score each topic idea against four factors:
| Factor | Weight | What it measures | | --- | --- | --- | | Customer Impact | 40% | How much does ranking for this topic affect a real customer's decision? | | Content-Market Fit | 30% | Can you produce genuinely useful content on this topic with real depth? | | Search Potential | 20% | Is there sufficient search volume? Are you likely to rank? | | Resource Requirements | 10% | How much effort does this piece take to produce well? |
Score each 1-5 on each factor, apply the weights, rank the list. The top 8-12 items are your starting backlog.
Week 1-2: Foundation
Week 3-4: Extension
Adjust based on available resources. Consistency beats volume.
| Topic | Reference | Load When |
| ----- | --------- | --------- |
| Content Strategy Framework | references/content-strategy-guide.md | Always |
development
Use when the user wants to run the project's lint + types + build sequence as a gate before pushing, opening a PR, or merging. Invoked by chained dev skills between phases. Trigger phrases - "/quality-gate", "run the quality gate", "check it builds".
tools
Use when the user wants to verify a PR's feature works at runtime by booting the dev server, exercising the affected UI via Chrome DevTools MCP, and posting a screenshot summary back to the PR. Idempotent — skips if `verified` or `verify-failed` is already on the PR. Trigger phrases - "/pr-verify", "verify this PR", "runtime check the pr".
testing
Use when the user wants a security-focused review pass on a PR with findings actioned as commits on the same branch. Trigger phrases - "/pr-security-review", "security review and fix".
testing
Use when the user wants to open a pull request for an already-pushed branch that implements a specific issue. Idempotent — returns the existing PR if one is already open for the branch. Trigger phrases - "/pr-open", "open the pr", "create pr for this branch".