Agent skill

Content Production

by borghei in borghei/Claude-Skills

Full content production pipeline from blank page to publish-ready piece: research, briefs, drafting, SEO, readability, and editorial gates.

MITAuto-check passedWriting & Content

Install Content Production

skills CLI
$ npx skills add borghei/Claude-Skills --skill content-production -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills content-production --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
content-production
GitHub stars
881
Token cost
~4.8k tokens
SKILL.md length
2,258 words
Files
4 (incl. scripts)
Skills in repo
349
Repo updated
First seen
Licence
MIT

At a glance

Full content production pipeline from blank page to publish-ready piece: research, briefs, drafting, SEO, readability, and editorial gates.

  • Works in 5 steps: Research: analyze top 5 ranking pieces… → Brief: define keyword targets, angle,… → Draft: write with outline-first… → …
  • Writing blog posts
  • SKILL.md covers Table of Contents, Keywords, Clarify First and Quick Start, plus 10 more sections
  • Runs Python scripts from its folder; calls python

What it does

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.

When your agent uses it

  • Writing blog posts
  • Long-form content end-to-end at scale

Example prompts

  • “/content-production”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Research: analyze top 5 ranking pieces for the target keyword
  2. Brief: define keyword targets, angle, audience, and H2 structure
  3. Draft: write with outline-first approach, leading each section with its main point
  4. Optimize: SEO pass, readability pass, structure audit, meta tags
  5. Validate: run the quality gate checklist before publishing

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. 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

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    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 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.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 2,258 words, ~4,775 tokens.

Download SKILL.mdSave it as .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.
name
content-production
description
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.
license
MIT
metadata.version
1.0.0
metadata.author
borghei
metadata.category
marketing
metadata.domain
content
metadata.updated
2026-03-09

Content Production

The execution engine for content — taking topics from blank page to published, optimized, and distributed.


Table of Contents


Keywords

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


Clarify First

Before producing the content, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Primary keyword & search intent — the target query and whether it is informational/commercial (drives the brief Target + SEO pass)
  • Unique angle / core thesis — the one argument this piece makes (one angle per piece; drives the Angle section)
  • Target audience & awareness level — who reads it and what they already know (sets altitude and the Audience section)
  • Target word count — comprehensive guide vs. supporting post (drives scope and structure)

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.

Quick Start

Write a Blog Post End-to-End
  1. Research: analyze top 5 ranking pieces for the target keyword
  2. Brief: define keyword targets, angle, audience, and H2 structure
  3. Draft: write with outline-first approach, leading each section with its main point
  4. Optimize: SEO pass, readability pass, structure audit, meta tags
  5. Validate: run the quality gate checklist before publishing
Set Up Content Operations
  1. Define content pillars aligned with business goals
  2. Build an editorial calendar with 4-6 weeks of planned content
  3. Establish the production workflow (brief > draft > edit > optimize > publish)
  4. Set up repurposing workflow to multiply each piece across channels
  5. Define quality gates that every piece must pass before publishing

Core Workflows

Workflow 1: Research and Brief

Step 1: Competitive Content Analysis

Before writing, understand what already ranks for your target keyword:

  1. Identify the top 5-10 ranking pieces
  2. Map their angles and formats:
URLFormatWord CountKey AngleWhat's Missing
[URL 1]How-to guide2,400Step-by-step technicalNo real-world examples
[URL 2]Listicle1,800Tools comparisonOutdated, 2023 data
[URL 3]Expert roundup3,100Multiple perspectivesNo actionable framework
  1. Identify the content gap: what does nobody cover well?
  2. Verify search intent:
SERP PatternIntentWhat to Write
"What is / How to" dominateInformationalComprehensive guide or explainer
Product pages, reviewsCommercialComparison or buyer's guide
Forum results (Reddit, Quora)DiscoveryOpinionated piece with real perspective
News, recent articlesTrendingTimely take with unique angle

Step 2: Source Gathering

Collect 3-5 credible, citable sources before drafting:

  • Original research (studies, surveys, published reports)
  • Official documentation or industry standards
  • Expert quotes with full attribution
  • Data with specific numbers (not vague claims)

Rule: If you cannot cite a specific number, do not make a vague claim.

Step 3: Produce the Content Brief

markdown
## 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]
Workflow 2: Drafting

Step 1: Build the Outline

