Site Architecture
alirezarezvani/claude-skills
When the user wants to audit, redesign, or plan their website's structure, URL hierarchy, navigation design, or internal linking strategy.
Define what content a product needs, how it is structured, and who owns it.
Install Content Strategy
$ npx skills add Owl-Listener/designer-skills --skill content-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills content-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ux-strategy/skills/content-strategy .claude/skills/content-strategy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "content-strategy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/content-strategy into .claude/skills/content-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/content-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill content-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills content-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ux-strategy/skills/content-strategy .agents/skills/content-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-strategy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/content-strategy into .agents/skills/content-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill content-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills content-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ux-strategy/skills/content-strategy .cursor/skills/content-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "content-strategy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/content-strategy into .cursor/skills/content-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path ux-strategy/skills/content-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill content-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills content-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ux-strategy/skills/content-strategy .gemini/skills/content-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "content-strategy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/content-strategy into .gemini/skills/content-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills content-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill content-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ux-strategy/skills/content-strategy .github/skills/content-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "content-strategy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/content-strategy into .github/skills/content-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill content-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills content-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ux-strategy/skills/content-strategy .opencode/skills/content-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "content-strategy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/content-strategy into .opencode/skills/content-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
content-strategy- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~852 tokens
- SKILL.md length
- 430 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Define what content a product needs, how it is structured, and who owns it.
- Works in 6 steps: Audit existing content and identify… → Interview users and stakeholders to… → Define content types and models → …
- Content itself is the problem
- SKILL.md covers What You Do, Content Strategy Components, Relationship to Adjacent… and Process, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Content Strategy is an agent skill from Owl-Listener/designer-skills. Define what content a product needs, how it is structured, and who owns it. Use when content itself is the problem. For the words in the interface use ux-writing (designer-toolkit); for structural hierarchy use information-architecture.
Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Content strategy and UX design. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- Content itself is the problem
- Tasks that involve Content strategy
- Tasks that involve UX design
Example prompts
- “/content-strategy”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Audit existing content and identify gaps, redundancy, and orphaned material
- Interview users and stakeholders to understand content needs and vocabulary
- Define content types and models
- Establish voice, tone, and writing principles
- Define governance: owners, workflows, review cycles
- Document and socialize — content strategy only works if writers follow it
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Content Strategy loads about 852 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 430 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 430 words, ~852 tokens.
Download SKILL.mdSave it as
.claude/skills/content-strategy/SKILL.md (or your agent's skills folder).- name
- content-strategy
- description
- Define what content a product needs, how it is structured, and who owns it. Use when content itself is the problem. For the words in the interface use `ux-writing` (designer-toolkit); for structural hierarchy use `information-architecture`.
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
Show full SKILL.md (169 more words)Show less
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
- Audit existing content and identify gaps, redundancy, and orphaned material
- Interview users and stakeholders to understand content needs and vocabulary
- Define content types and models
- Establish voice, tone, and writing principles
- Define governance: owners, workflows, review cycles
- 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
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ux-strategy/skills/content-strategy of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Content Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Content Strategy this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~852 | Automated safety check: Pass | MIT | |
| Site Architecturealirezarezvani/claude-skills | 28k | 1 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Site Architectureborghei/Claude-Skills | 886 | — | ~5.6k | Automated safety check: Pass | MIT | |
| Blogger Distillerotter1101/blogger-distiller | 697 | — | ~3.8k | Automated safety check: Notes | MIT | |
| Linkedin Content Plannersergebulaev/linkedin-skills | 4.4k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Blog Post Draftingluongnv89/claude-howto | 42k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Site Architecture
borghei/Claude-Skills
Information architecture, URL hierarchy, internal linking strategy, navigation design, and silo structure for websites.
Blogger Distiller
otter1101/blogger-distiller
A skill your agent uses when the user wants to analyze or distill a blogger/account on Xiaohongshu or Douyin, benchmark a target creator, or diagnose their own content strategy.
Linkedin Content Planner
sergebulaev/linkedin-skills
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.
Blog Post Drafting
luongnv89/claude-howto
Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.
UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Categories
Questions about Content Strategy
What does Content Strategy do?
Define what content a product needs, how it is structured, and who owns it. Content Strategy is an agent skill from Owl-Listener/designer-skills. Define what content a product needs, how it is structured, and who owns it.
When should I use Content Strategy?
Content Strategy fits situations like: content itself is the problem; tasks that involve Content strategy; tasks that involve UX design.
How do I install Content Strategy in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill content-strategy -a claude-code`. Or copy the skill folder (ux-strategy/skills/content-strategy in Owl-Listener/designer-skills) into .claude/skills/content-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Content Strategy in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill content-strategy -a codex`. Or copy the skill folder (ux-strategy/skills/content-strategy in Owl-Listener/designer-skills) into .agents/skills/content-strategy in your project. Codex loads it when a task matches its description.
Can I use Content Strategy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill content-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-strategy, .gemini/skills/content-strategy, .github/skills/content-strategy and .opencode/skills/content-strategy in your project.
What does Content Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Content Strategy is instructions for the agent only.
Does Content Strategy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Content Strategy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Content Strategy use?
Content Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Content Strategy use?
About 852 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Content Strategy?
Skills that share tags, products or a category with Content Strategy: Site Architecture (alirezarezvani/claude-skills, 28k stars), Site Architecture (borghei/Claude-Skills, 886 stars), Blogger Distiller (otter1101/blogger-distiller, 697 stars) and Linkedin Content Planner (sergebulaev/linkedin-skills, 4.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Content Strategy?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,862 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.