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.
Develop and execute a content strategy that maps content to audience needs, funnel stages, and business goals through editorial planning and performance analysis.
Install Content Strategy
$ npx skills add seb1n/awesome-ai-agent-skills --skill content-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install seb1n/awesome-ai-agent-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/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing-and-seo/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/seb1n/awesome-ai-agent-skills/tree/main/marketing-and-seo/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/seb1n/awesome-ai-agent-skills/tree/main/marketing-and-seo/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 seb1n/awesome-ai-agent-skills --skill content-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills content-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing-and-seo/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/seb1n/awesome-ai-agent-skills/tree/main/marketing-and-seo/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 seb1n/awesome-ai-agent-skills --skill content-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills content-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing-and-seo/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/seb1n/awesome-ai-agent-skills/tree/main/marketing-and-seo/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/seb1n/awesome-ai-agent-skills.git --path marketing-and-seo/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 seb1n/awesome-ai-agent-skills --skill content-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install seb1n/awesome-ai-agent-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/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing-and-seo/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/seb1n/awesome-ai-agent-skills/tree/main/marketing-and-seo/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 seb1n/awesome-ai-agent-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 seb1n/awesome-ai-agent-skills --skill content-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing-and-seo/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/seb1n/awesome-ai-agent-skills/tree/main/marketing-and-seo/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 seb1n/awesome-ai-agent-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 seb1n/awesome-ai-agent-skills content-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing-and-seo/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/seb1n/awesome-ai-agent-skills/tree/main/marketing-and-seo/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
- 206
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,225 words
- Files
- 1
- Skills in repo
- 101
- Repo updated
- First seen
- Licence
- MIT
At a glance
Develop and execute a content strategy that maps content to audience needs, funnel stages, and business goals through editorial planning and performance analysis.
- Works in 6 steps: Audit existing content and define goals.… → Research the target audience and build… → Establish content pillars and topic… → …
- The user requests content strategy
- SKILL.md covers Workflow, Usage, Examples and Best Practices, 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 seb1n/awesome-ai-agent-skills. Develop and execute a content strategy that maps content to audience needs, funnel stages, and business goals through editorial planning and performance analysis. Use when the user requests content strategy or provides relevant inputs for this workflow.
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: 103 ready-to-use AI agent skills for Claude Code, OpenAI Codex, Gemini CLI, Cursor, GitHub Copilot, Windsurf, and other Agent Skills-compatible tools. Complete SKILL.md… The licence is MIT.
When your agent uses it
- The user requests content strategy
- Provides relevant inputs for this workflow
Example prompts
- “/content-strategy”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Audit existing content and define goals. Inventory all current content assets — blog posts, landing pages, case studies, videos…
- Research the target audience and build personas. Define 2–4 buyer personas with demographics, job roles, pain points, content consumption…
- Establish content pillars and topic clusters. Define 3–5 content pillars — broad themes that align with the product's value proposition…
- Build the editorial calendar. Plan content production on a rolling 3-month horizon. For each piece, specify the topic, target keyword…
- Define distribution and repurposing workflows. For each content piece, plan the distribution path: organic social posts, email newsletter…
- Set up measurement and iteration cadence. Define KPIs for each funnel stage: TOFU (traffic, impressions, social shares), MOFU (email…
What it can do on your machine
Read from SKILL.md and the folder at commit 75865a5. 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 2.4k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 1,225 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 seb1n/awesome-ai-agent-skills at commit 75865a5, republished under its MIT licence (© seb1n). 1,225 words, ~2,350 tokens.
Download SKILL.mdSave it as
.claude/skills/content-strategy/SKILL.md (or your agent's skills folder).- name
- content-strategy
- description
- Develop and execute a content strategy that maps content to audience needs, funnel stages, and business goals through editorial planning and performance analysis. Use when the user requests content strategy or provides relevant inputs for this workflow.
- license
- MIT
- metadata.author
- awesome-ai-agent-skills
- metadata.version
- 1.0.0
Content Strategy
This skill enables an AI agent to build a comprehensive content strategy from the ground up or audit and improve an existing one. The agent defines content pillars aligned to business objectives, maps content types to funnel stages (TOFU/MOFU/BOFU), creates editorial calendars, and establishes a measurement framework. The output is a repeatable system for producing, distributing, and optimizing content that drives traffic, engagement, and conversions.
Workflow
Audit existing content and define goals. Inventory all current content assets — blog posts, landing pages, case studies, videos, whitepapers — with their publication dates, traffic, and conversion metrics. Identify top performers, underperformers, and content gaps. Align the strategy to 2–3 measurable goals such as "increase organic traffic 40% in 6 months" or "generate 200 MQLs per month from content."
Research the target audience and build personas. Define 2–4 buyer personas with demographics, job roles, pain points, content consumption habits, and preferred channels. Map each persona to their buyer journey stages: awareness (problem recognition), consideration (evaluating solutions), and decision (selecting a vendor). This determines what content types each persona needs at each stage.
Establish content pillars and topic clusters. Define 3–5 content pillars — broad themes that align with the product's value proposition and audience needs. Under each pillar, plan a cluster of 8–15 supporting pieces that link back to a comprehensive pillar page. This structure builds topical authority for SEO and creates a logical content architecture.
Build the editorial calendar. Plan content production on a rolling 3-month horizon. For each piece, specify the topic, target keyword, content format (blog, video, infographic, podcast), funnel stage, assigned persona, distribution channels, author, and publish date. Balance content across pillars and funnel stages — roughly 60% TOFU, 30% MOFU, and 10% BOFU.
Define distribution and repurposing workflows. For each content piece, plan the distribution path: organic social posts, email newsletter inclusion, syndication partners, and paid promotion budget. Design repurposing chains — for example, a long-form blog post becomes a LinkedIn carousel, a Twitter/X thread, an email snippet, and a short video. This multiplies reach without multiplying production effort.
Set up measurement and iteration cadence. Define KPIs for each funnel stage: TOFU (traffic, impressions, social shares), MOFU (email signups, content downloads, time on page), BOFU (demo requests, free trial starts, SQLs). Review content performance biweekly, retire or update underperforming content quarterly, and refresh the editorial calendar monthly.
Usage
Provide the agent with your business type, target audience, existing content (if any), and goals. The agent will return a complete content strategy with pillars, editorial calendar, and distribution plan.
Prompt: Create a content strategy for a B2B cybersecurity startup targeting IT directors at mid-market companies. Goal: generate 150 leads/month from content within 6 months.
Examples
Example 1: Three-Month Editorial Calendar
Request: Create a Q2 content calendar for a SaaS HR platform targeting startup founders.
| Week | Topic | Format | Funnel | Pillar | Channel | Keyword |
|---|---|---|---|---|---|---|
| W1 Apr | How to Write Your First Employee Handbook | Blog (2,000 words) | TOFU | HR Compliance | Organic + LinkedIn | employee handbook template |
| W2 Apr | Employee Handbook Checklist (PDF) | Downloadable guide | MOFU | HR Compliance | Email + Gated landing page | — |
| W3 Apr | 5 Onboarding Mistakes That Increase Turnover | Blog (1,500 words) | TOFU | Employee Onboarding | Organic + Twitter/X | onboarding mistakes |
| W4 Apr | Video: Setting Up PTO Policies in HRBot | Tutorial video (8 min) | BOFU | Product Demos | YouTube + Email | — |
| W1 May | Remote Hiring: Compliance in 5 States | Blog (2,500 words) | TOFU | Remote Work | Organic + LinkedIn | remote hiring compliance |
| W2 May | Startup Compensation Benchmarks 2025 | Data report + infographic | MOFU | Compensation | Gated + Social | startup salary benchmarks |
| W3 May | How We Helped Acme Scale from 10 to 100 Employees | Case study | BOFU | Product Demos | Email + Sales enablement | — |
| W4 May | Ask an HR Expert: Live Q&A Webinar | Webinar | MOFU | HR Compliance | Email + LinkedIn Events | — |
| W1 Jun | Performance Review Templates That Actually Work | Blog + templates | TOFU | Performance Mgmt | Organic + Pinterest | performance review template |
| W2 Jun | MOFU Email Nurture Sequence (5-part) | Email series | MOFU | Cross-pillar | Email automation | — |
| W3 Jun | Comparison: HRBot vs BambooHR vs Gusto | Comparison page | BOFU | Product Demos | Organic + Paid search | hrbot vs bamboohr |
| W4 Jun | Q2 Content Performance Review | Internal report | — | — | Internal | — |
Show full SKILL.md (549 more words)Show less
Example 2: Content Audit with Recommendations
Request: Audit the existing blog for startuphub.io (42 posts published over 18 months).
Audit Findings:
| Category | Count | Avg Monthly Traffic | Action |
|---|---|---|---|
| High performers (>1,000 visits/mo) | 6 | 2,400 | Update with fresh data, add CTAs, interlink with MOFU content |
| Moderate performers (200–1,000 visits/mo) | 14 | 480 | Optimize titles/meta descriptions, add internal links, refresh examples |
| Low performers (<200 visits/mo) | 18 | 65 | Consolidate 8 thin posts into 4 comprehensive guides; redirect old URLs |
| Outdated content (>12 months, no updates) | 12 | 110 | Update statistics and screenshots, re-publish with current date |
| No-traffic content (<10 visits/mo) | 4 | 6 | Evaluate for removal or complete rewrite; 301 redirect to related content |
Top Recommendations:
- Consolidate thin content. Merge the 8 low-traffic posts on overlapping topics into 4 pillar-style guides. This reduces index bloat and concentrates link equity.
- Add MOFU conversion paths. Only 3 of 42 posts include a content upgrade or lead magnet CTA. Add relevant downloadable assets to the top 20 posts.
- Fix internal linking. 15 posts have zero internal links. Create a hub-and-spoke linking structure around the 3 strongest content pillars.
- Establish a refresh cadence. Commit to updating 4 posts per month with current year data, new screenshots, and expanded sections.
Best Practices
- Balance content across funnel stages. A common mistake is publishing only TOFU blog posts. Without MOFU comparison guides and BOFU case studies, traffic does not convert. Target a 60/30/10 split.
- Repurpose every long-form piece into at least 3 derivative formats. A single blog post can become a LinkedIn carousel, a Twitter/X thread, an email newsletter section, and a short-form video. This triples distribution without tripling production cost.
- Set a sustainable publishing cadence. Two high-quality posts per week consistently outperforms five mediocre posts per week. Quality signals (time on page, backlinks, shares) compound over time.
- Tie every content piece to a measurable outcome. Each piece should have a primary CTA: subscribe, download, book a demo, start a free trial. Content without a next step is a dead end.
- Use content briefs for every piece. A brief should include the target keyword, search intent, competitor URLs to beat, outline with H2/H3 headings, target word count, and internal links to include. Briefs improve consistency and reduce revision cycles.
- Document your strategy in a living playbook. Include brand voice guidelines, persona definitions, pillar topics, and distribution checklists. This enables new team members to execute without losing quality.
Edge Cases
- Brand-new sites with no existing content. Skip the audit phase and prioritize creating 3 pillar pages and 10–15 supporting posts before diversifying into other formats. Focus on low-difficulty keywords to build initial domain authority.
- Highly regulated industries (finance, healthcare). All content requires compliance review before publication. Build a 2-week legal review buffer into the editorial calendar and maintain an approval workflow.
- Seasonal businesses. Plan content production 8–12 weeks ahead of peak season. Publish evergreen foundational content year-round and layer seasonal pieces on top during peak windows.
- Limited budget or solo creator. Reduce to 2 content pillars and 1 post per week. Focus on SEO-driven evergreen content that compounds over time rather than social-first content that decays quickly.
- Pivoting product or audience. When the product repositions, audit existing content for alignment with the new positioning. Archive or redirect misaligned content rather than deleting it, to preserve any existing backlinks and authority.
© seb1n, 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 marketing-and-seo/content-strategy of seb1n/awesome-ai-agent-skills.
Open the folder on GitHubat commit 75865a5
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 skillseb1n/awesome-ai-agent-skills | 206 | — | ~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 seb1n/awesome-ai-agent-skills
All 101 skills in this repoAgent Red Teaming
seb1n/awesome-ai-agent-skills
Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings.
Eu AI Act Readiness
seb1n/awesome-ai-agent-skills
Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency…
Human In The Loop
seb1n/awesome-ai-agent-skills
Design and verify auditable human oversight, approval gates, escalation paths, and safe state transitions for AI agent workflows.
MCP Server Building
seb1n/awesome-ai-agent-skills
Design, implement, harden, and verify Model Context Protocol (MCP) servers with precise tool contracts, least-privilege authorization, safe transports, structured errors, and interoperability tests.
PDF Processing
seb1n/awesome-ai-agent-skills
Inspect, extract, OCR, create, merge, split, reorder, rotate, annotate, fill, redact, compress, secure, and verify PDF documents while preserving source files and visual fidelity.
Skill Supply Chain Audit
seb1n/awesome-ai-agent-skills
Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk.
Related
Categories
Questions about Content Strategy
What does Content Strategy do?
Develop and execute a content strategy that maps content to audience needs, funnel stages, and business goals through editorial planning and performance analysis. Content Strategy is an agent skill from seb1n/awesome-ai-agent-skills. Develop and execute a content strategy that maps content to audience needs, funnel stages, and business goals through editorial planning and performance analysis.
When should I use Content Strategy?
Content Strategy fits situations like: the user requests content strategy; provides relevant inputs for this workflow.
How do I install Content Strategy in Claude Code?
Run `npx skills add seb1n/awesome-ai-agent-skills --skill content-strategy -a claude-code`. Or copy the skill folder (marketing-and-seo/content-strategy in seb1n/awesome-ai-agent-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 seb1n/awesome-ai-agent-skills --skill content-strategy -a codex`. Or copy the skill folder (marketing-and-seo/content-strategy in seb1n/awesome-ai-agent-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 seb1n/awesome-ai-agent-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 (declared in SKILL.md). 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.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: 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?
seb1n (a GitHub user) maintains it in seb1n/awesome-ai-agent-skills, which has 206 GitHub stars. The repository holds 101 skills in this directory. The repository was last updated on August 9, 2026.
Source: seb1n/awesome-ai-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.