Before writing prose, create the header skeleton:

  • H1 that includes the keyword and creates curiosity
  • 4-7 H2 sections in logical progression
  • H3s only when a section genuinely needs subdivision
  • Conclusion with CTA

Step 2: Write the Introduction

The intro has one job: make the reader believe this piece answers their question.

Formula:

  1. Name the problem or situation the reader is in (1 sentence)
  2. Name what this piece does about it (1 sentence)
  3. Establish credibility if relevant (1 sentence, optional)

What to avoid:

  • "In today's digital landscape..." (everyone does this)
  • Starting with a question unless it is genuinely sharp
  • Three sentences of context before reaching the point

Step 3: Write Section by Section

For each H2:

  1. State the main point in the first sentence
  2. Prove it with an example, statistic, or comparison
  3. Provide one actionable takeaway before moving to the next section
  4. Use transitional phrases to connect sections naturally

Step 4: Write the Conclusion

Three elements:

  1. Summary of core argument (1-2 sentences, not a repeat of the intro)
  2. The single most important next step
  3. CTA aligned with the content goal
Workflow 3: Optimization Pipeline

Run these passes in order on every draft:

Pass 1: SEO Optimization

  • Title tag: contains primary keyword, under 60 characters, curiosity-driving
  • H1: different from title tag, keyword-rich, reads naturally
  • H2s: at least 2-3 contain secondary keywords or related phrases
  • First paragraph: primary keyword appears in first 100 words
  • Keyword density: primary keyword appears naturally 3-5 times (not stuffed)
  • Image alt text: descriptive, includes keyword where natural
  • URL slug: short, keyword-first, no stop words
  • Internal links: 2-4 minimum, linking to and from related content
  • External links: 1-3 to authoritative sources

Pass 2: Readability

  • Average sentence length: 15-20 words with variation
  • No paragraph exceeds 4 sentences
  • Active voice used in 80%+ of sentences
  • Jargon explained on first use for non-expert audiences
  • At least one visual element (image, table, diagram) per 500 words
  • Subheadings visible every 200-300 words
  • Readability score target: 60-70 (Flesch-Kincaid)

Pass 3: Structure Audit

  • Intro delivers on the headline's promise
  • Every H2 earns its place (cut sections that add no value)
  • At least 2 concrete examples or illustrations
  • Conclusion feels earned, not padded
  • Content flow follows logical progression
  • No orphan sections that could be merged

Pass 4: Meta Content

  • Meta description: 150-160 characters, includes keyword, ends with hook
  • OG title: optimized for social sharing (can differ from meta title)
  • OG description: optimized for social click-through
  • Canonical URL: set correctly
  • Schema markup: Article schema at minimum

Editorial Calendar Management

Calendar Structure
WeekMondayWednesdayFriday
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]
Content Types by Frequency
TypeFrequencyPurpose
Pillar posts (2,000+ words)2x/monthAuthority building, SEO ranking
Supporting posts (800-1,500 words)2-4x/monthTopic cluster depth, internal linking
Update/refresh existing posts2x/monthMaintain ranking, improve performance
Data/research pieces1x/monthBacklink attraction, original insights
Guest/collaboration1x/monthAudience expansion, backlinks
Production Timeline
StageOwnerDurationDeadline Relative to Publish
Brief creationStrategist1 dayPublish - 14 days
Research and outlineWriter2 daysPublish - 12 days
First draftWriter3 daysPublish - 9 days
Editorial reviewEditor2 daysPublish - 7 days
RevisionsWriter1 dayPublish - 5 days
SEO optimizationSEO lead1 dayPublish - 4 days
Final reviewEditor1 dayPublish - 3 days
Staging and QAOperations1 dayPublish - 2 days
PublishOperations—Publish day

Content Repurposing System

One Piece, Many Formats

Every pillar content piece should produce 5-8 derivative pieces:

SourceDerivativePlatformEffort
Blog postKey insight threadTwitter/XLow
Blog postCarousel of main pointsLinkedInMedium
Blog postShort-form video summaryTikTok/ReelsMedium
Blog postNewsletter sectionEmailLow
Blog postSlide deckSlideShare/LinkedInMedium
Blog postPodcast discussion topicPodcastLow
Blog postInfographicPinterest/BlogHigh
Blog postFAQ page contentWebsiteLow
Repurposing Workflow
  1. Publish the pillar piece — Let it index and get initial traction
  2. Extract 3-5 key insights — Each insight becomes a standalone social piece
  3. Adapt format per platform — Not copy-paste; reformat for each platform's norms
  4. Schedule distribution — Spread across 1-2 weeks after publication
  5. Cross-link everything — Social pieces link back to the pillar content
  6. Track performance — Identify which derivative formats drive the most traffic back
