content-strategy
Define what content a product needs, how it is structured, and who owns it. Content audit, content model, voice and tone, governance, and content hierarchy.
How do I install this agent skill?
npx skills add https://github.com/podo/design-agent-skills --skill content-strategyIs this agent skill safe to install?
- Gen Agent Trust Hubwarn
This skill acts as a stub that facilitates the installation of the full content-strategy skill from an external third-party repository.
- Socketwarn
1 alert: gptAnomaly
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
content-strategy
<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->Catalogue stub — full skill: Owl-Listener/designer-skills
Decision tree
-
Is the full skill already installed?
- Global:
f=~/.agents/skills/content-strategy/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer" - Project:
f=.agents/skills/content-strategy/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer" installed→ the skill is installed ascontent-strategy, invoke it and proceedpointer→ go to step 2
- Global:
-
Detect scope, then install:
[ -e ~/.agents/skills/content-strategy ] && echo "global" || echo "project"Global:
npx skills add Owl-Listener/designer-skills --skill content-strategy -g -yProject:
npx skills add Owl-Listener/designer-skills --skill content-strategy -yClaude Code: send a command as a chat message starting with
!to run it without leaving the conversation.
Claude Code plugin route:
/plugin marketplace add Owl-Listener/designer-skills
/plugin install ux-strategy@designer-skills
Heads-up
- License: MIT
Invoke after install
- Skill name:
content-strategy - Trigger phrases: "content strategy", "content model", "content governance", "voice and tone framework"
What it does
Owl's product content-strategy framework: content audit (keep/revise/consolidate/remove), content model with typed attributes and relationships, voice-vs-tone with registers, governance (owners/review cycles/source-of-truth), and content hierarchy. Distinct from microcopy/UX-writing — this is the upstream framework that UX writing executes within.
When NOT to use
- Writing individual UI strings → use
ux-writing-skill - Long-form marketing copy → use
copywriting-skill - Structuring where content lives (navigation, labelling) → use
information-architecture-and-navigation
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/podo/design-agent-skills/content-strategy">View content-strategy on skillZs</a>