[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MS5ADRFW93K1FJR2PW58VC":3,"skill-same:01M6MS5ADRFW93K1FJR2PW58VC":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":36,"publishedAt":57,"linkOnly":58,"markdownContent":59,"markdownBody":60,"frontMatter":61,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":13,"repositoryHtmlUrl":70,"repositoryHomepageUrl":6,"ownerHtmlUrl":71,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":72,"install":73,"resources":86},"01M6MS5ADRFW93K1FJR2PW58VC","content-production",null,"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.","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-03-claude-skills-main-marketing-content-production-skill-9f4b6c66\u002FSKILL.md",[17,22,25,28,33],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":29,"categoryName":30,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":34,"categoryName":35,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000036","内容创作者",[37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56],"content","Production","content production","editorial","writing","long-form","at","briefs","posts","form","guides","end","full","readability","ready","page","marketing","seo","pipeline","publish","2026-11-10 10:12:30",false,"---\nname: content-production\ndescription: >\n  Full content production pipeline from blank page to publish-ready piece:\n  research, briefs, drafting, SEO, readability, and editorial gates. Use when\n  writing blog posts, articles, guides, or long-form content end-to-end at scale.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: borghei\n  category: marketing\n  domain: content\n  updated: 2026-03-09\n---\n# Content Production\n\nThe execution engine for content — taking topics from blank page to published, optimized, and distributed.\n\n---\n\n## Table of Contents\n\n- [Keywords](#keywords)\n- [Quick Start](#quick-start)\n- [Core Workflows](#core-workflows)\n- [Content Brief Framework](#content-brief-framework)\n- [Drafting Methodology](#drafting-methodology)\n- [Optimization Pipeline](#optimization-pipeline)\n- [Editorial Calendar Management](#editorial-calendar-management)\n- [Content Repurposing System](#content-repurposing-system)\n- [Quality Gates](#quality-gates)\n- [Best Practices](#best-practices)\n- [Integration Points](#integration-points)\n\n---\n\n## Keywords\n\ncontent 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\n\n---\n\n## Clarify First\n\nBefore producing the content, confirm these inputs. If any is unknown or vague, ASK — do not assume:\n\n- [ ] **Primary keyword & search intent** — the target query and whether it is informational\u002Fcommercial (drives the brief Target + SEO pass)\n- [ ] **Unique angle \u002F core thesis** — the one argument this piece makes (one angle per piece; drives the Angle section)\n- [ ] **Target audience & awareness level** — who reads it and what they already know (sets altitude and the Audience section)\n- [ ] **Target word count** — comprehensive guide vs. supporting post (drives scope and structure)\n\nStop 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.\n\n## Quick Start\n\n### Write a Blog Post End-to-End\n\n1. Research: analyze top 5 ranking pieces for the target keyword\n2. Brief: define keyword targets, angle, audience, and H2 structure\n3. Draft: write with outline-first approach, leading each section with its main point\n4. Optimize: SEO pass, readability pass, structure audit, meta tags\n5. Validate: run the quality gate checklist before publishing\n\n### Set Up Content Operations\n\n1. Define content pillars aligned with business goals\n2. Build an editorial calendar with 4-6 weeks of planned content\n3. Establish the production workflow (brief > draft > edit > optimize > publish)\n4. Set up repurposing workflow to multiply each piece across channels\n5. Define quality gates that every piece must pass before publishing\n\n---\n\n## Core Workflows\n\n### Workflow 1: Research and Brief\n\n**Step 1: Competitive Content Analysis**\n\nBefore writing, understand what already ranks for your target keyword:\n\n1. Identify the top 5-10 ranking pieces\n2. Map their angles and formats:\n\n| URL | Format | Word Count | Key Angle | What's Missing |\n|-----|--------|-----------|-----------|----------------|\n| [URL 1] | How-to guide | 2,400 | Step-by-step technical | No real-world examples |\n| [URL 2] | Listicle | 1,800 | Tools comparison | Outdated, 2023 data |\n| [URL 3] | Expert roundup | 3,100 | Multiple perspectives | No actionable framework |\n\n3. Identify the content gap: what does nobody cover well?\n4. Verify search intent:\n\n| SERP Pattern | Intent | What to Write |\n|-------------|--------|---------------|\n| \"What is \u002F How to\" dominate | Informational | Comprehensive guide or explainer |\n| Product pages, reviews | Commercial | Comparison or buyer's guide |\n| Forum results (Reddit, Quora) | Discovery | Opinionated piece with real perspective |\n| News, recent articles | Trending | Timely take with unique angle |\n\n**Step 2: Source Gathering**\n\nCollect 3-5 credible, citable sources before drafting:\n- Original research (studies, surveys, published reports)\n- Official documentation or industry standards\n- Expert quotes with full attribution\n- Data with specific numbers (not vague claims)\n\nRule: If you cannot cite a specific number, do not make a vague claim.\n\n**Step 3: Produce the Content Brief**\n\n```markdown\n## Content Brief\n\n### Target\n- Primary keyword: [keyword] (volume: [X], difficulty: [X])\n- Secondary keywords: [keyword 1], [keyword 2], [keyword 3]\n- Search intent: [Informational \u002F Commercial \u002F Transactional]\n\n### Audience\n- Reader profile: [Who they are and what they know]\n- Job-to-be-done: [What problem they are solving right now]\n- Awareness level: [Unaware \u002F Problem-aware \u002F Solution-aware]\n\n### Angle\n- Unique perspective: [What makes this piece different]\n- Core argument: [The single thesis of this piece]\n- Key claims to prove: [3-5 specific claims with supporting evidence]\n\n### Structure\n- H1: [Working title]\n- H2: [Section 1]\n- H2: [Section 2]\n- H2: [Section 3]\n- H2: [Section 4]\n- H2: [Conclusion \u002F Next Steps]\n\n### Requirements\n- Target word count: [X]\n- Internal links to include: [List existing pages to link to]\n- Competitive pieces to beat: [Top 3 URLs to outperform]\n- CTA: [What action should the reader take]\n```\n\n### Workflow 2: Drafting\n\n**Step 1: Build the Outline**\n\nBefore writing prose, create the header skeleton:\n- H1 that includes the keyword and creates curiosity\n- 4-7 H2 sections in logical progression\n- H3s only when a section genuinely needs subdivision\n- Conclusion with CTA\n\n**Step 2: Write the Introduction**\n\nThe intro has one job: make the reader believe this piece answers their question.\n\nFormula:\n1. Name the problem or situation the reader is in (1 sentence)\n2. Name what this piece does about it (1 sentence)\n3. Establish credibility if relevant (1 sentence, optional)\n\nWhat to avoid:\n- \"In today's digital landscape...\" (everyone does this)\n- Starting with a question unless it is genuinely sharp\n- Three sentences of context before reaching the point\n\n**Step 3: Write Section by Section**\n\nFor each H2:\n1. State the main point in the first sentence\n2. Prove it with an example, statistic, or comparison\n3. Provide one actionable takeaway before moving to the next section\n4. Use transitional phrases to connect sections naturally\n\n**Step 4: Write the Conclusion**\n\nThree elements:\n1. Summary of core argument (1-2 sentences, not a repeat of the intro)\n2. The single most important next step\n3. CTA aligned with the content goal\n\n### Workflow 3: Optimization Pipeline\n\nRun these passes in order on every draft:\n\n**Pass 1: SEO Optimization**\n\n- [ ] Title tag: contains primary keyword, under 60 characters, curiosity-driving\n- [ ] H1: different from title tag, keyword-rich, reads naturally\n- [ ] H2s: at least 2-3 contain secondary keywords or related phrases\n- [ ] First paragraph: primary keyword appears in first 100 words\n- [ ] Keyword density: primary keyword appears naturally 3-5 times (not stuffed)\n- [ ] Image alt text: descriptive, includes keyword where natural\n- [ ] URL slug: short, keyword-first, no stop words\n- [ ] Internal links: 2-4 minimum, linking to and from related content\n- [ ] External links: 1-3 to authoritative sources\n\n**Pass 2: Readability**\n\n- [ ] Average sentence length: 15-20 words with variation\n- [ ] No paragraph exceeds 4 sentences\n- [ ] Active voice used in 80%+ of sentences\n- [ ] Jargon explained on first use for non-expert audiences\n- [ ] At least one visual element (image, table, diagram) per 500 words\n- [ ] Subheadings visible every 200-300 words\n- [ ] Readability score target: 60-70 (Flesch-Kincaid)\n\n**Pass 3: Structure Audit**\n\n- [ ] Intro delivers on the headline's promise\n- [ ] Every H2 earns its place (cut sections that add no value)\n- [ ] At least 2 concrete examples or illustrations\n- [ ] Conclusion feels earned, not padded\n- [ ] Content flow follows logical progression\n- [ ] No orphan sections that could be merged\n\n**Pass 4: Meta Content**\n\n- [ ] Meta description: 150-160 characters, includes keyword, ends with hook\n- [ ] OG title: optimized for social sharing (can differ from meta title)\n- [ ] OG description: optimized for social click-through\n- [ ] Canonical URL: set correctly\n- [ ] Schema markup: Article schema at minimum\n\n---\n\n## Editorial Calendar Management\n\n### Calendar Structure\n\n| Week | Monday | Wednesday | Friday |\n|------|--------|-----------|--------|\n| 1 | [Pillar topic A] | [Supporting topic B] | [Social repurpose] |\n| 2 | [Pillar topic C] | [Guest\u002Fcollab piece] | [Update old post] |\n| 3 | [Pillar topic A] | [Supporting topic D] | [Social repurpose] |\n| 4 | [Data\u002Fresearch piece] | [Supporting topic E] | [Roundup\u002Fcompilation] |\n\n### Content Types by Frequency\n\n| Type | Frequency | Purpose |\n|------|-----------|---------|\n| Pillar posts (2,000+ words) | 2x\u002Fmonth | Authority building, SEO ranking |\n| Supporting posts (800-1,500 words) | 2-4x\u002Fmonth | Topic cluster depth, internal linking |\n| Update\u002Frefresh existing posts | 2x\u002Fmonth | Maintain ranking, improve performance |\n| Data\u002Fresearch pieces | 1x\u002Fmonth | Backlink attraction, original insights |\n| Guest\u002Fcollaboration | 1x\u002Fmonth | Audience expansion, backlinks |\n\n### Production Timeline\n\n| Stage | Owner | Duration | Deadline Relative to Publish |\n|-------|-------|----------|---------------------------|\n| Brief creation | Strategist | 1 day | Publish - 14 days |\n| Research and outline | Writer | 2 days | Publish - 12 days |\n| First draft | Writer | 3 days | Publish - 9 days |\n| Editorial review | Editor | 2 days | Publish - 7 days |\n| Revisions | Writer | 1 day | Publish - 5 days |\n| SEO optimization | SEO lead | 1 day | Publish - 4 days |\n| Final review | Editor | 1 day | Publish - 3 days |\n| Staging and QA | Operations | 1 day | Publish - 2 days |\n| Publish | Operations | — | Publish day |\n\n---\n\n## Content Repurposing System\n\n### One Piece, Many Formats\n\nEvery pillar content piece should produce 5-8 derivative pieces:\n\n| Source | Derivative | Platform | Effort |\n|--------|-----------|----------|--------|\n| Blog post | Key insight thread | Twitter\u002FX | Low |\n| Blog post | Carousel of main points | LinkedIn | Medium |\n| Blog post | Short-form video summary | TikTok\u002FReels | Medium |\n| Blog post | Newsletter section | Email | Low |\n| Blog post | Slide deck | SlideShare\u002FLinkedIn | Medium |\n| Blog post | Podcast discussion topic | Podcast | Low |\n| Blog post | Infographic | Pinterest\u002FBlog | High |\n| Blog post | FAQ page content | Website | Low |\n\n### Repurposing Workflow\n\n1. **Publish the pillar piece** — Let it index and get initial traction\n2. **Extract 3-5 key insights** — Each insight becomes a standalone social piece\n3. **Adapt format per platform** — Not copy-paste; reformat for each platform's norms\n4. **Schedule distribution** — Spread across 1-2 weeks after publication\n5. **Cross-link everything** — Social pieces link back to the pillar content\n6. **Track performance** — Identify which derivative formats drive the most traffic back\n\n### Evergreen Refresh Cycle\n\nFor high-performing content:\n- Review quarterly for accuracy and relevance\n- Update statistics and data points annually\n- Refresh publish date after significant updates\n- Re-promote refreshed content through social and email\n- Add new internal links as related content is published\n\n---\n\n## Quality Gates\n\n### Pre-Publish Checklist\n\nEvery piece must pass these gates before publishing:\n\n**Content Quality:**\n- [ ] Core thesis is stated clearly in the first 200 words\n- [ ] Every factual claim has a source or is labeled as opinion\n- [ ] At least one image, table, or visual element\n- [ ] Introduction does not start with a cliche\n- [ ] Word count is within 10% of target\n- [ ] No AI-sounding patterns (run Content Humanizer audit if uncertain)\n\n**SEO Quality:**\n- [ ] Primary keyword in title, H1, first 100 words, and 2+ H2s\n- [ ] Meta title under 60 characters with keyword\n- [ ] Meta description 150-160 characters with keyword and hook\n- [ ] All images have descriptive alt text\n- [ ] 2-4 internal links present and functional\n- [ ] URL slug is clean and keyword-first\n\n**Technical Quality:**\n- [ ] All links verified and functional\n- [ ] Images optimized for web (compressed, appropriate dimensions)\n- [ ] Mobile rendering verified\n- [ ] Schema markup implemented\n- [ ] Canonical URL set\n- [ ] OG tags configured for social sharing\n\n**Editorial Quality:**\n- [ ] Spelling and grammar checked\n- [ ] Consistent formatting throughout\n- [ ] Heading hierarchy maintained (H1 > H2 > H3, no skips)\n- [ ] Consistent voice and tone from start to finish\n- [ ] CTA present and aligned with content goal\n\n---\n\n## Best Practices\n\n1. **Brief first, always** — Never start writing without a brief. Even a 5-minute brief prevents 2 hours of rewriting.\n\n2. **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.\n\n3. **Front-load value** — The reader should get something useful in the first 300 words. Do not make them scroll to find the point.\n\n4. **Optimize existing before creating new** — Refreshing a post ranked #8 to #3 produces more traffic than a new post starting at #50.\n\n5. **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.\n\n6. **Kill your darlings** — If a section does not serve the reader or the keyword strategy, cut it. Length without value hurts ranking.\n\n7. **Batch production** — Write briefs for 4-6 pieces at once, then draft in batches. Context-switching between briefing and writing reduces quality.\n\n8. **Measure what matters** — Track organic traffic, time on page, and conversion rate. Vanity metrics (word count, publishing frequency alone) are misleading.\n\n9. **Repurpose systematically** — Every pillar piece should produce 5+ derivative pieces. Build repurposing into the production workflow, not as an afterthought.\n\n10. **Maintain a content debt backlog** — Track content that needs updating, broken links, outdated statistics, and missing internal links. Address content debt regularly.\n\n---\n\n## Integration Points\n\n- **Content Strategy** — Use for deciding what to write (topics, calendar, pillar structure). Content Production handles the execution.\n- **Content Humanizer** — Use after drafting when the piece sounds robotic. Run before the SEO optimization pass.\n- **AI SEO** — Use for optimizing specifically for AI search citation in addition to traditional SEO.\n- **Copywriting** — Use for landing pages, CTAs, and conversion copy. Content Production handles long-form content.\n- **SEO Specialist** — Use for technical SEO audits across the content library. Content Production handles per-piece optimization.\n- **Social Content** — Use for distributing and repurposing content across social platforms.\n- **Copy Editing** — Use for the editorial review pass within the production pipeline.\n\n---\n\n## Troubleshooting\n\n| Problem | Likely Cause | Fix |\n|---------|-------------|-----|\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n\n---\n\n## Success Criteria\n\n- **Production velocity**: Maintaining planned cadence (2-4 pieces\u002Fweek) with less than 10% schedule slippage\n- **Quality gate pass rate**: 90%+ of drafts passing the pre-publish quality gate checklist on first or second review\n- **SEO optimization score**: Average score of 75+ on the four-pass optimization pipeline (SEO, readability, structure, meta)\n- **Readability score**: Flesch Reading Ease of 60-70 across all published content (appropriate for web audiences)\n- **Internal link coverage**: Every new piece includes 3-5 internal links, and 3+ existing pieces updated to link back\n- **Repurposing multiplier**: Each pillar piece produces 5+ derivative pieces across social, email, and other channels\n- **Content performance**: 60%+ of content published in last 6 months generating organic impressions within 90 days\n\n---\n\n## Scope & Limitations\n\n**In scope:**\n- Full content production pipeline from brief to publish\n- Competitive research and source gathering for content briefs\n- Drafting methodology (outline-first, section-by-section)\n- Four-pass optimization pipeline (SEO, readability, structure, meta)\n- Editorial calendar management and production timelines\n- Content repurposing system across channels\n- Quality gates and pre-publish checklists\n\n**Out of scope:**\n- Content strategy and topic selection (use Content Strategy)\n- AI content humanization (use Content Humanizer)\n- Detailed copy editing (use Copy Editing)\n- Technical SEO audits (use SEO Specialist)\n- Social media platform management (use Social Content)\n- Design and visual content creation\n\n**Known limitations:**\n- 60% of marketing teams now use AI in content workflows (2026 data) — quality control processes must account for AI-assisted drafting\n- Production timelines assume dedicated writer and editor roles; solo operators need adjusted timelines\n- Content performance measurement requires Google Search Console and analytics access\n- Repurposing effectiveness varies by platform — not all derivative formats will perform equally\n\n---\n\n## Scripts\n\n```bash\n# Score content readability with detailed metrics\npython scripts\u002Freadability_scorer.py article.md --json\n\n# Generate a content brief from keyword research\npython scripts\u002Fcontent_brief_generator.py --keyword \"cloud cost optimization\" --json\n\n# Analyze headline options for a new piece\npython scripts\u002Fheadline_analyzer.py --headlines headlines.txt --json\n```\n","# Content Production\n\nThe execution engine for content — taking topics from blank page to published, optimized, and distributed.\n\n---\n\n## Table of Contents\n\n- [Keywords](#keywords)\n- [Quick Start](#quick-start)\n- [Core Workflows](#core-workflows)\n- [Content Brief Framework](#content-brief-framework)\n- [Drafting Methodology](#drafting-methodology)\n- [Optimization Pipeline](#optimization-pipeline)\n- [Editorial Calendar Management](#editorial-calendar-management)\n- [Content Repurposing System](#content-repurposing-system)\n- [Quality Gates](#quality-gates)\n- [Best Practices](#best-practices)\n- [Integration Points](#integration-points)\n\n---\n\n## Keywords\n\ncontent 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\n\n---\n\n## Clarify First\n\nBefore producing the content, confirm these inputs. If any is unknown or vague, ASK — do not assume:\n\n- [ ] **Primary keyword & search intent** — the target query and whether it is informational\u002Fcommercial (drives the brief Target + SEO pass)\n- [ ] **Unique angle \u002F core thesis** — the one argument this piece makes (one angle per piece; drives the Angle section)\n- [ ] **Target audience & awareness level** — who reads it and what they already know (sets altitude and the Audience section)\n- [ ] **Target word count** — comprehensive guide vs. supporting post (drives scope and structure)\n\nStop 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.\n\n## Quick Start\n\n### Write a Blog Post End-to-End\n\n1. Research: analyze top 5 ranking pieces for the target keyword\n2. Brief: define keyword targets, angle, audience, and H2 structure\n3. Draft: write with outline-first approach, leading each section with its main point\n4. Optimize: SEO pass, readability pass, structure audit, meta tags\n5. Validate: run the quality gate checklist before publishing\n\n### Set Up Content Operations\n\n1. Define content pillars aligned with business goals\n2. Build an editorial calendar with 4-6 weeks of planned content\n3. Establish the production workflow (brief > draft > edit > optimize > publish)\n4. Set up repurposing workflow to multiply each piece across channels\n5. Define quality gates that every piece must pass before publishing\n\n---\n\n## Core Workflows\n\n### Workflow 1: Research and Brief\n\n**Step 1: Competitive Content Analysis**\n\nBefore writing, understand what already ranks for your target keyword:\n\n1. Identify the top 5-10 ranking pieces\n2. Map their angles and formats:\n\n| URL | Format | Word Count | Key Angle | What's Missing |\n|-----|--------|-----------|-----------|----------------|\n| [URL 1] | How-to guide | 2,400 | Step-by-step technical | No real-world examples |\n| [URL 2] | Listicle | 1,800 | Tools comparison | Outdated, 2023 data |\n| [URL 3] | Expert roundup | 3,100 | Multiple perspectives | No actionable framework |\n\n3. Identify the content gap: what does nobody cover well?\n4. Verify search intent:\n\n| SERP Pattern | Intent | What to Write |\n|-------------|--------|---------------|\n| \"What is \u002F How to\" dominate | Informational | Comprehensive guide or explainer |\n| Product pages, reviews | Commercial | Comparison or buyer's guide |\n| Forum results (Reddit, Quora) | Discovery | Opinionated piece with real perspective |\n| News, recent articles | Trending | Timely take with unique angle |\n\n**Step 2: Source Gathering**\n\nCollect 3-5 credible, citable sources before drafting:\n- Original research (studies, surveys, published reports)\n- Official documentation or industry standards\n- Expert quotes with full attribution\n- Data with specific numbers (not vague claims)\n\nRule: If you cannot cite a specific number, do not make a vague claim.\n\n**Step 3: Produce the Content Brief**\n\n```markdown\n## Content Brief\n\n### Target\n- Primary keyword: [keyword] (volume: [X], difficulty: [X])\n- Secondary keywords: [keyword 1], [keyword 2], [keyword 3]\n- Search intent: [Informational \u002F Commercial \u002F Transactional]\n\n### Audience\n- Reader profile: [Who they are and what they know]\n- Job-to-be-done: [What problem they are solving right now]\n- Awareness level: [Unaware \u002F Problem-aware \u002F Solution-aware]\n\n### Angle\n- Unique perspective: [What makes this piece different]\n- Core argument: [The single thesis of this piece]\n- Key claims to prove: [3-5 specific claims with supporting evidence]\n\n### Structure\n- H1: [Working title]\n- H2: [Section 1]\n- H2: [Section 2]\n- H2: [Section 3]\n- H2: [Section 4]\n- H2: [Conclusion \u002F Next Steps]\n\n### Requirements\n- Target word count: [X]\n- Internal links to include: [List existing pages to link to]\n- Competitive pieces to beat: [Top 3 URLs to outperform]\n- CTA: [What action should the reader take]\n```\n\n### Workflow 2: Drafting\n\n**Step 1: Build the Outline**\n\nBefore writing prose, create the header skeleton:\n- H1 that includes the keyword and creates curiosity\n- 4-7 H2 sections in logical progression\n- H3s only when a section genuinely needs subdivision\n- Conclusion with CTA\n\n**Step 2: Write the Introduction**\n\nThe intro has one job: make the reader believe this piece answers their question.\n\nFormula:\n1. Name the problem or situation the reader is in (1 sentence)\n2. Name what this piece does about it (1 sentence)\n3. Establish credibility if relevant (1 sentence, optional)\n\nWhat to avoid:\n- \"In today's digital landscape...\" (everyone does this)\n- Starting with a question unless it is genuinely sharp\n- Three sentences of context before reaching the point\n\n**Step 3: Write Section by Section**\n\nFor each H2:\n1. State the main point in the first sentence\n2. Prove it with an example, statistic, or comparison\n3. Provide one actionable takeaway before moving to the next section\n4. Use transitional phrases to connect sections naturally\n\n**Step 4: Write the Conclusion**\n\nThree elements:\n1. Summary of core argument (1-2 sentences, not a repeat of the intro)\n2. The single most important next step\n3. CTA aligned with the content goal\n\n### Workflow 3: Optimization Pipeline\n\nRun these passes in order on every draft:\n\n**Pass 1: SEO Optimization**\n\n- [ ] Title tag: contains primary keyword, under 60 characters, curiosity-driving\n- [ ] H1: different from title tag, keyword-rich, reads naturally\n- [ ] H2s: at least 2-3 contain secondary keywords or related phrases\n- [ ] First paragraph: primary keyword appears in first 100 words\n- [ ] Keyword density: primary keyword appears naturally 3-5 times (not stuffed)\n- [ ] Image alt text: descriptive, includes keyword where natural\n- [ ] URL slug: short, keyword-first, no stop words\n- [ ] Internal links: 2-4 minimum, linking to and from related content\n- [ ] External links: 1-3 to authoritative sources\n\n**Pass 2: Readability**\n\n- [ ] Average sentence length: 15-20 words with variation\n- [ ] No paragraph exceeds 4 sentences\n- [ ] Active voice used in 80%+ of sentences\n- [ ] Jargon explained on first use for non-expert audiences\n- [ ] At least one visual element (image, table, diagram) per 500 words\n- [ ] Subheadings visible every 200-300 words\n- [ ] Readability score target: 60-70 (Flesch-Kincaid)\n\n**Pass 3: Structure Audit**\n\n- [ ] Intro delivers on the headline's promise\n- [ ] Every H2 earns its place (cut sections that add no value)\n- [ ] At least 2 concrete examples or illustrations\n- [ ] Conclusion feels earned, not padded\n- [ ] Content flow follows logical progression\n- [ ] No orphan sections that could be merged\n\n**Pass 4: Meta Content**\n\n- [ ] Meta description: 150-160 characters, includes keyword, ends with hook\n- [ ] OG title: optimized for social sharing (can differ from meta title)\n- [ ] OG description: optimized for social click-through\n- [ ] Canonical URL: set correctly\n- [ ] Schema markup: Article schema at minimum\n\n---\n\n## Editorial Calendar Management\n\n### Calendar Structure\n\n| Week | Monday | Wednesday | Friday |\n|------|--------|-----------|--------|\n| 1 | [Pillar topic A] | [Supporting topic B] | [Social repurpose] |\n| 2 | [Pillar topic C] | [Guest\u002Fcollab piece] | [Update old post] |\n| 3 | [Pillar topic A] | [Supporting topic D] | [Social repurpose] |\n| 4 | [Data\u002Fresearch piece] | [Supporting topic E] | [Roundup\u002Fcompilation] |\n\n### Content Types by Frequency\n\n| Type | Frequency | Purpose |\n|------|-----------|---------|\n| Pillar posts (2,000+ words) | 2x\u002Fmonth | Authority building, SEO ranking |\n| Supporting posts (800-1,500 words) | 2-4x\u002Fmonth | Topic cluster depth, internal linking |\n| Update\u002Frefresh existing posts | 2x\u002Fmonth | Maintain ranking, improve performance |\n| Data\u002Fresearch pieces | 1x\u002Fmonth | Backlink attraction, original insights |\n| Guest\u002Fcollaboration | 1x\u002Fmonth | Audience expansion, backlinks |\n\n### Production Timeline\n\n| Stage | Owner | Duration | Deadline Relative to Publish |\n|-------|-------|----------|---------------------------|\n| Brief creation | Strategist | 1 day | Publish - 14 days |\n| Research and outline | Writer | 2 days | Publish - 12 days |\n| First draft | Writer | 3 days | Publish - 9 days |\n| Editorial review | Editor | 2 days | Publish - 7 days |\n| Revisions | Writer | 1 day | Publish - 5 days |\n| SEO optimization | SEO lead | 1 day | Publish - 4 days |\n| Final review | Editor | 1 day | Publish - 3 days |\n| Staging and QA | Operations | 1 day | Publish - 2 days |\n| Publish | Operations | — | Publish day |\n\n---\n\n## Content Repurposing System\n\n### One Piece, Many Formats\n\nEvery pillar content piece should produce 5-8 derivative pieces:\n\n| Source | Derivative | Platform | Effort |\n|--------|-----------|----------|--------|\n| Blog post | Key insight thread | Twitter\u002FX | Low |\n| Blog post | Carousel of main points | LinkedIn | Medium |\n| Blog post | Short-form video summary | TikTok\u002FReels | Medium |\n| Blog post | Newsletter section | Email | Low |\n| Blog post | Slide deck | SlideShare\u002FLinkedIn | Medium |\n| Blog post | Podcast discussion topic | Podcast | Low |\n| Blog post | Infographic | Pinterest\u002FBlog | High |\n| Blog post | FAQ page content | Website | Low |\n\n### Repurposing Workflow\n\n1. **Publish the pillar piece** — Let it index and get initial traction\n2. **Extract 3-5 key insights** — Each insight becomes a standalone social piece\n3. **Adapt format per platform** — Not copy-paste; reformat for each platform's norms\n4. **Schedule distribution** — Spread across 1-2 weeks after publication\n5. **Cross-link everything** — Social pieces link back to the pillar content\n6. **Track performance** — Identify which derivative formats drive the most traffic back\n\n### Evergreen Refresh Cycle\n\nFor high-performing content:\n- Review quarterly for accuracy and relevance\n- Update statistics and data points annually\n- Refresh publish date after significant updates\n- Re-promote refreshed content through social and email\n- Add new internal links as related content is published\n\n---\n\n## Quality Gates\n\n### Pre-Publish Checklist\n\nEvery piece must pass these gates before publishing:\n\n**Content Quality:**\n- [ ] Core thesis is stated clearly in the first 200 words\n- [ ] Every factual claim has a source or is labeled as opinion\n- [ ] At least one image, table, or visual element\n- [ ] Introduction does not start with a cliche\n- [ ] Word count is within 10% of target\n- [ ] No AI-sounding patterns (run Content Humanizer audit if uncertain)\n\n**SEO Quality:**\n- [ ] Primary keyword in title, H1, first 100 words, and 2+ H2s\n- [ ] Meta title under 60 characters with keyword\n- [ ] Meta description 150-160 characters with keyword and hook\n- [ ] All images have descriptive alt text\n- [ ] 2-4 internal links present and functional\n- [ ] URL slug is clean and keyword-first\n\n**Technical Quality:**\n- [ ] All links verified and functional\n- [ ] Images optimized for web (compressed, appropriate dimensions)\n- [ ] Mobile rendering verified\n- [ ] Schema markup implemented\n- [ ] Canonical URL set\n- [ ] OG tags configured for social sharing\n\n**Editorial Quality:**\n- [ ] Spelling and grammar checked\n- [ ] Consistent formatting throughout\n- [ ] Heading hierarchy maintained (H1 > H2 > H3, no skips)\n- [ ] Consistent voice and tone from start to finish\n- [ ] CTA present and aligned with content goal\n\n---\n\n## Best Practices\n\n1. **Brief first, always** — Never start writing without a brief. Even a 5-minute brief prevents 2 hours of rewriting.\n\n2. **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.\n\n3. **Front-load value** — The reader should get something useful in the first 300 words. Do not make them scroll to find the point.\n\n4. **Optimize existing before creating new** — Refreshing a post ranked #8 to #3 produces more traffic than a new post starting at #50.\n\n5. **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.\n\n6. **Kill your darlings** — If a section does not serve the reader or the keyword strategy, cut it. Length without value hurts ranking.\n\n7. **Batch production** — Write briefs for 4-6 pieces at once, then draft in batches. Context-switching between briefing and writing reduces quality.\n\n8. **Measure what matters** — Track organic traffic, time on page, and conversion rate. Vanity metrics (word count, publishing frequency alone) are misleading.\n\n9. **Repurpose systematically** — Every pillar piece should produce 5+ derivative pieces. Build repurposing into the production workflow, not as an afterthought.\n\n10. **Maintain a content debt backlog** — Track content that needs updating, broken links, outdated statistics, and missing internal links. Address content debt regularly.\n\n---\n\n## Integration Points\n\n- **Content Strategy** — Use for deciding what to write (topics, calendar, pillar structure). Content Production handles the execution.\n- **Content Humanizer** — Use after drafting when the piece sounds robotic. Run before the SEO optimization pass.\n- **AI SEO** — Use for optimizing specifically for AI search citation in addition to traditional SEO.\n- **Copywriting** — Use for landing pages, CTAs, and conversion copy. Content Production handles long-form content.\n- **SEO Specialist** — Use for technical SEO audits across the content library. Content Production handles per-piece optimization.\n- **Social Content** — Use for distributing and repurposing content across social platforms.\n- **Copy Editing** — Use for the editorial review pass within the production pipeline.\n\n---\n\n## Troubleshooting\n\n| Problem | Likely Cause | Fix |\n|---------|-------------|-----|\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n\n---\n\n## Success Criteria\n\n- **Production velocity**: Maintaining planned cadence (2-4 pieces\u002Fweek) with less than 10% schedule slippage\n- **Quality gate pass rate**: 90%+ of drafts passing the pre-publish quality gate checklist on first or second review\n- **SEO optimization score**: Average score of 75+ on the four-pass optimization pipeline (SEO, readability, structure, meta)\n- **Readability score**: Flesch Reading Ease of 60-70 across all published content (appropriate for web audiences)\n- **Internal link coverage**: Every new piece includes 3-5 internal links, and 3+ existing pieces updated to link back\n- **Repurposing multiplier**: Each pillar piece produces 5+ derivative pieces across social, email, and other channels\n- **Content performance**: 60%+ of content published in last 6 months generating organic impressions within 90 days\n\n---\n\n## Scope & Limitations\n\n**In scope:**\n- Full content production pipeline from brief to publish\n- Competitive research and source gathering for content briefs\n- Drafting methodology (outline-first, section-by-section)\n- Four-pass optimization pipeline (SEO, readability, structure, meta)\n- Editorial calendar management and production timelines\n- Content repurposing system across channels\n- Quality gates and pre-publish checklists\n\n**Out of scope:**\n- Content strategy and topic selection (use Content Strategy)\n- AI content humanization (use Content Humanizer)\n- Detailed copy editing (use Copy Editing)\n- Technical SEO audits (use SEO Specialist)\n- Social media platform management (use Social Content)\n- Design and visual content creation\n\n**Known limitations:**\n- 60% of marketing teams now use AI in content workflows (2026 data) — quality control processes must account for AI-assisted drafting\n- Production timelines assume dedicated writer and editor roles; solo operators need adjusted timelines\n- Content performance measurement requires Google Search Console and analytics access\n- Repurposing effectiveness varies by platform — not all derivative formats will perform equally\n\n---\n\n## Scripts\n\n```bash\n# Score content readability with detailed metrics\npython scripts\u002Freadability_scorer.py article.md --json\n\n# Generate a content brief from keyword research\npython scripts\u002Fcontent_brief_generator.py --keyword \"cloud cost optimization\" --json\n\n# Analyze headline options for a new piece\npython scripts\u002Fheadline_analyzer.py --headlines headlines.txt --json\n```\n",{"name":5,"license":14,"metadata":62,"description":66},{"author":63,"domain":37,"updated":64,"version":65,"category":53},"borghei",1773014400000,"1.0.0","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.\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-03-claude-skills-main-marketing-content-production-skill-9f4b6c66","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill content-production",{"tool":79,"command":80},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill content-production",{"tool":82,"command":83},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill content-production","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-03-claude-skills-main-marketing-content-production-skill-9f4b6c66\u002FSKILL.md",true,[],[88,113,140,170,198,226],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":57},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[90,95,96,97,98,99,100,101,102,103,104,105,106,107,51,108,109,110,111,112],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","unrelated","app","scope","for","webmcp",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":117,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":57},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,43,139],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","copilot instructions",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":152,"publishedAt":57},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[146,149],{"categoryNo":147,"categoryName":148,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":150,"categoryName":151,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[153,154,155,156,157,158,159,160,55,161,162,163,164,107,165,166,167,168,111,169],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"publishedAt":57},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[180,181,182,183,184,185,186,187,188,107,189,190,191,192,193,194,195,196,197,111],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":209,"publishedAt":57},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[204,205,206],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":34,"categoryName":35,"taxonomyType":31,"taxonomyTypeDesc":32},{"categoryNo":207,"categoryName":208,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000038","人力资源",[210,211,212,213,41,214,215,216,122,217,107,218,219,220,221,222,223,224,111,225],"search","Job Search","technical job search","technical","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":232,"publishedAt":57},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[233,234,235,236,237,213,238,107,222,239,240,241,242,243,244,245,246,247,111,248],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]