Evergreen Refresh Cycle

For high-performing content:

  • Review quarterly for accuracy and relevance
  • Update statistics and data points annually
  • Refresh publish date after significant updates
  • Re-promote refreshed content through social and email
  • Add new internal links as related content is published

Quality Gates

Show full SKILL.md (982 more words)Show less
Pre-Publish Checklist

Every piece must pass these gates before publishing:

Content Quality:

  • Core thesis is stated clearly in the first 200 words
  • Every factual claim has a source or is labeled as opinion
  • At least one image, table, or visual element
  • Introduction does not start with a cliche
  • Word count is within 10% of target
  • No AI-sounding patterns (run Content Humanizer audit if uncertain)

SEO Quality:

  • Primary keyword in title, H1, first 100 words, and 2+ H2s
  • Meta title under 60 characters with keyword
  • Meta description 150-160 characters with keyword and hook
  • All images have descriptive alt text
  • 2-4 internal links present and functional
  • URL slug is clean and keyword-first

Technical Quality:

  • All links verified and functional
  • Images optimized for web (compressed, appropriate dimensions)
  • Mobile rendering verified
  • Schema markup implemented
  • Canonical URL set
  • OG tags configured for social sharing

Editorial Quality:

  • Spelling and grammar checked
  • Consistent formatting throughout
  • Heading hierarchy maintained (H1 > H2 > H3, no skips)
  • Consistent voice and tone from start to finish
  • CTA present and aligned with content goal

Best Practices

  1. Brief first, always — Never start writing without a brief. Even a 5-minute brief prevents 2 hours of rewriting.

  2. 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.

  3. Front-load value — The reader should get something useful in the first 300 words. Do not make them scroll to find the point.

  4. Optimize existing before creating new — Refreshing a post ranked #8 to #3 produces more traffic than a new post starting at #50.

  5. 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.

  6. Kill your darlings — If a section does not serve the reader or the keyword strategy, cut it. Length without value hurts ranking.

  7. Batch production — Write briefs for 4-6 pieces at once, then draft in batches. Context-switching between briefing and writing reduces quality.

  8. Measure what matters — Track organic traffic, time on page, and conversion rate. Vanity metrics (word count, publishing frequency alone) are misleading.

  9. Repurpose systematically — Every pillar piece should produce 5+ derivative pieces. Build repurposing into the production workflow, not as an afterthought.

  10. Maintain a content debt backlog — Track content that needs updating, broken links, outdated statistics, and missing internal links. Address content debt regularly.


Integration Points

  • Content Strategy — Use for deciding what to write (topics, calendar, pillar structure). Content Production handles the execution.
  • Content Humanizer — Use after drafting when the piece sounds robotic. Run before the SEO optimization pass.
  • AI SEO — Use for optimizing specifically for AI search citation in addition to traditional SEO.
  • Copywriting — Use for landing pages, CTAs, and conversion copy. Content Production handles long-form content.
  • SEO Specialist — Use for technical SEO audits across the content library. Content Production handles per-piece optimization.
  • Social Content — Use for distributing and repurposing content across social platforms.
  • Copy Editing — Use for the editorial review pass within the production pipeline.

Troubleshooting

ProblemLikely CauseFix
Content consistently fails the quality gate checklistBriefs are incomplete or writers do not have enough contextInvest 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 10Content depth insufficient or missing E-E-A-T signals compared to page 1 resultsAdd original data, expert quotes, experience signals; increase word count to match or exceed top-ranking competitors
Content sounds robotic after AI-assisted draftingAI patterns not caught during editing passesRun Content Humanizer audit before SEO optimization pass; check for filler words, hedging, and structural uniformity
Internal linking neglected on new postsNot built into production workflowAdd "update 2-4 existing posts to link to new content" as a required step in every production checklist
Repurposing never happens despite planningRepurposing treated as afterthought instead of workflow stepBuild repurposing into the production timeline — schedule derivative content in the same editorial calendar
Production bottleneck at editorial review stageSingle editor reviewing all content; no SLA on review turnaroundSet 48-hour review SLA; create self-service checklists writers can run before submitting for review
Content outdated within 6 months of publishingNo refresh cycle establishedSchedule quarterly reviews for all content ranking top 20; update stats, links, and publish dates

