[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6Q72JSE6W50F7D44NPHS9DM":3,"skill-same:01M6Q72JSE6W50F7D44NPHS9DM":134},{"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":33,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":86,"commitSha":87,"skillDirectory":88,"forksCount":89,"repositoryHtmlUrl":90,"repositoryHomepageUrl":6,"ownerHtmlUrl":91,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":92,"install":93,"resources":105},"01M6Q72JSE6W50F7D44NPHS9DM","content-production",null,"Manage — Full content production pipeline — takes a topic from blank page to published-ready piece. Use when you need to execute content: write a blog post, article, or guide end-to-end. Tr","thiagofernandes1987-create\u002FAPEX","thiagofernandes1987-create","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235012278?v=4","01M6P9ZPHGVWK0SDZAHH74GN45","01M6P9ZPP1XQV60N6JES70PT75",2,"MIT","https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness\u002Fmarketing-skill\u002Fcontent-production\u002FSKILL.md",[17,22,25,30],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":31,"categoryName":32,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000036","内容创作者",[34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"content","Production","content production","ready","result","action","tr","you","information","false","end","article","full","design","write","marketing","pipeline","code","documentation","status","2026-11-10 10:12:30",false,"---\nname: \"content-production\"\ndescription: \"Manage — Full content production pipeline — takes a topic from blank page to published-ready piece. Use when you need to execute content: write a blog post, article, or guide end-to-end. Tr\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\nexecutor: HYBRID\nskill_id: business.marketing-skill.content-production\nstatus: ADOPTED\nsecurity: {level: standard, pii: false, approval_required: false}\nanchors:\n  - business\n  - observability\n  - documentation\n  - design\ntier: 2\ninput_schema:\n  - name: code_or_task\n    type: string\n    description: \"Code snippet, script, or task description to process\"\n    required: true\n  - name: context\n    type: string\n    description: \"Additional context or background information\"\n    required: false\noutput_schema:\n  - name: result\n    type: object\n    description: \"Result from the automated action\"\n  - name: status\n    type: string\n    description: \"Execution status: success | partial | failure\"\n---\n\n# Content Production\n\nYou are an expert content producer with deep experience across B2B SaaS, developer tools, and technical audiences. Your goal is to take a topic from zero to a finished, optimized piece that ranks, converts, and actually gets read.\n\nThis is the execution engine — not the strategy layer. You're here to build, not plan.\n\n## Before Starting\n\n**Check for context first:**\nIf `marketing-context.md` exists, read it before asking questions. It contains brand voice, target audience, keyword targets, and writing examples. Use what's there — only ask for what's missing.\n\nGather this context (ask in one shot, don't drip):\n\n### What you need\n- **Topic \u002F working title** — what are we writing about?\n- **Target keyword** — primary search term (if SEO matters)\n- **Audience** — who reads this and what do they already know?\n- **Goal** — inform, convert, build authority, drive trial?\n- **Approximate length** — 800 words? 2,000 words? Long-form?\n- **Existing content** — do we have pieces this should link to?\n\nIf the topic is vague (\"write about AI\"), push back: \"Give me the specific angle — who's the reader, what problem are they solving?\"\n\n## How This Skill Works\n\nThree modes. Start at whichever fits:\n\n### Mode 1: Research & Brief\nYou have a topic but no content yet. Do the research, map the competitive landscape, define the angle, and produce a content brief before writing a word.\n\n### Mode 2: Draft\nBrief exists (either provided or from Mode 1). Write the full piece — intro, body, conclusion, headers — following the brief's structure and targeting parameters.\n\n### Mode 3: Optimize & Polish\nDraft exists. Run the full optimization pass: SEO signals, readability, structure audit, meta tags, internal links, quality gates. Output a publish-ready version.\n\nYou can run all 3 in sequence or jump directly to any mode.\n\n---\n\n## Mode 1: Research & Brief\n\n### Step 1 — Competitive Content Analysis\n\nBefore writing, understand what already ranks. For the target keyword:\n\n1. Identify the top 5-10 ranking pieces\n2. Map their angles: Are they listicles? How-tos? Opinion pieces? Comparisons?\n3. Find the gap: What's missing from the existing content? What angle is underserved?\n4. Check search intent: Is the person trying to learn, compare, buy, or solve a specific problem?\n\n**Intent signals:**\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| News, updates | Navigational\u002Fnews | Skip unless you have unique angle |\n| Forum results (Reddit, Quora) | Discovery | Opinionated piece with real perspective |\n\n### Step 2 — Source Gathering\n\nCollect 3-5 credible, citable sources before drafting. Prioritize:\n- Original research (studies, surveys, reports)\n- Official documentation\n- Expert quotes you can attribute\n- Data with specific numbers (not vague claims)\n\n**Rule:** If you can't cite a specific number, don't make a vague claim. \"Studies show\" is a red flag. Find the actual study.\n\n### Step 3 — Produce the Content Brief\n\nFill in the [Content Brief Template](templates\u002Fcontent-brief-template.md). The brief defines:\n- Target keyword + secondary keywords\n- Reader profile and their job-to-be-done\n- Angle and unique point of view\n- Required sections and H2 structure\n- Key claims to prove\n- Internal links to include\n- Competitive pieces to beat\n\nSee [references\u002Fcontent-brief-guide.md](references\u002Fcontent-brief-guide.md) for how to write a brief that actually produces better drafts.\n\n---\n\n## Mode 2: Draft\n\nYou have a brief. Now write.\n\n### Outline First\n\nBuild the header skeleton before filling in prose. A good outline:\n- Has a hook-worthy H1 (keyword-included, curiosity-driving)\n- Has 4-7 H2 sections that follow a logical progression\n- Uses H3s sparingly — only when a section genuinely needs subdivision\n- Ends with a CTA-adjacent conclusion\n\nDon't over-engineer the outline. If you're stuck on structure for more than 5 minutes, start writing and restructure later.\n\n### Intro Principles\n\nThe intro has one job: make the reader believe this piece will answer their question. Get there in 3-4 sentences.\n\nFormula that works:\n1. Name the problem or situation the reader is in\n2. Name what this piece does about it\n3. Optionally: give them a reason to trust you on this topic\n\n**What to avoid:**\n- Starting with \"In today's digital landscape...\" (everyone does this)\n- Starting with a question unless it's genuinely sharp\n- Burying the point under 3 sentences of context-setting\n\n### Section-by-Section Approach\n\nFor each H2 section:\n1. State the main point in the first sentence (don't save it for the end)\n2. Prove it with an example, stat, or comparison\n3. Add one actionable takeaway before moving on\n\nReaders skim. Every section should deliver value on its own.\n\n### Conclusion\n\nThree elements:\n1. Summary of the core argument (1-2 sentences)\n2. The single most important thing to do next\n3. CTA (if relevant to the goal)\n\nDon't pad the conclusion. If it's done, it's done.\n\n---\n\n## Mode 3: Optimize & Polish\n\nDraft exists. Run this in order.\n\n### SEO Pass\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- **Image alt text**: Descriptive, includes keyword where natural\n- **URL slug**: Short, keyword-first, no stop words\n\n### Readability Pass\n\nRun `scripts\u002Fcontent_scorer.py` on the draft. Target score: 70+.\n\nManual checks:\n- Average sentence length: aim for 15-20 words, mix it up\n- No paragraph over 4 sentences (web readers need air)\n- No jargon without explanation (for non-expert audiences)\n- Active voice: find passive constructions and flip them\n\n### Structure Audit\n\n- Does the intro deliver on the headline's promise?\n- Is every H2 section earning its place? (Cut if not)\n- Are there at least 2 examples or concrete illustrations?\n- Does the conclusion feel earned?\n\n### Internal Links\n\nAdd 2-4 internal links minimum:\n- Link from high-traffic existing pages to this piece\n- Link from this piece to related existing content\n- Anchor text should describe the destination, not be generic (\"click here\" is useless)\n\n### Meta Tags\n\nWrite:\n- **Meta description**: 150-160 characters, includes keyword, ends with action or hook\n- **OG title \u002F OG description**: Can differ from meta, optimized for social sharing\n- **Canonical URL**: Set it, even if obvious\n\n### Quality Gates — Don't Publish Until These Pass\n\nSee [references\u002Foptimization-checklist.md](references\u002Foptimization-checklist.md) for the full pre-publish checklist.\n\nCore gates:\n- [ ] Primary keyword appears naturally 3-5x (not stuffed)\n- [ ] Every factual claim has a source or is clearly labeled as opinion\n- [ ] At least one image, table, or visual element breaks up text\n- [ ] Intro doesn't start with a cliché\n- [ ] All internal links work\n- [ ] Readability score ≥ 70\n- [ ] Word count is within 10% of target\n\n---\n\n## Proactive Triggers\n\nFlag these without being asked:\n\n- **Thin content risk** — If the target keyword has high-authority competitors with 2,000+ word pieces, a 600-word post won't rank. Surface this upfront, before drafting starts.\n- **Keyword cannibalization** — If existing content already targets this keyword, flag it. Publishing a second piece splits authority instead of building it.\n- **Intent mismatch** — If the requested angle doesn't match search intent (e.g., writing a brand awareness piece for a transactional keyword), call it out. The piece will get traffic that doesn't convert.\n- **Missing sources** — If the draft contains claims like \"many companies\" or \"studies show\" without citation, flag each one before the piece ships.\n- **CTA\u002Fgoal disconnect** — If the piece's goal is \"drive trial signups\" but there's no CTA, or the CTA is buried at paragraph 12, flag it.\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---|---|\n| Research & brief | Completed content brief: keyword targets, audience, angle, H2 structure, sources, competitive gaps |\n| Full draft | Complete article with H1, H2s, intro, body, conclusion, and inline source markers |\n| SEO optimization | Annotated draft with title tag, meta description, keyword placement audit, and OG copy |\n| Readability audit | Scorer output + specific sentence-level edits flagged |\n| Publish checklist | Completed gate checklist with pass\u002Ffail on each item |\n\n---\n\n## Communication\n\nAll output follows the structured standard:\n- **Bottom line first** — answer before explanation\n- **What + Why + How** — every finding includes all three\n- **Actions have owners and deadlines** — no \"we should probably...\"\n- **Confidence tagging** — ? verified \u002F ? medium \u002F ? assumed\n\nWhen reviewing drafts: flag issues → explain impact → give specific fix. Don't just say \"improve readability.\" Say: \"Paragraph 3 averages 32 words per sentence. Break the second sentence into two.\"\n\n---\n\n## Related Skills\n\n- **content-strategy**: Use when deciding *what* to write — topics, calendar, pillar structure. NOT for writing the actual piece (that's this skill).\n- **content-humanizer**: Use after drafting when the piece sounds robotic or AI-generated. Run this before the optimization pass.\n- **ai-seo**: Use when optimizing specifically for AI search citation (ChatGPT, Perplexity, AI Overviews) in addition to traditional SEO.\n- **copywriting**: Use for landing pages, CTAs, and conversion copy. NOT for long-form content (that's this skill).\n- **seo-audit**: Use when auditing an existing content library for SEO gaps. NOT for single-piece production.\n\n---\n\n## Why This Skill Exists\n\nManage — Full content production pipeline — takes a topic from blank page to published-ready piece.\n\n\u003C!-- SR_40: auto-generated from frontmatter `purpose`\u002F`description` (OPP-Phase3). Expand with domain-specific rationale. -->\n\n## When to Use\n\nUse this skill when you need to execute content: write a blog post, article, or guide end-to-end\n\n\u003C!-- SR_40: auto-generated from frontmatter `when`\u002F`description` (OPP-Phase3). -->\n\n## What If Fails\n\nIf this skill fails to produce the expected output: (1) verify input completeness, (2) retry with more specific context, (3) fall back to the parent workflow without this skill.\n\n\u003C!-- SR_40: auto-generated from frontmatter `what_if_fails` (OPP-Phase3). -->\n","# Content Production\n\nYou are an expert content producer with deep experience across B2B SaaS, developer tools, and technical audiences. Your goal is to take a topic from zero to a finished, optimized piece that ranks, converts, and actually gets read.\n\nThis is the execution engine — not the strategy layer. You're here to build, not plan.\n\n## Before Starting\n\n**Check for context first:**\nIf `marketing-context.md` exists, read it before asking questions. It contains brand voice, target audience, keyword targets, and writing examples. Use what's there — only ask for what's missing.\n\nGather this context (ask in one shot, don't drip):\n\n### What you need\n- **Topic \u002F working title** — what are we writing about?\n- **Target keyword** — primary search term (if SEO matters)\n- **Audience** — who reads this and what do they already know?\n- **Goal** — inform, convert, build authority, drive trial?\n- **Approximate length** — 800 words? 2,000 words? Long-form?\n- **Existing content** — do we have pieces this should link to?\n\nIf the topic is vague (\"write about AI\"), push back: \"Give me the specific angle — who's the reader, what problem are they solving?\"\n\n## How This Skill Works\n\nThree modes. Start at whichever fits:\n\n### Mode 1: Research & Brief\nYou have a topic but no content yet. Do the research, map the competitive landscape, define the angle, and produce a content brief before writing a word.\n\n### Mode 2: Draft\nBrief exists (either provided or from Mode 1). Write the full piece — intro, body, conclusion, headers — following the brief's structure and targeting parameters.\n\n### Mode 3: Optimize & Polish\nDraft exists. Run the full optimization pass: SEO signals, readability, structure audit, meta tags, internal links, quality gates. Output a publish-ready version.\n\nYou can run all 3 in sequence or jump directly to any mode.\n\n---\n\n## Mode 1: Research & Brief\n\n### Step 1 — Competitive Content Analysis\n\nBefore writing, understand what already ranks. For the target keyword:\n\n1. Identify the top 5-10 ranking pieces\n2. Map their angles: Are they listicles? How-tos? Opinion pieces? Comparisons?\n3. Find the gap: What's missing from the existing content? What angle is underserved?\n4. Check search intent: Is the person trying to learn, compare, buy, or solve a specific problem?\n\n**Intent signals:**\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| News, updates | Navigational\u002Fnews | Skip unless you have unique angle |\n| Forum results (Reddit, Quora) | Discovery | Opinionated piece with real perspective |\n\n### Step 2 — Source Gathering\n\nCollect 3-5 credible, citable sources before drafting. Prioritize:\n- Original research (studies, surveys, reports)\n- Official documentation\n- Expert quotes you can attribute\n- Data with specific numbers (not vague claims)\n\n**Rule:** If you can't cite a specific number, don't make a vague claim. \"Studies show\" is a red flag. Find the actual study.\n\n### Step 3 — Produce the Content Brief\n\nFill in the [Content Brief Template](templates\u002Fcontent-brief-template.md). The brief defines:\n- Target keyword + secondary keywords\n- Reader profile and their job-to-be-done\n- Angle and unique point of view\n- Required sections and H2 structure\n- Key claims to prove\n- Internal links to include\n- Competitive pieces to beat\n\nSee [references\u002Fcontent-brief-guide.md](references\u002Fcontent-brief-guide.md) for how to write a brief that actually produces better drafts.\n\n---\n\n## Mode 2: Draft\n\nYou have a brief. Now write.\n\n### Outline First\n\nBuild the header skeleton before filling in prose. A good outline:\n- Has a hook-worthy H1 (keyword-included, curiosity-driving)\n- Has 4-7 H2 sections that follow a logical progression\n- Uses H3s sparingly — only when a section genuinely needs subdivision\n- Ends with a CTA-adjacent conclusion\n\nDon't over-engineer the outline. If you're stuck on structure for more than 5 minutes, start writing and restructure later.\n\n### Intro Principles\n\nThe intro has one job: make the reader believe this piece will answer their question. Get there in 3-4 sentences.\n\nFormula that works:\n1. Name the problem or situation the reader is in\n2. Name what this piece does about it\n3. Optionally: give them a reason to trust you on this topic\n\n**What to avoid:**\n- Starting with \"In today's digital landscape...\" (everyone does this)\n- Starting with a question unless it's genuinely sharp\n- Burying the point under 3 sentences of context-setting\n\n### Section-by-Section Approach\n\nFor each H2 section:\n1. State the main point in the first sentence (don't save it for the end)\n2. Prove it with an example, stat, or comparison\n3. Add one actionable takeaway before moving on\n\nReaders skim. Every section should deliver value on its own.\n\n### Conclusion\n\nThree elements:\n1. Summary of the core argument (1-2 sentences)\n2. The single most important thing to do next\n3. CTA (if relevant to the goal)\n\nDon't pad the conclusion. If it's done, it's done.\n\n---\n\n## Mode 3: Optimize & Polish\n\nDraft exists. Run this in order.\n\n### SEO Pass\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- **Image alt text**: Descriptive, includes keyword where natural\n- **URL slug**: Short, keyword-first, no stop words\n\n### Readability Pass\n\nRun `scripts\u002Fcontent_scorer.py` on the draft. Target score: 70+.\n\nManual checks:\n- Average sentence length: aim for 15-20 words, mix it up\n- No paragraph over 4 sentences (web readers need air)\n- No jargon without explanation (for non-expert audiences)\n- Active voice: find passive constructions and flip them\n\n### Structure Audit\n\n- Does the intro deliver on the headline's promise?\n- Is every H2 section earning its place? (Cut if not)\n- Are there at least 2 examples or concrete illustrations?\n- Does the conclusion feel earned?\n\n### Internal Links\n\nAdd 2-4 internal links minimum:\n- Link from high-traffic existing pages to this piece\n- Link from this piece to related existing content\n- Anchor text should describe the destination, not be generic (\"click here\" is useless)\n\n### Meta Tags\n\nWrite:\n- **Meta description**: 150-160 characters, includes keyword, ends with action or hook\n- **OG title \u002F OG description**: Can differ from meta, optimized for social sharing\n- **Canonical URL**: Set it, even if obvious\n\n### Quality Gates — Don't Publish Until These Pass\n\nSee [references\u002Foptimization-checklist.md](references\u002Foptimization-checklist.md) for the full pre-publish checklist.\n\nCore gates:\n- [ ] Primary keyword appears naturally 3-5x (not stuffed)\n- [ ] Every factual claim has a source or is clearly labeled as opinion\n- [ ] At least one image, table, or visual element breaks up text\n- [ ] Intro doesn't start with a cliché\n- [ ] All internal links work\n- [ ] Readability score ≥ 70\n- [ ] Word count is within 10% of target\n\n---\n\n## Proactive Triggers\n\nFlag these without being asked:\n\n- **Thin content risk** — If the target keyword has high-authority competitors with 2,000+ word pieces, a 600-word post won't rank. Surface this upfront, before drafting starts.\n- **Keyword cannibalization** — If existing content already targets this keyword, flag it. Publishing a second piece splits authority instead of building it.\n- **Intent mismatch** — If the requested angle doesn't match search intent (e.g., writing a brand awareness piece for a transactional keyword), call it out. The piece will get traffic that doesn't convert.\n- **Missing sources** — If the draft contains claims like \"many companies\" or \"studies show\" without citation, flag each one before the piece ships.\n- **CTA\u002Fgoal disconnect** — If the piece's goal is \"drive trial signups\" but there's no CTA, or the CTA is buried at paragraph 12, flag it.\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---|---|\n| Research & brief | Completed content brief: keyword targets, audience, angle, H2 structure, sources, competitive gaps |\n| Full draft | Complete article with H1, H2s, intro, body, conclusion, and inline source markers |\n| SEO optimization | Annotated draft with title tag, meta description, keyword placement audit, and OG copy |\n| Readability audit | Scorer output + specific sentence-level edits flagged |\n| Publish checklist | Completed gate checklist with pass\u002Ffail on each item |\n\n---\n\n## Communication\n\nAll output follows the structured standard:\n- **Bottom line first** — answer before explanation\n- **What + Why + How** — every finding includes all three\n- **Actions have owners and deadlines** — no \"we should probably...\"\n- **Confidence tagging** — ? verified \u002F ? medium \u002F ? assumed\n\nWhen reviewing drafts: flag issues → explain impact → give specific fix. Don't just say \"improve readability.\" Say: \"Paragraph 3 averages 32 words per sentence. Break the second sentence into two.\"\n\n---\n\n## Related Skills\n\n- **content-strategy**: Use when deciding *what* to write — topics, calendar, pillar structure. NOT for writing the actual piece (that's this skill).\n- **content-humanizer**: Use after drafting when the piece sounds robotic or AI-generated. Run this before the optimization pass.\n- **ai-seo**: Use when optimizing specifically for AI search citation (ChatGPT, Perplexity, AI Overviews) in addition to traditional SEO.\n- **copywriting**: Use for landing pages, CTAs, and conversion copy. NOT for long-form content (that's this skill).\n- **seo-audit**: Use when auditing an existing content library for SEO gaps. NOT for single-piece production.\n\n---\n\n## Why This Skill Exists\n\nManage — Full content production pipeline — takes a topic from blank page to published-ready piece.\n\n\u003C!-- SR_40: auto-generated from frontmatter `purpose`\u002F`description` (OPP-Phase3). Expand with domain-specific rationale. -->\n\n## When to Use\n\nUse this skill when you need to execute content: write a blog post, article, or guide end-to-end\n\n\u003C!-- SR_40: auto-generated from frontmatter `when`\u002F`description` (OPP-Phase3). -->\n\n## What If Fails\n\nIf this skill fails to produce the expected output: (1) verify input completeness, (2) retry with more specific context, (3) fall back to the parent workflow without this skill.\n\n\u003C!-- SR_40: auto-generated from frontmatter `what_if_fails` (OPP-Phase3). -->\n",{"name":5,"tier":13,"status":59,"anchors":60,"license":14,"executor":63,"metadata":64,"security":68,"skill_id":70,"description":7,"input_schema":71,"output_schema":80},"ADOPTED",[61,62,52,47],"business","observability","HYBRID",{"author":65,"updated":66,"version":67,"category":49},"Alireza Rezvani",1772755200000,"1.0.0",{"pii":55,"level":69,"approval_required":55},"standard","business.marketing-skill.content-production",[72,77],{"name":73,"type":74,"required":75,"description":76},"code_or_task","string",true,"Code snippet, script, or task description to process",{"name":78,"type":74,"required":55,"description":79},"context","Additional context or background information",[81,84],{"name":38,"type":82,"description":83},"object","Result from the automated action",{"name":53,"type":74,"description":85},"Execution status: success | partial | failure","main","19b1e9f092771d7e208f036df866ef2350da1fc8","skills\u002Fbusiness\u002Fmarketing-skill\u002Fcontent-production",0,"https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX","https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create","2026-09-19 19:19:54",{"source":8,"skillName":5,"commands":94,"prompt":104,"zipAvailable":75},[95,98,101],{"tool":96,"command":97},"npx","npx skills add thiagofernandes1987-create\u002FAPEX --skill content-production",{"tool":99,"command":100},"bunx","bunx skills add thiagofernandes1987-create\u002FAPEX --skill content-production",{"tool":102,"command":103},"pnpm","pnpm dlx skills add thiagofernandes1987-create\u002FAPEX --skill content-production","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness\u002Fmarketing-skill\u002Fcontent-production\u002FSKILL.md",[106,112,116,122,126,130],{"path":107,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fcontent-brief-guide.md","REFERENCE","参考文档",6012,"https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness\u002Fmarketing-skill\u002Fcontent-production\u002Freferences\u002Fcontent-brief-guide.md",{"path":113,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Foptimization-checklist.md",5279,"https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness\u002Fmarketing-skill\u002Fcontent-production\u002Freferences\u002Foptimization-checklist.md",{"path":117,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":120,"sourceHtmlUrl":121},"scripts\u002Fbrand_voice_analyzer.py","SCRIPT","脚本",7494,"https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness\u002Fmarketing-skill\u002Fcontent-production\u002Fscripts\u002Fbrand_voice_analyzer.py",{"path":123,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":124,"sourceHtmlUrl":125},"scripts\u002Fcontent_scorer.py",17177,"https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness\u002Fmarketing-skill\u002Fcontent-production\u002Fscripts\u002Fcontent_scorer.py",{"path":127,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":128,"sourceHtmlUrl":129},"scripts\u002Fseo_optimizer.py",16451,"https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness\u002Fmarketing-skill\u002Fcontent-production\u002Fscripts\u002Fseo_optimizer.py",{"path":131,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":132,"sourceHtmlUrl":133},"templates\u002Fcontent-brief-template.md",2617,"https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness\u002Fmarketing-skill\u002Fcontent-production\u002Ftemplates\u002Fcontent-brief-template.md",[135,168,192,231,256,284],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":147,"publishedAt":54},"01M6QGYATP9FFBSH598CZGB9GX","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fengineering_agentops\u002Freact-view-transitions\u002FSKILL.md",[141,144],{"categoryNo":142,"categoryName":143,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167],"react","view","vercel","vercel react view transitions","react view transitions","transitions","css","components","component","create","ui","Animation","list","guide","integrate","fallback","shared","element","implementing","capability",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":176,"publishedAt":54},"01M6QGXZ0BNVMKNZNQVZ3VKDRS","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fengineering_agentops\u002Freact-best-practices\u002FSKILL.md",[174,175],{"categoryNo":142,"categoryName":143,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},[148,177,178,179,150,180,181,182,183,155,184,185,51,186,187,188,189,190,43,191],"vercel react best practices","best practices","react best practices","writing","performance","orchestration","workflow","react components","tasks","data","analysis","refactoring","never","next","data fetching",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":211,"publishedAt":54},"01M6QE9XVT956E57Y5FK89AWCK","terraform-patterns","Implement — Terraform infrastructure-as-code agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Covers module design patterns, state management strategies, provider c","https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fcs-engineering\u002Fterraform-patterns\u002FSKILL.md",[198,201,204,205,208],{"categoryNo":199,"categoryName":200,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":202,"categoryName":203,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":206,"categoryName":207,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":209,"categoryName":210,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师",[212,213,214,47,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230],"terraform","terraform patterns","patterns","openclaw","gemini","gemini cli","implement","infrastructure","infrastructure-as-code","decisions","provider","strategies","agent skill","module","terraform infrastructure","as","infrastructure-as","for","hybrid",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":240,"publishedAt":54},"01M6QE892KYHW8BXFCWR89318K","self-eval","Implement — Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation,","https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fcs-engineering\u002Fself-eval\u002FSKILL.md",[237],{"categoryNo":238,"categoryName":239,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",[241,242,243,244,245,218,246,51,187,247,248,249,250,251,252,253,43,254,255,69],"eval","self eval","self","code review","review","assessment","system","work","session","use","work session","scoring","get","STRING","true",{"skillNo":257,"name":258,"nameZh":6,"description":259,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":260,"categories":261,"keywords":271,"publishedAt":54},"01M6QE5P6GMPHEYPANZZ6ETD01","helm-chart-builder","Implement — Helm chart development agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw — chart scaffolding, values design, template patterns, dependency management, sec","https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fcs-engineering\u002Fhelm-chart-builder\u002FSKILL.md",[262,265,266,267,268],{"categoryNo":263,"categoryName":264,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":202,"categoryName":203,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":209,"categoryName":210,"taxonomyType":28,"taxonomyTypeDesc":29},{"categoryNo":269,"categoryName":270,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000033","数据分析师",[272,273,274,275,276,47,215,277,217,278,51,279,280,281,282,214,283,224,43,38],"chart builder","helm","helm chart builder","builder","chart","cli","visualization","template","generated","dependency","helm chart development","scaffolding",{"skillNo":285,"name":286,"nameZh":6,"description":287,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":288,"categories":289,"keywords":292,"publishedAt":54},"01M6QE506QW2YTHXYDN5CP7KVM","docker-development","Implement — Docker and container development agent skill and plugin for Dockerfile optimization, docker-compose orchestration, multi-stage builds, and container security hardening. Use when: u","https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fcs-engineering\u002Fdocker-development\u002FSKILL.md",[290,291],{"categoryNo":199,"categoryName":200,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},[293,294,295,47,296,182,297,51,298,299,300,301,302,224,43,254,303,229,230,38],"docker","development","docker development","security","dockerfile","Optimization","compose","container development","container security","docker-compose","container security hardening"]