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.
Plan content strategy: content pillars, audience research, topic clustering, funnel mapping, and content audits.
$ npx skills add borghei/Claude-Skills --skill content-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-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/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing/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/borghei/Claude-Skills/tree/main/marketing/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/borghei/Claude-Skills/tree/main/marketing/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 borghei/Claude-Skills --skill content-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills content-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing/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/borghei/Claude-Skills/tree/main/marketing/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 borghei/Claude-Skills --skill content-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills content-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing/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/borghei/Claude-Skills/tree/main/marketing/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/borghei/Claude-Skills.git --path marketing/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 borghei/Claude-Skills --skill content-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-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/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing/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/borghei/Claude-Skills/tree/main/marketing/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 borghei/Claude-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 borghei/Claude-Skills --skill content-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing/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/borghei/Claude-Skills/tree/main/marketing/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 borghei/Claude-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 borghei/Claude-Skills content-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing/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/borghei/Claude-Skills/tree/main/marketing/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.
content-strategyPlan content strategy: content pillars, audience research, topic clustering, funnel mapping, and content audits.
Content Strategy is an agent skill from borghei/Claude-Skills. Plan content strategy: content pillars, audience research, topic clustering, funnel mapping, and content audits. Use when deciding what content to create, building a content calendar, planning topic clusters, or finding content gaps.
Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/content_brief_generator.py`, `scripts/content_calendar_planner.py` and `scripts/headline_analyzer.py`).
It sits in Writing & Content, covering Content strategy. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit c9a1487. It shows what the files ask for, not the result of running them.
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.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Content Strategy loads about 5k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 2,080 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.
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); the scripts in this folder are not scanned.
The full file from borghei/Claude-Skills at commit c9a1487, republished under its MIT licence (© borghei). 2,080 words, ~5,046 tokens.
.claude/skills/content-strategy/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Strategic content planning that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.
content strategy, content planning, content pillars, topic clusters, content calendar, audience research, content audit, funnel mapping, content gaps, editorial planning, blog strategy, content ideas, topic ideation, SEO content strategy, content roadmap, content marketing strategy, content performance, keyword research, buyer journey content, search intent mapping
Before building the strategy, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Step 1: Business Context Gathering
Before planning content, understand the business foundation:
## Strategy Context
- Business goal for content: [Traffic / Leads / Brand awareness / Thought leadership]
- Product/service: [What you sell and to whom]
- Ideal customer profile: [Industry, company size, role, seniority]
- Sales cycle: [Self-serve / Sales-assisted / Enterprise]
- Current content state: [Starting fresh / Some content / Mature library]
- Resources: [Writers, budget, publishing capacity per week/month]
- Competitors producing content: [Top 3-5 competitor blogs]Step 2: Customer Research for Content
Mine these sources for content topics:
| Source | What to Extract | How to Use |
|---|---|---|
| Sales call recordings | Questions prospects ask before buying | Create content answering each question |
| Support tickets | Recurring problems and confusion | Tutorial and troubleshooting content |
| Customer interviews | Language they use to describe problems | Use their exact words in headlines and copy |
| Product reviews (yours + competitors) | Praise and complaints | Content addressing concerns, amplifying strengths |
| Community forums (Reddit, Slack, Discord) | Questions, debates, misconceptions | Topic ideas with proven demand |
| Search console queries | What people search to find you | Optimize for highest-potential queries |
Step 3: Define Content Pillars
Pillars are the 3-5 broad topic areas your content focuses on. Each pillar should:
Step 4: Build Topic Clusters
For each pillar, develop a cluster of 10-25 topics:
## Pillar: [Topic Area]
Pillar page: [Comprehensive guide serving as the hub]
### Supporting Topics
1. [Topic] — KW: [keyword], Vol: [X], Diff: [X], Intent: [Info/Commercial]
2. [Topic] — KW: [keyword], Vol: [X], Diff: [X], Intent: [Info/Commercial]
3. [Topic] — KW: [keyword], Vol: [X], Diff: [X], Intent: [Info/Commercial]
...
### Internal Linking Plan
- All supporting topics link to pillar page
- Pillar page links to all supporting topics
- Related supporting topics cross-link to each otherStep 5: Prioritize Topics
Score each topic on a priority matrix:
| Factor | Weight | Scoring |
|---|---|---|
| Search volume | 25% | High (3), Medium (2), Low (1) |
| Keyword difficulty | 20% | Easy (3), Medium (2), Hard (1) |
| Business relevance | 30% | Direct product connection (3), Adjacent (2), Tangential (1) |
| Competitive gap | 15% | No good content exists (3), Beatable content (2), Strong competitors (1) |
| Content asset value | 10% | Evergreen + repurposable (3), Seasonal (2), One-time (1) |
Priority score = weighted sum. Execute highest scores first.
Step 1: Inventory All Content
Build a content inventory spreadsheet:
| URL | Title | Pillar | Format | Publish Date | Last Updated | Monthly Traffic | Avg Time on Page | Conversions | Target Keyword | Ranking Position |
|---|
Step 2: Classify Each Piece
For each piece, determine:
Step 3: Score Performance
| Score | Traffic | Engagement | Conversion | Action |
|---|---|---|---|---|
| A (top 20%) | High traffic | Above avg time on page | Drives conversions | Protect, repurpose, update regularly |
| B (middle 40%) | Moderate | Average engagement | Some conversions | Optimize, improve, interlink |
| C (next 30%) | Low | Below average | Minimal | Update or consolidate |
| D (bottom 10%) | Near zero | High bounce | None | Redirect, remove, or completely rewrite |
Step 4: Build Remediation Plan
| Action | When | How |
|---|---|---|
| Update | Content is B or C tier with good topic but outdated info | Refresh data, add new sections, update publish date |
| Consolidate | Multiple thin pieces on same topic | Merge into one comprehensive piece, redirect old URLs |
| Remove | Content is irrelevant, duplicate, or unfixable | 301 redirect to most relevant remaining page |
| Create new | Gap exists in pillar coverage | Add to editorial calendar with priority score |
| Optimize | Content ranks #4-20 for target keyword | On-page SEO improvements, better intro, internal links |
Example Pillar Structure for a SaaS Product:
| Pillar | Business Connection | Audience Need | Content Types |
|---|---|---|---|
| [Core problem you solve] | Direct product relevance | Actively searching for solutions | How-to guides, tutorials, comparisons |
| [Industry your audience works in] | Thought leadership | Staying current on trends | Analysis, predictions, benchmarks |
| [Adjacent skill your audience needs] | Trust building | Professional development | Frameworks, templates, playbooks |
| [Use case deep dives] | Product education | Understanding applications | Case studies, walkthroughs, examples |
Each pillar should have a comprehensive hub page (2,000-4,000 words) that:
| Method | Time Required | Quality | Best For |
|---|---|---|---|
| Customer interview analysis | 2-4 hours | Highest | Understanding language, pain points, objections |
| Sales call review | 1-2 hours | High | Identifying pre-purchase questions |
| Support ticket mining | 1-2 hours | High | Finding confusion points and tutorial needs |
| Competitor comment analysis | 1 hour | Medium | Discovering unmet content needs |
| Community forum research | 1-2 hours | Medium | Finding real questions and debates |
| Search console analysis | 30 min | Medium | Understanding what queries already reach you |
| Keyword research tools | 1-2 hours | Medium | Quantifying demand for topics |
The most valuable output of audience research is exact language:
| Customer Says | Content Opportunity |
|---|---|
| "I wish I knew..." | Educational content using their exact framing |
| "The hardest part is..." | Tutorial content addressing that specific difficulty |
| "I always forget to..." | Checklist or template content |
| "Everyone says to do X, but..." | Contrarian or nuanced content |
| "Is it worth it to..." | ROI analysis or comparison content |
| "What's the difference between..." | Comparison or explainer content |
| Stage | Reader Mindset | Content Goal | Content Types | Metrics |
|---|---|---|---|---|
| Awareness | "I have a problem" | Attract and educate | Blog posts, videos, infographics, social content | Traffic, impressions, shares |
| Consideration | "What are my options?" | Build trust and differentiate | Comparisons, case studies, guides, webinars | Time on page, email signups, return visits |
| Decision | "Is this the right solution?" | Convert | Product pages, demos, free trials, ROI calculators | Signups, trials, demo requests, purchases |
For each content pillar, ensure coverage across all funnel stages:
## Pillar: [Topic]
### Awareness Topics (attract new visitors)
- [Topic targeting broad informational keyword]
- [Topic answering common beginner question]
- [Topic providing industry data or benchmark]
### Consideration Topics (build trust and preference)
- [Topic comparing approaches or solutions]
- [Topic showing how to evaluate options]
- [Case study demonstrating results]
### Decision Topics (drive conversion)
- [Product-specific tutorial or walkthrough]
- [ROI calculator or assessment tool]
- [FAQ addressing buying objections]| Dimension | Searchable Content | Shareable Content |
|---|---|---|
| Discovery | People search for it (keyword-driven) | People share it (social-driven) |
| Lifespan | Evergreen (months to years) | Timely (days to weeks) |
| Examples | "How to set up GA4 tracking" | "The state of marketing in 2026" |
| Traffic pattern | Steady, compounding | Spike, then decline |
| Optimization | SEO-first | Hook and emotion-first |
| Measurement | Organic traffic, rankings | Shares, engagement, referral traffic |
Most content strategies should be:
| Content Type | Searchable | Shareable | Both |
|---|---|---|---|
| How-to guides | High | Low | — |
| Original research | Medium | High | Yes |
| Comparisons | High | Medium | Yes |
| Thought leadership | Low | High | — |
| Templates/tools | High | Medium | Yes |
| Case studies | Medium | Medium | Yes |
| Industry news takes | Low | High | — |
| Tutorials | High | Low | — |
| Frameworks/playbooks | Medium | High | Yes |
For each top competitor:
## Competitor: [Name]
### Content Inventory
- Blog frequency: [Posts per week/month]
- Content types: [Formats they use]
- Average word count: [Length]
- Primary topics: [Their content pillars]
### Strengths
- [What they do well]
- [Topics where they dominate]
### Gaps
- [Topics they don't cover]
- [Angles they miss]
- [Outdated content that could be beaten]
### Opportunity
- [Where you can win with better content]
- [Underserved topics in their coverage]| Topic | Competitor A | Competitor B | Competitor C | Your Coverage | Gap Score |
|---|---|---|---|---|---|
| [Topic 1] | Strong | None | Weak | None | High opportunity |
| [Topic 2] | Strong | Strong | Strong | Weak | Improve existing |
| [Topic 3] | None | None | None | None | Blue ocean opportunity |
Strategy before production — A mediocre topic executed well is still a mediocre result. Spend time picking the right topics.
Customer research is non-negotiable — Content strategy built without customer input is guessing. Mine sales calls, support tickets, and customer language before planning.
Cover the full funnel — Most teams over-index on awareness content. Ensure each pillar has consideration and decision-stage content too.
Prioritize by business impact, not search volume — A 500-volume keyword with high purchase intent outperforms a 10,000-volume keyword with no commercial relevance.
Audit before you create — Most content libraries have underperforming content that could be improved for more impact than writing something new.
Interlink systematically — Topic clusters only work when content is connected through internal links. Build linking into the production process.
Refresh > Publish — Updating a post ranking #8 to reach #3 produces more traffic than a new post starting at position #50.
One pillar at a time — Build depth in one pillar before spreading across all of them. Authority comes from depth, not breadth.
Document your strategy — A strategy that only lives in someone's head is not a strategy. Write it down, share it, refer to it.
Measure quarterly — Content strategy is a 6-12 month investment. Monthly reviews for tactics, quarterly reviews for strategy adjustments.
| Problem | Likely Cause | Fix |
|---|---|---|
| Content published consistently but no organic traffic growth | Topics selected without keyword research or targeting zero-volume queries | Re-prioritize using search volume x business relevance x competitive gap scoring matrix |
| All content is awareness-stage, no leads generated | Over-indexing on top-of-funnel content without consideration/decision stage pieces | Audit funnel coverage per pillar; create 2-3 consideration and decision pieces per pillar |
| Topic cannibalization across content pieces | Multiple articles targeting the same keyword without differentiation | Map one primary keyword per page; consolidate competing pieces or differentiate angles |
| Content calendar frequently disrupted | Production timelines too tight or no buffer for reviews and revisions | Add 3-day buffer per piece; batch brief creation 4-6 pieces at a time |
| Competitor consistently outranks on shared topics | Competitor has stronger E-E-A-T signals or deeper content coverage | Analyze competitor content depth; add original data, expert quotes, and experience signals |
| Content audit reveals 70%+ of library is underperforming | Strategy was never defined — content was reactive, not planned | Start with 3 content pillars, build 10-15 cluster topics per pillar, then produce systematically |
In scope:
Out of scope:
Known limitations:
# Generate a content calendar plan from topic list
python scripts/content_calendar_planner.py --topics topics.csv --cadence weekly --json
# Analyze headlines for click-worthiness and SEO
python scripts/headline_analyzer.py --headlines headlines.txt --json
# Score content brief completeness
python scripts/content_brief_generator.py --keyword "cloud cost optimization" --json© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts) in marketing/content-strategy of borghei/Claude-Skills.
Open the folder on GitHubat commit c9a1487
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 skillborghei/Claude-Skills | 874 | — | ~5k | Automated safety check: Pass | MIT | |
| Blogger Distillerotter1101/blogger-distiller | 692 | — | ~3.8k | Automated safety check: Notes | MIT | |
| Blog Post Draftingluongnv89/claude-howto | 42k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Linkedin Content Plannersergebulaev/linkedin-skills | 4.3k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| WeChat Hot Article AnalysisSpaceZephyr/creator-buddy | 1.6k | — | ~847 | Automated safety check: Pass | None | |
| Ralph Copywritermuratcankoylan/ralph-wiggum-marketer | 778 | — | ~2.4k | Automated safety check: Pass | None |
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.
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.
sergebulaev/linkedin-skills
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.
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.
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…
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.
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Categories
Plan content strategy: content pillars, audience research, topic clustering, funnel mapping, and content audits. Content Strategy is an agent skill from borghei/Claude-Skills. Plan content strategy: content pillars, audience research, topic clustering, funnel mapping, and content audits.
Content Strategy fits situations like: deciding what content to create; building a content calendar; planning topic clusters; finding content gaps.
Run `npx skills add borghei/Claude-Skills --skill content-strategy -a claude-code`. Or copy the skill folder (marketing/content-strategy in borghei/Claude-Skills) into .claude/skills/content-strategy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add borghei/Claude-Skills --skill content-strategy -a codex`. Or copy the skill folder (marketing/content-strategy in borghei/Claude-Skills) into .agents/skills/content-strategy in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-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.
Going by SKILL.md and its folder, Content Strategy needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
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.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
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.
About 5k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Content Strategy: Blogger Distiller (otter1101/blogger-distiller, 692 stars), Blog Post Drafting (luongnv89/claude-howto, 42k stars), Linkedin Content Planner (sergebulaev/linkedin-skills, 4.3k 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.
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 874 GitHub stars. The repository holds 364 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.