[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6Q737DF0HD23SEMC38EW1P3":3,"skill-same:01M6Q737DF0HD23SEMC38EW1P3":113},{"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":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":81,"commitSha":82,"skillDirectory":83,"forksCount":84,"repositoryHtmlUrl":85,"repositoryHomepageUrl":6,"ownerHtmlUrl":86,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":87,"install":88,"resources":100},"01M6Q737DF0HD23SEMC38EW1P3","email-sequence",null,"Manage — When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions 'email sequence,' 'dri","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\u002Femail-sequence\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"email","sequence","email sequence","manage","result","hybrid","action","information","drip campaign","STRING","false","optimize","status","campaign","context","marketing","lifecycle","flow","code","create","2026-11-10 10:12:30",false,"---\nname: \"email-sequence\"\ndescription: \"Manage — When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions 'email sequence,' 'dri\"\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.email-sequence\nstatus: ADOPTED\nsecurity: {level: standard, pii: true, approval_required: false}\nanchors:\n  - business\n  - marketing\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# Email Sequence Design\n\nYou are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore creating a sequence, understand:\n\n1. **Sequence Type**\n   - Welcome\u002Fonboarding sequence\n   - Lead nurture sequence\n   - Re-engagement sequence\n   - Post-purchase sequence\n   - Event-based sequence\n   - Educational sequence\n   - Sales sequence\n\n2. **Audience Context**\n   - Who are they?\n   - What triggered them into this sequence?\n   - What do they already know\u002Fbelieve?\n   - What's their current relationship with you?\n\n3. **Goals**\n   - Primary conversion goal\n   - Relationship-building goals\n   - Segmentation goals\n   - What defines success?\n\n---\n\n## Core Principles\n→ See references\u002Femail-sequence-playbook.md for details\n\n## Output Format\n\n### Sequence Overview\n```\nSequence Name: [Name]\nTrigger: [What starts the sequence]\nGoal: [Primary conversion goal]\nLength: [Number of emails]\nTiming: [Delay between emails]\nExit Conditions: [When they leave the sequence]\n```\n\n### For Each Email\n```\nEmail [#]: [Name\u002FPurpose]\nSend: [Timing]\nSubject: [Subject line]\nPreview: [Preview text]\nBody: [Full copy]\nCTA: [Button text] → [Link destination]\nSegment\u002FConditions: [If applicable]\n```\n\n### Metrics Plan\nWhat to measure and benchmarks\n\n---\n\n## Task-Specific Questions\n\n1. What triggers entry to this sequence?\n2. What's the primary goal\u002Fconversion action?\n3. What do they already know about you?\n4. What other emails are they receiving?\n5. What's your current email performance?\n\n---\n\n## Tool Integrations\n\nFor implementation, see the [tools registry](..\u002F..\u002Ftools\u002FREGISTRY.md). Key email tools:\n\n| Tool | Best For | MCP | Guide |\n|------|----------|:---:|-------|\n| **Customer.io** | Behavior-based automation | - | [customer-io.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fcustomer-io.md) |\n| **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fmailchimp.md) |\n| **Resend** | Developer-friendly transactional | ✓ | [resend.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fresend.md) |\n| **SendGrid** | Transactional email at scale | - | [sendgrid.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fsendgrid.md) |\n| **Kit** | Creator\u002Fnewsletter focused | - | [kit.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fkit.md) |\n\n---\n\n## Related Skills\n\n- **cold-email** — WHEN the sequence targets people who have NOT opted in (outbound prospecting). NOT for warm leads or subscribers who have expressed interest.\n- **copywriting** — WHEN landing pages linked from emails need copy optimization that matches the email's message and audience. NOT for the email copy itself.\n- **launch-strategy** — WHEN coordinating email sequences around a specific product launch, announcement, or release window. NOT for evergreen nurture or onboarding sequences.\n- **analytics-tracking** — WHEN setting up email click tracking, UTM parameters, and attribution to connect email engagement to downstream conversions. NOT for writing or designing the sequence.\n- **onboarding-cro** — WHEN email sequences are supporting a parallel in-app onboarding flow and need to be coordinated to avoid duplication. NOT as a replacement for in-app onboarding experience.\n\n---\n\n## Communication\n\nDeliver email sequences as complete, ready-to-send drafts — include subject line, preview text, full body, and CTA for every email in the sequence. Always specify the trigger condition and send timing. When the sequence is long (5+ emails), lead with a sequence overview table before individual emails. Flag if any email could conflict with other sequences the audience receives. Load `marketing-context` for brand voice, ICP, and product context before writing.\n\n---\n\n## Proactive Triggers\n\n- User mentions low trial-to-paid conversion → ask if there's a trial expiration email sequence before recommending in-app or pricing changes.\n- User reports high open rates but low clicks → diagnose email body copy and CTA specificity before blaming subject lines.\n- User wants to \"do email marketing\" → clarify sequence type (welcome, nurture, re-engagement, etc.) before writing anything.\n- User has a product launch coming → recommend coordinating launch email sequence with in-app messaging and landing page copy for consistent messaging.\n- User mentions list is going cold → suggest re-engagement sequence with progressive offers before recommending acquisition spend.\n\n---\n\n## Output Artifacts\n\n| Artifact | Description |\n|----------|-------------|\n| Sequence Architecture Doc | Trigger, goal, length, timing, exit conditions, and branching logic for the full sequence |\n| Complete Email Drafts | Subject line, preview text, full body, and CTA for every email in the sequence |\n| Metrics Benchmarks | Open rate, click rate, and conversion rate targets per email type and sequence goal |\n| Segmentation Rules | Audience entry\u002Fexit conditions, behavioral branching, and suppression lists |\n| Subject Line Variations | 3 subject line alternatives per email for A\u002FB testing |\n\n---\n\n## Why This Skill Exists\n\nManage — When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also\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 the user mentions\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","# Email Sequence Design\n\nYou are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore creating a sequence, understand:\n\n1. **Sequence Type**\n   - Welcome\u002Fonboarding sequence\n   - Lead nurture sequence\n   - Re-engagement sequence\n   - Post-purchase sequence\n   - Event-based sequence\n   - Educational sequence\n   - Sales sequence\n\n2. **Audience Context**\n   - Who are they?\n   - What triggered them into this sequence?\n   - What do they already know\u002Fbelieve?\n   - What's their current relationship with you?\n\n3. **Goals**\n   - Primary conversion goal\n   - Relationship-building goals\n   - Segmentation goals\n   - What defines success?\n\n---\n\n## Core Principles\n→ See references\u002Femail-sequence-playbook.md for details\n\n## Output Format\n\n### Sequence Overview\n```\nSequence Name: [Name]\nTrigger: [What starts the sequence]\nGoal: [Primary conversion goal]\nLength: [Number of emails]\nTiming: [Delay between emails]\nExit Conditions: [When they leave the sequence]\n```\n\n### For Each Email\n```\nEmail [#]: [Name\u002FPurpose]\nSend: [Timing]\nSubject: [Subject line]\nPreview: [Preview text]\nBody: [Full copy]\nCTA: [Button text] → [Link destination]\nSegment\u002FConditions: [If applicable]\n```\n\n### Metrics Plan\nWhat to measure and benchmarks\n\n---\n\n## Task-Specific Questions\n\n1. What triggers entry to this sequence?\n2. What's the primary goal\u002Fconversion action?\n3. What do they already know about you?\n4. What other emails are they receiving?\n5. What's your current email performance?\n\n---\n\n## Tool Integrations\n\nFor implementation, see the [tools registry](..\u002F..\u002Ftools\u002FREGISTRY.md). Key email tools:\n\n| Tool | Best For | MCP | Guide |\n|------|----------|:---:|-------|\n| **Customer.io** | Behavior-based automation | - | [customer-io.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fcustomer-io.md) |\n| **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fmailchimp.md) |\n| **Resend** | Developer-friendly transactional | ✓ | [resend.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fresend.md) |\n| **SendGrid** | Transactional email at scale | - | [sendgrid.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fsendgrid.md) |\n| **Kit** | Creator\u002Fnewsletter focused | - | [kit.md](..\u002F..\u002Ftools\u002Fintegrations\u002Fkit.md) |\n\n---\n\n## Related Skills\n\n- **cold-email** — WHEN the sequence targets people who have NOT opted in (outbound prospecting). NOT for warm leads or subscribers who have expressed interest.\n- **copywriting** — WHEN landing pages linked from emails need copy optimization that matches the email's message and audience. NOT for the email copy itself.\n- **launch-strategy** — WHEN coordinating email sequences around a specific product launch, announcement, or release window. NOT for evergreen nurture or onboarding sequences.\n- **analytics-tracking** — WHEN setting up email click tracking, UTM parameters, and attribution to connect email engagement to downstream conversions. NOT for writing or designing the sequence.\n- **onboarding-cro** — WHEN email sequences are supporting a parallel in-app onboarding flow and need to be coordinated to avoid duplication. NOT as a replacement for in-app onboarding experience.\n\n---\n\n## Communication\n\nDeliver email sequences as complete, ready-to-send drafts — include subject line, preview text, full body, and CTA for every email in the sequence. Always specify the trigger condition and send timing. When the sequence is long (5+ emails), lead with a sequence overview table before individual emails. Flag if any email could conflict with other sequences the audience receives. Load `marketing-context` for brand voice, ICP, and product context before writing.\n\n---\n\n## Proactive Triggers\n\n- User mentions low trial-to-paid conversion → ask if there's a trial expiration email sequence before recommending in-app or pricing changes.\n- User reports high open rates but low clicks → diagnose email body copy and CTA specificity before blaming subject lines.\n- User wants to \"do email marketing\" → clarify sequence type (welcome, nurture, re-engagement, etc.) before writing anything.\n- User has a product launch coming → recommend coordinating launch email sequence with in-app messaging and landing page copy for consistent messaging.\n- User mentions list is going cold → suggest re-engagement sequence with progressive offers before recommending acquisition spend.\n\n---\n\n## Output Artifacts\n\n| Artifact | Description |\n|----------|-------------|\n| Sequence Architecture Doc | Trigger, goal, length, timing, exit conditions, and branching logic for the full sequence |\n| Complete Email Drafts | Subject line, preview text, full body, and CTA for every email in the sequence |\n| Metrics Benchmarks | Open rate, click rate, and conversion rate targets per email type and sequence goal |\n| Segmentation Rules | Audience entry\u002Fexit conditions, behavioral branching, and suppression lists |\n| Subject Line Variations | 3 subject line alternatives per email for A\u002FB testing |\n\n---\n\n## Why This Skill Exists\n\nManage — When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also\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 the user mentions\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":56,"anchors":57,"license":14,"executor":59,"metadata":60,"security":64,"skill_id":67,"description":7,"input_schema":68,"output_schema":75},"ADOPTED",[58,46],"business","HYBRID",{"author":61,"updated":62,"version":63,"category":46},"Alireza Rezvani",1772755200000,"1.0.0",{"pii":65,"level":66,"approval_required":52},true,"standard","business.marketing-skill.email-sequence",[69,73],{"name":70,"type":71,"required":65,"description":72},"code_or_task","string","Code snippet, script, or task description to process",{"name":45,"type":71,"required":52,"description":74},"Additional context or background information",[76,79],{"name":35,"type":77,"description":78},"object","Result from the automated action",{"name":43,"type":71,"description":80},"Execution status: success | partial | failure","main","19b1e9f092771d7e208f036df866ef2350da1fc8","skills\u002Fbusiness\u002Fmarketing-skill\u002Femail-sequence",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":89,"prompt":99,"zipAvailable":65},[90,93,96],{"tool":91,"command":92},"npx","npx skills add thiagofernandes1987-create\u002FAPEX --skill email-sequence",{"tool":94,"command":95},"bunx","bunx skills add thiagofernandes1987-create\u002FAPEX --skill email-sequence",{"tool":97,"command":98},"pnpm","pnpm dlx skills add thiagofernandes1987-create\u002FAPEX --skill email-sequence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness\u002Fmarketing-skill\u002Femail-sequence\u002FSKILL.md",[101,107],{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Femail-sequence-playbook.md","REFERENCE","参考文档",4820,"https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness\u002Fmarketing-skill\u002Femail-sequence\u002Freferences\u002Femail-sequence-playbook.md",{"path":108,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":111,"sourceHtmlUrl":112},"scripts\u002Fsequence_analyzer.py","SCRIPT","脚本",14162,"https:\u002F\u002Fgithub.com\u002Fthiagofernandes1987-create\u002FAPEX\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness\u002Fmarketing-skill\u002Femail-sequence\u002Fscripts\u002Fsequence_analyzer.py",[114,146,170,209,233,261],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":126,"publishedAt":51},"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",[120,123],{"categoryNo":121,"categoryName":122,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":124,"categoryName":125,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[127,128,129,130,131,132,133,134,135,50,136,137,138,139,140,141,142,143,144,145],"react","view","vercel","vercel react view transitions","react view transitions","transitions","css","components","component","ui","Animation","list","guide","integrate","fallback","shared","element","implementing","capability",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":154,"publishedAt":51},"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",[152,153],{"categoryNo":121,"categoryName":122,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":124,"categoryName":125,"taxonomyType":20,"taxonomyTypeDesc":21},[127,155,156,157,129,158,159,160,161,134,162,163,49,164,165,166,167,168,41,169],"vercel react best practices","best practices","react best practices","writing","performance","orchestration","workflow","react components","tasks","data","analysis","refactoring","never","next","data fetching",{"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":189,"publishedAt":51},"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",[176,179,182,183,186],{"categoryNo":177,"categoryName":178,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":180,"categoryName":181,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":124,"categoryName":125,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":184,"categoryName":185,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":187,"categoryName":188,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师",[190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,36],"terraform","terraform patterns","patterns","design","openclaw","gemini","gemini cli","implement","infrastructure","infrastructure-as-code","decisions","provider","strategies","agent skill","module","terraform infrastructure","as","infrastructure-as","for",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":218,"publishedAt":51},"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",[215],{"categoryNo":216,"categoryName":217,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",[219,220,221,222,223,197,224,49,165,225,226,227,228,229,230,231,41,40,232,66],"eval","self eval","self","code review","review","assessment","system","work","session","use","work session","scoring","get","true",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":248,"publishedAt":51},"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",[239,242,243,244,245],{"categoryNo":240,"categoryName":241,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":180,"categoryName":181,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":124,"categoryName":125,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":187,"categoryName":188,"taxonomyType":28,"taxonomyTypeDesc":29},{"categoryNo":246,"categoryName":247,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000033","数据分析师",[249,250,251,252,253,193,194,254,196,255,49,256,257,258,259,192,260,203,41,35],"chart builder","helm","helm chart builder","builder","chart","cli","visualization","template","generated","dependency","helm chart development","scaffolding",{"skillNo":262,"name":263,"nameZh":6,"description":264,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":265,"categories":266,"keywords":269,"publishedAt":51},"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",[267,268],{"categoryNo":177,"categoryName":178,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":124,"categoryName":125,"taxonomyType":20,"taxonomyTypeDesc":21},[270,271,272,193,273,160,274,49,275,276,277,278,279,203,41,40,280,208,36,35],"docker","development","docker development","security","dockerfile","Optimization","compose","container development","container security","docker-compose","container security hardening"]