[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EB9G9WE69RT3PFM1DH6TSK":3,"skill-same:01M6EB9G9WE69RT3PFM1DH6TSK":95},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6EB9G9WE69RT3PFM1DH6TSK","email-sequence",null,"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,\" \"drip campaign,\" \"nurture sequence,\" \"onboarding emails,\" \"welcome sequence,\" \"re-engagement emails,\" \"email automation,\" or \"lifecycle emails.\" For in-app onboarding, see onboarding-cro.","levalencia\u002Fagent-god-mode","levalencia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6962857?v=4","01M6EB0FZZ4BPQPC4HET4QY6NM","Luis Valencia ","01M6EB0G4HWHPWW0H9X7QKSAHP",3,"MIT","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002F.gemini-email-sequence-1\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"email","email sequence","cro","welcome sequence","drip campaign","app","emails","optimize","campaign","engagement","use","user","automation","marketing","lifecycle","flow","onboarding","create","welcome","2026-11-10 10:12:30",false,"---\nname: \"email-sequence\"\ndescription: 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,\" \"drip campaign,\" \"nurture sequence,\" \"onboarding emails,\" \"welcome sequence,\" \"re-engagement emails,\" \"email automation,\" or \"lifecycle emails.\" For in-app onboarding, see onboarding-cro.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\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","# 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",{"name":5,"license":15,"metadata":56,"description":7},{"author":57,"updated":58,"version":59,"category":45},"Alireza Rezvani",1772755200000,"1.0.0","main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002F.gemini-email-sequence-1",1,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode","https:\u002F\u002Fgithub.com\u002Flevalencia","https:\u002F\u002Fmedium.com\u002F@luisevalencia","Microsoft MVP - Artificial Intelligence\r\nMachine Learning Enthusiast\r\n","2026-05-02 06:55:36",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add levalencia\u002Fagent-god-mode --skill email-sequence",{"tool":75,"command":76},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill email-sequence",{"tool":78,"command":79},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill email-sequence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002F.gemini-email-sequence-1\u002FSKILL.md",true,[83,89],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Femail-sequence-playbook.md","REFERENCE","参考文档",4820,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002F.gemini-email-sequence-1\u002Freferences\u002Femail-sequence-playbook.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fsequence_analyzer.py","SCRIPT","脚本",13736,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002F.gemini-email-sequence-1\u002Fscripts\u002Fsequence_analyzer.py",[96,118,150,175,201,229],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":51},"01M6EM8ES5M9J4S8N78NJST0YC","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzarr-python\u002FSKILL.md",[],[103,104,105,106,107,108,109,110,111,112,113,114,115,116,117],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":133,"publishedAt":51},"01M6EM8AR6ZFKZ9YVW8TTG850Z","zabbix","Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper\u002Fsender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User\u002Fpermission management","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzabbix-api-skill\u002FSKILL.md",[124,127,130],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":131,"categoryName":132,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师",[120,103,44,134,135,136,137,138,139,140,42,141,142,143,144,145,146,147,148,149],"window management","monitoring","data","templates","api","system","operations","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":51},"01M6EM6Q9JG846ECQY9A210A26","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fx-twitter-growth\u002FSKILL.md",[],[157,158,159,160,161,162,163,45,164,165,166,167,39,168,169,170,171,172,173,174],"twitter","x twitter growth","growth","competitive intelligence","search","analyzing","plan","web search","competitors","analyze","write","social","intelligence","viral","growth engine","mechanics","grow","competitive",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":51},"01M6EM3FQNPYNKPC4CV9TCVNGD","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwhat-if-oracle\u002FSKILL.md",[],[182,183,184,185,186,187,188,189,190,191,192,193,42,194,195,196,197,198,199,200],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":210,"publishedAt":51},"01M6EM08C06RGDYCJ86HAPK0FF","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\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvercel-react-best-practices\u002FSKILL.md",[207],{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[211,212,213,214,215,216,217,218,219,220,221,222,223,136,224,225,226,227,228,145],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","tasks","code","Optimization","Next.js","refactoring","performance optimization","next","pages",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":245,"publishedAt":51},"01M6EM00S13326QM08DTM94J6Z","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvenue-templates\u002FSKILL.md",[235,238,241,242],{"categoryNo":236,"categoryName":237,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":239,"categoryName":240,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":243,"categoryName":244,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[137,246,247,220,248,249,250,251,252,253,254,167,255,256,257,258,259,260,117,261],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]