Content Creator
sickn33/agentic-awesome-skills
Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.
Full content production pipeline from blank page to publish-ready piece: research, briefs, drafting, SEO, readability, and editorial gates.
$ npx skills add borghei/Claude-Skills --skill content-production -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills content-production --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-production .claude/skills/content-production && 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-production" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/content-production into .claude/skills/content-production/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-production", 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-productionType 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-production -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills content-production --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-production .agents/skills/content-production && 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-production" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/content-production into .agents/skills/content-production/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-production", 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-production -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills content-production --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-production .cursor/skills/content-production && 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-production" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/content-production into .cursor/skills/content-production/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-production", 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-production--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-production -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills content-production --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-production .gemini/skills/content-production && 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-production" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/content-production into .gemini/skills/content-production/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-production", 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-productionInstalls 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-production -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-production .github/skills/content-production && 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-production" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/content-production into .github/skills/content-production/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-production", 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-production -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-production --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-production .opencode/skills/content-production && 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-production" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/content-production into .opencode/skills/content-production/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-production", 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-productionFull content production pipeline from blank page to publish-ready piece: research, briefs, drafting, SEO, readability, and editorial gates.
Content Production is an agent skill from borghei/Claude-Skills. Full content production pipeline from blank page to publish-ready piece: research, briefs, drafting, SEO, readability, and editorial gates. Use when writing blog posts, articles, guides, or long-form content end-to-end at scale.
Its SKILL.md is about 4.8k 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/headline_analyzer.py` and `scripts/readability_scorer.py`).
It sits in Writing & Content, covering Blog and article writing, Plain language and style rules and Deep research. 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.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 4a698e8. 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 Production loads about 4.8k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 2,258 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 4a698e8, republished under its MIT licence (© borghei). 2,258 words, ~4,775 tokens.
.claude/skills/content-production/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.The execution engine for content — taking topics from blank page to published, optimized, and distributed.
content production, blog writing, article drafting, content pipeline, editorial workflow, content operations, content calendar, content brief, SEO content, content optimization, readability, internal linking, meta tags, content repurposing, content at scale, editorial calendar, content quality, publishing workflow, long-form content, content management
Before producing the content, 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: Competitive Content Analysis
Before writing, understand what already ranks for your target keyword:
| URL | Format | Word Count | Key Angle | What's Missing |
|---|---|---|---|---|
| [URL 1] | How-to guide | 2,400 | Step-by-step technical | No real-world examples |
| [URL 2] | Listicle | 1,800 | Tools comparison | Outdated, 2023 data |
| [URL 3] | Expert roundup | 3,100 | Multiple perspectives | No actionable framework |
| SERP Pattern | Intent | What to Write |
|---|---|---|
| "What is / How to" dominate | Informational | Comprehensive guide or explainer |
| Product pages, reviews | Commercial | Comparison or buyer's guide |
| Forum results (Reddit, Quora) | Discovery | Opinionated piece with real perspective |
| News, recent articles | Trending | Timely take with unique angle |
Step 2: Source Gathering
Collect 3-5 credible, citable sources before drafting:
Rule: If you cannot cite a specific number, do not make a vague claim.
Step 3: Produce the Content Brief
## Content Brief
### Target
- Primary keyword: [keyword] (volume: [X], difficulty: [X])
- Secondary keywords: [keyword 1], [keyword 2], [keyword 3]
- Search intent: [Informational / Commercial / Transactional]
### Audience
- Reader profile: [Who they are and what they know]
- Job-to-be-done: [What problem they are solving right now]
- Awareness level: [Unaware / Problem-aware / Solution-aware]
### Angle
- Unique perspective: [What makes this piece different]
- Core argument: [The single thesis of this piece]
- Key claims to prove: [3-5 specific claims with supporting evidence]
### Structure
- H1: [Working title]
- H2: [Section 1]
- H2: [Section 2]
- H2: [Section 3]
- H2: [Section 4]
- H2: [Conclusion / Next Steps]
### Requirements
- Target word count: [X]
- Internal links to include: [List existing pages to link to]
- Competitive pieces to beat: [Top 3 URLs to outperform]
- CTA: [What action should the reader take]Step 1: Build the Outline
Before writing prose, create the header skeleton:
Step 2: Write the Introduction
The intro has one job: make the reader believe this piece answers their question.
Formula:
What to avoid:
Step 3: Write Section by Section
For each H2:
Step 4: Write the Conclusion
Three elements:
Run these passes in order on every draft:
Pass 1: SEO Optimization
Pass 2: Readability
Pass 3: Structure Audit
Pass 4: Meta Content
| Week | Monday | Wednesday | Friday |
|---|---|---|---|
| 1 | [Pillar topic A] | [Supporting topic B] | [Social repurpose] |
| 2 | [Pillar topic C] | [Guest/collab piece] | [Update old post] |
| 3 | [Pillar topic A] | [Supporting topic D] | [Social repurpose] |
| 4 | [Data/research piece] | [Supporting topic E] | [Roundup/compilation] |
| Type | Frequency | Purpose |
|---|---|---|
| Pillar posts (2,000+ words) | 2x/month | Authority building, SEO ranking |
| Supporting posts (800-1,500 words) | 2-4x/month | Topic cluster depth, internal linking |
| Update/refresh existing posts | 2x/month | Maintain ranking, improve performance |
| Data/research pieces | 1x/month | Backlink attraction, original insights |
| Guest/collaboration | 1x/month | Audience expansion, backlinks |
| Stage | Owner | Duration | Deadline Relative to Publish |
|---|---|---|---|
| Brief creation | Strategist | 1 day | Publish - 14 days |
| Research and outline | Writer | 2 days | Publish - 12 days |
| First draft | Writer | 3 days | Publish - 9 days |
| Editorial review | Editor | 2 days | Publish - 7 days |
| Revisions | Writer | 1 day | Publish - 5 days |
| SEO optimization | SEO lead | 1 day | Publish - 4 days |
| Final review | Editor | 1 day | Publish - 3 days |
| Staging and QA | Operations | 1 day | Publish - 2 days |
| Publish | Operations | — | Publish day |
Every pillar content piece should produce 5-8 derivative pieces:
| Source | Derivative | Platform | Effort |
|---|---|---|---|
| Blog post | Key insight thread | Twitter/X | Low |
| Blog post | Carousel of main points | Medium | |
| Blog post | Short-form video summary | TikTok/Reels | Medium |
| Blog post | Newsletter section | Low | |
| Blog post | Slide deck | SlideShare/LinkedIn | Medium |
| Blog post | Podcast discussion topic | Podcast | Low |
| Blog post | Infographic | Pinterest/Blog | High |
| Blog post | FAQ page content | Website | Low |
For high-performing content:
Every piece must pass these gates before publishing:
Content Quality:
SEO Quality:
Technical Quality:
Editorial Quality:
Brief first, always — Never start writing without a brief. Even a 5-minute brief prevents 2 hours of rewriting.
One angle per piece — A piece that tries to be a how-to, a comparison, and an opinion piece fails at all three. Pick one angle.
Front-load value — The reader should get something useful in the first 300 words. Do not make them scroll to find the point.
Optimize existing before creating new — Refreshing a post ranked #8 to #3 produces more traffic than a new post starting at #50.
Internal linking is not optional — Every new piece should link to 2-4 existing pieces, and 2-4 existing pieces should be updated to link to the new piece.
Kill your darlings — If a section does not serve the reader or the keyword strategy, cut it. Length without value hurts ranking.
Batch production — Write briefs for 4-6 pieces at once, then draft in batches. Context-switching between briefing and writing reduces quality.
Measure what matters — Track organic traffic, time on page, and conversion rate. Vanity metrics (word count, publishing frequency alone) are misleading.
Repurpose systematically — Every pillar piece should produce 5+ derivative pieces. Build repurposing into the production workflow, not as an afterthought.
Maintain a content debt backlog — Track content that needs updating, broken links, outdated statistics, and missing internal links. Address content debt regularly.
| Problem | Likely Cause | Fix |
|---|---|---|
| Content consistently fails the quality gate checklist | Briefs are incomplete or writers do not have enough context | Invest more time in brief creation — include target keyword, angle, audience, H2 structure, and competitive gaps |
| Published content ranks #15-30 but does not break into top 10 | Content depth insufficient or missing E-E-A-T signals compared to page 1 results | Add original data, expert quotes, experience signals; increase word count to match or exceed top-ranking competitors |
| Content sounds robotic after AI-assisted drafting | AI patterns not caught during editing passes | Run Content Humanizer audit before SEO optimization pass; check for filler words, hedging, and structural uniformity |
| Internal linking neglected on new posts | Not built into production workflow | Add "update 2-4 existing posts to link to new content" as a required step in every production checklist |
| Repurposing never happens despite planning | Repurposing treated as afterthought instead of workflow step | Build repurposing into the production timeline — schedule derivative content in the same editorial calendar |
| Production bottleneck at editorial review stage | Single editor reviewing all content; no SLA on review turnaround | Set 48-hour review SLA; create self-service checklists writers can run before submitting for review |
| Content outdated within 6 months of publishing | No refresh cycle established | Schedule quarterly reviews for all content ranking top 20; update stats, links, and publish dates |
In scope:
Out of scope:
Known limitations:
# Score content readability with detailed metrics
python scripts/readability_scorer.py article.md --json
# Generate a content brief from keyword research
python scripts/content_brief_generator.py --keyword "cloud cost optimization" --json
# Analyze headline options for a new piece
python scripts/headline_analyzer.py --headlines headlines.txt --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-production of borghei/Claude-Skills.
Open the folder on GitHubat commit 4a698e8
Content Production 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 Production this skillborghei/Claude-Skills | 881 | — | ~4.8k | Automated safety check: Pass | MIT | |
| Content Creatorsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Content Creatorthatrebeccarae/claude-marketing | 162 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Readability Checkjdevalk/skills | 104 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Blog BriefAgriciDaniel/claude-blog | 2.3k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Blog BriefAgriciDaniel/claude-blog | 2.3k | — | ~3.3k | Automated safety check: Pass | MIT |
sickn33/agentic-awesome-skills
Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.
thatrebeccarae/claude-marketing
Comprehensive content marketing toolkit with brand voice analysis, SEO optimization scripts, content frameworks, social media strategy, and content calendar planning.
jdevalk/skills
Runs a readability audit on a blog post draft or other multi-paragraph prose, calibrated for readers who read English as a second language.
AgriciDaniel/claude-blog
Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…
AgriciDaniel/claude-blog
Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…
flaqai/backlink_skills
SEO-friendly article writing, audit, and humanization workflow for Markdown content.
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
Full content production pipeline from blank page to publish-ready piece: research, briefs, drafting, SEO, readability, and editorial gates. Content Production is an agent skill from borghei/Claude-Skills. Full content production pipeline from blank page to publish-ready piece: research, briefs, drafting, SEO, readability, and editorial gates.
Content Production fits situations like: writing blog posts; long-form content end-to-end at scale.
Run `npx skills add borghei/Claude-Skills --skill content-production -a claude-code`. Or copy the skill folder (marketing/content-production in borghei/Claude-Skills) into .claude/skills/content-production in your project. Claude Code loads it when a task matches its description.
Run `npx skills add borghei/Claude-Skills --skill content-production -a codex`. Or copy the skill folder (marketing/content-production in borghei/Claude-Skills) into .agents/skills/content-production 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-production -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-production, .gemini/skills/content-production, .github/skills/content-production and .opencode/skills/content-production in your project.
Going by SKILL.md and its folder, Content Production 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 Production is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.8k tokens (SKILL.md is roughly 19k 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 Production: Content Creator (sickn33/agentic-awesome-skills, 47k stars), Content Creator (thatrebeccarae/claude-marketing, 162 stars), Readability Check (jdevalk/skills, 104 stars) and Blog Brief (AgriciDaniel/claude-blog, 2.3k 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 881 GitHub stars. The repository holds 349 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.