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.
Build content strategies, editorial calendars, topic clusters, and content plans.
Install Content Strategy
$ npx skills add OpenClaudia/openclaudia-skills --skill content-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OpenClaudia/openclaudia-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/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/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/OpenClaudia/openclaudia-skills/tree/main/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/OpenClaudia/openclaudia-skills/tree/main/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 OpenClaudia/openclaudia-skills --skill content-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OpenClaudia/openclaudia-skills content-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/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/OpenClaudia/openclaudia-skills/tree/main/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 OpenClaudia/openclaudia-skills --skill content-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OpenClaudia/openclaudia-skills content-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/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/OpenClaudia/openclaudia-skills/tree/main/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/OpenClaudia/openclaudia-skills.git --path 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 OpenClaudia/openclaudia-skills --skill content-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OpenClaudia/openclaudia-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/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/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/OpenClaudia/openclaudia-skills/tree/main/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 OpenClaudia/openclaudia-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 OpenClaudia/openclaudia-skills --skill content-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/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/OpenClaudia/openclaudia-skills/tree/main/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 OpenClaudia/openclaudia-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 OpenClaudia/openclaudia-skills content-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/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/OpenClaudia/openclaudia-skills/tree/main/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
- 713
- Token cost
- ~2.4k tokens
- SKILL.md length
- 915 words
- Files
- 1
- Skills in repo
- 74
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build content strategies, editorial calendars, topic clusters, and content plans.
- Works in 11 steps: Awareness (Top of Funnel) → Consideration (Middle of Funnel) → Decision (Bottom of Funnel) → …
- Phrases: content strategy
- SKILL.md covers Gathering Requirements, Topic Cluster Architecture, Buyer Journey Content Mapping and Content Mix and Ratio, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Content Strategy is an agent skill from OpenClaudia/openclaudia-skills. Build content strategies, editorial calendars, topic clusters, and content plans. Map content to buyer journey stages and plan distribution. Trigger phrases: "content strategy", "content plan", "topic clusters", "editorial calendar", "content calendar", "pillar page", "content roadmap", "buyer journey content", "content funnel", "content mapping".
Its SKILL.md is about 2.4k 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. The repository describes itself as: 77 open-source marketing skills for Claude Code, Codex, and other AI coding agents. SEO, content, email, ads, analytics, and growth. The licence is MIT.
When your agent uses it
- Phrases: content strategy
- Editorial calendar
- Content calendar
- Content roadmap
Example prompts
- “content strategy”
- “content plan”
- “topic clusters”
- “/content-strategy”
Workflow steps
11 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 28bf209. 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 (its code samples are markdown).
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 2.4k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 915 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 OpenClaudia/openclaudia-skills at commit 28bf209, republished under its MIT licence (© OpenClaudia). 915 words, ~2,371 tokens.
Download SKILL.mdSave it as
.claude/skills/content-strategy/SKILL.md (or your agent's skills folder).- name
- content-strategy
- description
- Build content strategies, editorial calendars, topic clusters, and content plans. Map content to buyer journey stages and plan distribution. Trigger phrases: "content strategy", "content plan", "topic clusters", "editorial calendar", "content calendar", "pillar page", "content roadmap", "buyer journey content", "content funnel", "content mapping".
Content Strategy Skill
You are a senior content strategist. Your job is to build comprehensive content plans that drive organic traffic, nurture leads, and support business goals through strategic content creation and distribution.
Gathering Requirements
Before building any strategy, collect these inputs:
- Business type - SaaS, ecommerce, agency, media, B2B, B2C, etc.
- Target audience - ICPs, personas, demographics, pain points.
- Business goals - Traffic, leads, brand awareness, thought leadership, SEO, conversions.
- Current state - Existing content assets, traffic levels, top-performing content.
- Competitors - 3-5 competitors whose content you admire or compete against.
- Resources - Team size, budget, publishing capacity (posts per week/month).
- Channels - Blog, newsletter, social, YouTube, podcast, etc.
- Timeline - 30/60/90-day plan or quarterly/annual.
Topic Cluster Architecture
What is a Topic Cluster?
A topic cluster is a pillar page (comprehensive, 2000-5000 word guide) supported by 8-20 cluster pages (focused articles of 800-1500 words) that interlink to the pillar and to each other. This structure signals topical authority to search engines.
How to Build a Topic Cluster
Step 1: Identify Core Topics
List 3-5 core topics that align with your product and audience needs.
Example for a project management SaaS:
- Project management methodologies
- Team productivity
- Remote work collaboration
- Resource planning
- Agile development
Step 2: Create Pillar Pages
For each core topic, define a pillar page:
Pillar: "The Complete Guide to Agile Project Management"
URL: /agile-project-management
Target: "agile project management" (high volume, high difficulty)
Length: 3000-5000 words
Format: Comprehensive guide with table of contents, jump linksStep 3: Map Cluster Content
For each pillar, brainstorm 10-20 cluster articles targeting long-tail keywords:
Pillar: Agile Project Management
Clusters:
- "What is a Sprint? A Beginner's Guide" -> /agile/what-is-a-sprint
- "Scrum vs Kanban: Which Is Right for Your Team?" -> /agile/scrum-vs-kanban
- "How to Run an Effective Sprint Retrospective" -> /agile/sprint-retrospective
- "Agile Estimation Techniques: Story Points Explained" -> /agile/story-points
- "Daily Standup Best Practices for Remote Teams" -> /agile/daily-standup
- "How to Create a Product Backlog That Actually Works" -> /agile/product-backlog
- "Agile vs Waterfall: A Side-by-Side Comparison" -> /agile/agile-vs-waterfall
- "Sprint Planning Template (Free Download)" -> /agile/sprint-planning-template
- "Common Agile Mistakes and How to Avoid Them" -> /agile/common-mistakes
- "How to Measure Agile Team Velocity" -> /agile/team-velocityStep 4: Define Internal Linking Rules
- Every cluster page links to its pillar page (required).
- The pillar page links to every cluster page (required).
- Cluster pages link to 2-3 sibling cluster pages where relevant (recommended).
- Use descriptive anchor text, not "click here".
Topic Cluster Template
## Cluster: [Topic Name]
### Pillar Page
- Title: [Title]
- Target keyword: [keyword] (volume: [X], difficulty: [Y])
- URL: [/path]
- Word count: [3000-5000]
- Format: [Comprehensive guide / Ultimate guide]
### Cluster Pages
| # | Title | Target Keyword | Volume | Difficulty | Word Count | Priority |
|---|-------|---------------|--------|------------|------------|----------|
| 1 | [Title] | [keyword] | [X] | [Y] | [800-1500] | [High/Med/Low] |
| 2 | ... | ... | ... | ... | ... | ... |
### Internal Linking Map
- Pillar -> All clusters
- Cluster 1 -> Cluster 3, Cluster 5
- Cluster 2 -> Cluster 1, Cluster 7
- (etc.)Buyer Journey Content Mapping
Map every piece of content to a buyer journey stage.
Stage 1: Awareness (Top of Funnel)
Reader mindset: "I have a problem but don't know the solution yet."
Content types:
- Blog posts answering "what is" and "why" questions
- Educational guides and how-to articles
- Industry reports and trend pieces
- Infographics and explainer videos
- Social media educational content
Keyword intent: Informational (what, why, how, guide, tips)
KPIs: Traffic, time on page, social shares, newsletter signups.
Goal: Build awareness and capture email addresses.
Stage 2: Consideration (Middle of Funnel)
Reader mindset: "I know the solution category. Which option is best for me?"
Content types:
- Comparison articles (X vs Y)
- "Best [category] for [use case]" listicles
- Case studies
- Webinars and demos
- Detailed feature guides
- Templates and toolkits
Keyword intent: Commercial investigation (best, compare, review, alternative, vs)
KPIs: Email signups, content downloads, webinar registrations, demo requests.
Goal: Position your product as the best option.
Stage 3: Decision (Bottom of Funnel)
Reader mindset: "I'm ready to buy. Convince me this is the right choice."
Content types:
- Product landing pages
- Pricing pages
- Customer testimonials and success stories
- Free trial / demo pages
- ROI calculators
- Implementation guides
Keyword intent: Transactional (buy, pricing, free trial, demo, signup)
KPIs: Trial signups, demo bookings, purchases, revenue.
Goal: Convert leads to customers.
Stage 4: Retention (Post-Purchase)
Reader mindset: "How do I get the most from this product?"
Content types:
- Onboarding guides and tutorials
- Best practices and tips
- Product update announcements
- Community content
- Advanced use case guides
- Customer spotlight features
KPIs: Activation rate, feature adoption, NPS, churn rate, expansion revenue.
Goal: Reduce churn and drive expansion.
Show full SKILL.md (373 more words)Show less
Content Mix and Ratio
Follow this ratio for a balanced content strategy:
| Content Type | % of Output | Purpose |
|---|---|---|
| Awareness / Educational | 40% | Drive organic traffic, build authority |
| Consideration / Comparison | 25% | Capture mid-funnel leads |
| Decision / Conversion | 15% | Drive signups and sales |
| Retention / Enablement | 10% | Reduce churn, increase LTV |
| Thought Leadership / Brand | 10% | Build brand, attract press and links |
Publishing Cadence
Recommended Cadence by Company Stage
| Stage | Blog Posts | Newsletter | Social | Video |
|---|---|---|---|---|
| Early (0-50K traffic) | 2-4/week | 1/week | 5/week | 1/month |
| Growth (50-200K traffic) | 3-5/week | 1-2/week | 7/week | 2/month |
| Scale (200K+ traffic) | 5-10/week | 2-3/week | 10+/week | 4/month |
Content Batching Workflow
- Week 1 of month: Research and outline all content for the month.
- Week 2: Write first drafts of all pieces.
- Week 3: Edit, design assets, and prepare for publishing.
- Week 4: Publish, promote, and repurpose.
Distribution Strategy
For every piece of content, plan distribution across these channels:
Owned Channels
- Blog - Publish the full piece.
- Newsletter - Summarize with a link to full article.
- Social media - Create 3-5 social posts per article (see below).
- Podcast/video - Repurpose written content into audio/video.
Earned Channels
- SEO - Optimize for target keywords, build internal links.
- Backlinks - Pitch the piece for guest posts, link roundups, resource pages.
- PR - If newsworthy, pitch to journalists and industry publications.
- Communities - Share in relevant Slack groups, Discord servers, Reddit, forums.
Paid Channels
- Social ads - Boost top-performing organic posts.
- Retargeting - Show content to website visitors who did not convert.
- Sponsored newsletters - Place in niche industry newsletters.
Content Repurposing Plan
Turn one blog post into 8+ pieces of content:
1 Blog Post (2000 words)
-> 1 Newsletter summary (300 words)
-> 1 Twitter/X thread (10 tweets)
-> 1 LinkedIn post (long-form)
-> 1 Instagram carousel (10 slides)
-> 1 Short-form video script (60 seconds)
-> 1 Infographic
-> 1 Podcast episode outline
-> 3-5 Quote graphicsOutput Format
When building a content strategy, deliver:
1. Content Audit Summary
Assessment of current content, gaps, and opportunities.
2. Topic Cluster Map
Visual or tabular representation of all pillar and cluster content.
3. Buyer Journey Content Map
Table mapping each planned piece to a funnel stage.
4. 90-Day Content Calendar
Month-by-month publishing plan with titles, target keywords, funnel stage, content type, owner, and due date.
5. Distribution Playbook
Channel-by-channel plan for promoting each content type.
6. KPI Dashboard
Metrics to track for each funnel stage with targets.
7. Content Briefs
For the first month's content, provide detailed content briefs including:
- Title and target keyword
- Search intent
- Outline (H2s and H3s)
- Competitor content to beat
- Internal linking targets
- CTA and conversion goal
© OpenClaudia, 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 skills/content-strategy of OpenClaudia/openclaudia-skills.
Open the folder on GitHubat commit 28bf209
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 skillOpenClaudia/openclaudia-skills | 713 | — | ~2.4k | 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 | |
| WeChat Hot Article AnalysisSpaceZephyr/creator-buddy | 1.6k | — | ~847 | Automated safety check: Pass | None | |
| Brand Voice Content Creatordavila7/claude-code-templates | 32k | 3 repos | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
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.
WeChat Hot Article Analysis
SpaceZephyr/creator-buddy
Fetches hot WeChat Official Account articles by sector or keywords and produces a data file and an HTML report with rankings, style patterns and writing references.
Brand Voice Content Creator
davila7/claude-code-templates
Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.
Ralph Copywriter
muratcankoylan/ralph-wiggum-marketer
A skill your agent uses when the user asks to "analyze my content", "learn my writing style", "research competitors", "find content angles", "improve my blog", "write like me", "embody my brand…
More from OpenClaudia/openclaudia-skills
All 74 skills in this repoCompetitor Traffic Report
OpenClaudia/openclaudia-skills
Build an interactive competitive-traffic report for any company and its rivals — monthly visits (SimilarWeb), organic search traffic and Domain Rating (Ahrefs) — as one self-contained HTML page with…
Geo Difficulty
OpenClaudia/openclaudia-skills
Score how hard a keyword is to rank for in the AI-search era — page-level URL Rating of real competitors (not just domain DR), Ahrefs keyword difficulty, and whether a given site already ranks or is…
Gsc Portfolio Audit
OpenClaudia/openclaudia-skills
Audit EVERY Google Search Console property at once — rank all sites by clicks and impressions with period-over-period deltas, then diff keywords per site to surface what is newly ranking, rising…
Similarweb Traffic
OpenClaudia/openclaudia-skills
Fetch website traffic estimates (monthly visits, traffic sources, top countries, keywords, engagement, ranks) for any domain from SimilarWeb.
Ahrefs Python
OpenClaudia/openclaudia-skills
Manages Ahrefs API usage in Python using ahrefs-python library.
Ab Test Setup
OpenClaudia/openclaudia-skills
Design, plan, and analyze A/B tests with statistical rigor. An agent skill from OpenClaudia/openclaudia-skills.
Related
Categories
Questions about Content Strategy
What does Content Strategy do?
Build content strategies, editorial calendars, topic clusters, and content plans. Content Strategy is an agent skill from OpenClaudia/openclaudia-skills. Build content strategies, editorial calendars, topic clusters, and content plans.
When should I use Content Strategy?
Content Strategy fits situations like: phrases: content strategy; editorial calendar; content calendar; content roadmap.
How do I install Content Strategy in Claude Code?
Run `npx skills add OpenClaudia/openclaudia-skills --skill content-strategy -a claude-code`. Or copy the skill folder (skills/content-strategy in OpenClaudia/openclaudia-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 OpenClaudia/openclaudia-skills --skill content-strategy -a codex`. Or copy the skill folder (skills/content-strategy in OpenClaudia/openclaudia-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 OpenClaudia/openclaudia-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 2.4k tokens (SKILL.md is roughly 9.5k 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: Blogger Distiller (otter1101/blogger-distiller, 697 stars), Linkedin Content Planner (sergebulaev/linkedin-skills, 4.4k stars), Blog Post Drafting (luongnv89/claude-howto, 42k stars) and WeChat Hot Article Analysis (SpaceZephyr/creator-buddy, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Content Strategy?
OpenClaudia (a GitHub organization) maintains it in OpenClaudia/openclaudia-skills, which has 713 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on September 18, 2026.
Source: OpenClaudia/openclaudia-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.