Content Strategy
- 614 installs
- 2k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
content-strategy is a Claude Code design skill that defines what content a software product needs, how it is structured, and who owns it for developers who must plan trustworthy in-product communication.
About
content-strategy is a designer-skills agent skill from owl-listener/designer-skills that plans and governs product content across touchpoints. The skill defines required content types, placement, ownership, writing standards, and maintenance rules so a product communicates consistently. Its workflow includes content audits that inventory existing material by type, location, owner, age, and performance, then classify items to keep, revise, consolidate, or remove while surfacing user-facing gaps. Developers and designers invoke content-strategy when onboarding flows, empty states, help docs, or marketing copy lack a coherent plan. The output is a structured content strategy that ties UX writing decisions to product goals instead of ad hoc page-by-page copy.
- content-strategy
Content Strategy by the numbers
- 614 all-time installs (skills.sh)
- +60 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #632 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill content-strategyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 614 |
|---|---|
| repo stars | ★ 2k |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you plan in-product content structure and ownership?
Use content-strategy for development tasks
Who is it for?
Developers and designers shipping SaaS products who need a governed plan for UX copy, help content, and documentation before build-out.
Skip if: Teams seeking only SEO blog calendars or keyword-driven marketing content plans without product UX writing scope.
When should I use this skill?
A developer asks what content a product needs, how it should be structured, or who maintains docs and in-app copy across touchpoints.
What you get
A content inventory, gap analysis, ownership matrix, and structured content strategy for product touchpoints.
Files
Content Strategy
You are an expert in planning and governing the content that makes a product useful and trustworthy.
What You Do
You define what content a product needs, where it lives, who creates and maintains it, and how it should be written and structured — so the product communicates consistently and serves user needs at every touchpoint.
Content Strategy Components
Content Audit
- Inventory of all existing content by type, location, owner, age, and performance
- Classification: keep, revise, consolidate, or remove
- Identifies gaps (content users need that doesn't exist) and redundancy (same content in multiple places)
Content Model
- Defines content types and their attributes (e.g. an "article" has: title, summary, body, author, tags, publish date)
- Maps relationships between content types
- Drives both design decisions (what fields a form needs) and engineering decisions (data structure)
- A good content model enables reuse: one piece of content rendered in multiple contexts
Voice & Tone
- Voice: the consistent personality of the product's writing (helpful, direct, expert, warm…)
- Tone: how voice adjusts to context (reassuring in error states, celebratory in success states, neutral in legal content)
- Documented with examples and counter-examples for each register
Content Governance
- Who creates content (product, marketing, legal, users)?
- Who reviews and approves it?
- How often is it reviewed for accuracy and freshness?
- Where is the source of truth?
- What is the deprecation process for outdated content?
Content Hierarchy
- Primary content: the main thing users come to do or read
- Secondary content: supporting context (descriptions, labels, help text)
- Tertiary content: metadata, timestamps, attribution
- Design should reflect this hierarchy visually; content strategy defines it semantically
Relationship to Adjacent Disciplines
- UX writing: content strategy defines the framework; UX writing executes at the component level
- Information architecture: IA structures where content lives; content strategy defines what content exists and its attributes
- SEO: content strategy decisions (topics, titles, depth) drive findability in search
- Brand: voice and tone guidelines connect content strategy to brand identity
Process
1. Audit existing content and identify gaps, redundancy, and orphaned material 2. Interview users and stakeholders to understand content needs and vocabulary 3. Define content types and models 4. Establish voice, tone, and writing principles 5. Define governance: owners, workflows, review cycles 6. Document and socialize — content strategy only works if writers follow it
Best Practices
- Start with a content audit before designing new structures — you often need less than you think
- Involve legal and compliance early in voice and tone decisions
- Make the content model drive component design, not the reverse
- Revisit governance quarterly — content rots when ownership is unclear
- Measure content performance (findability, task completion, search queries) to drive revisions
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Use this skill for in-product and documentation governance rather than SEO keyword calendars or social posting schedules.
FAQ
What does content-strategy produce for a product team?
content-strategy defines what content a product needs, where it lives, who creates and maintains it, and how it should be written. The skill outputs audit classifications, gap lists, and governance rules so UX copy and docs stay consistent across touchpoints.
How does content-strategy evaluate existing product content?
content-strategy inventories content by type, location, owner, age, and performance, then labels each item keep, revise, consolidate, or remove. That audit highlights gaps where users lack the information they need in the product experience.