This skill should be used when the user asks to "check accessibility", "audit WCAG compliance", "scan HTML for a11y issues", "check color contrast", or "find accessibility violations in web pages".
日本語の概要は準備中です。原文の説明を表示しています。
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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
This skill should be used when the user asks to "check accessibility", "audit WCAG compliance", "scan HTML for a11y issues", "check color contrast", or "find accessibility violations in web pages".
日本語の概要は準備中です。原文の説明を表示しています。
Design and run statistically rigorous A/B tests and experiments. Use when planning experiments, calculating sample sizes, designing test variants, selecting metrics, analyzing results, or when someone says "let's test that."
日本語の概要は準備中です。原文の説明を表示しています。
Design and analyze A/B tests: sample size, test duration, and statistical significance for conversion experiments. Use when setting up an A/B test, calculating sample size, designing an experiment, or analyzing results.
日本語の概要は準備中です。原文の説明を表示しています。
Sales execution across pipeline, discovery, demos, negotiation, and closing. Use when qualifying opportunities, running MEDDIC discovery, building account plans, handling objections, structuring proposals, or forecasting pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Design ad creative across Google, Meta, LinkedIn, Twitter/X, and TikTok with platform format specs, headline formulas, and A/B testing. Use when writing ad copy, generating headline variations, creating ad sets, or validating creative.
日本語の概要は準備中です。原文の説明を表示しています。
Answer Engine Optimization (AEO): optimize content to be cited by LLMs (ChatGPT, Claude, Perplexity, Gemini) in their answers. Use when designing content for LLM citation, auditing citability, or structuring Q&A schema.
日本語の概要は準備中です。原文の説明を表示しています。