Success Criteria

  • Production velocity: Maintaining planned cadence (2-4 pieces/week) with less than 10% schedule slippage
  • Quality gate pass rate: 90%+ of drafts passing the pre-publish quality gate checklist on first or second review
  • SEO optimization score: Average score of 75+ on the four-pass optimization pipeline (SEO, readability, structure, meta)
  • Readability score: Flesch Reading Ease of 60-70 across all published content (appropriate for web audiences)
  • Internal link coverage: Every new piece includes 3-5 internal links, and 3+ existing pieces updated to link back
  • Repurposing multiplier: Each pillar piece produces 5+ derivative pieces across social, email, and other channels
  • Content performance: 60%+ of content published in last 6 months generating organic impressions within 90 days

Scope & Limitations

In scope:

  • Full content production pipeline from brief to publish
  • Competitive research and source gathering for content briefs
  • Drafting methodology (outline-first, section-by-section)
  • Four-pass optimization pipeline (SEO, readability, structure, meta)
  • Editorial calendar management and production timelines
  • Content repurposing system across channels
  • Quality gates and pre-publish checklists

Out of scope:

  • Content strategy and topic selection (use Content Strategy)
  • AI content humanization (use Content Humanizer)
  • Detailed copy editing (use Copy Editing)
  • Technical SEO audits (use SEO Specialist)
  • Social media platform management (use Social Content)
  • Design and visual content creation

Known limitations:

  • 60% of marketing teams now use AI in content workflows (2026 data) — quality control processes must account for AI-assisted drafting
  • Production timelines assume dedicated writer and editor roles; solo operators need adjusted timelines
  • Content performance measurement requires Google Search Console and analytics access
  • Repurposing effectiveness varies by platform — not all derivative formats will perform equally

Scripts

bash
# 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

Files

SKILL.md and 3 other files (scripts) in marketing/content-production of borghei/Claude-Skills.

  • SKILL.md
  • scripts/content_brief_generator.py
  • scripts/headline_analyzer.py
  • scripts/readability_scorer.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

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.

Content Production compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Content Production this skillborghei/Claude-Skills881—~4.8kAutomated safety check: PassMIT
Content Creatorsickn33/agentic-awesome-skills47k1 repos~2.5kAutomated safety check: PassMIT
Content Creatorthatrebeccarae/claude-marketing162—~1.1kAutomated safety check: PassMIT
Readability Checkjdevalk/skills104—~3.3kAutomated safety check: PassMIT
Blog BriefAgriciDaniel/claude-blog2.3k—~3.2kAutomated safety check: PassMIT
Blog BriefAgriciDaniel/claude-blog2.3k—~3.3kAutomated safety check: PassMIT

Similar skills

  • 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.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Writing & ContentAuto-check passed
  • Content Creator

    thatrebeccarae/claude-marketing

    Comprehensive content marketing toolkit with brand voice analysis, SEO optimization scripts, content frameworks, social media strategy, and content calendar planning.

    162 GitHub stars~1.1k tokensUpdated 4 mo ago
    Writing & ContentAuto-check passed
  • Readability Check

    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.

    104 GitHub stars~3.3k tokensUpdated 3 mo ago
    Writing & ContentAuto-check passed
  • Blog Brief

    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…

    2.3k GitHub stars~3.2k tokensUpdated today
    Writing & ContentAuto-check passed
  • Blog Brief

    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…

    2.3k GitHub stars~3.3k tokensUpdated today
    Writing & ContentAuto-check passed
  • Writer

    flaqai/backlink_skills

    SEO-friendly article writing, audit, and humanization workflow for Markdown content.

    752 GitHub stars~5.8k tokensUpdated 14 days ago
    Writing & ContentAuto-check passed

More from borghei/Claude-Skills

All 349 skills in this repo
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    881 GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed
  • AI Content Disclosure

    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.

    881 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    881 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    881 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    881 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    881 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Questions about Content Production

What does Content Production do?

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.

When should I use Content Production?

Content Production fits situations like: writing blog posts; long-form content end-to-end at scale.

How do I install Content Production in Claude Code?

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.

How do I install Content Production in Codex?

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.

Can I use Content Production 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 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.

What does Content Production need to run?

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.

Does Content Production 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 Production 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Content Production use?

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.

How many tokens does Content Production use?

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.

What are the alternatives to Content Production?

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.

Who maintains Content Production?

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.