[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGQDB1J6THM0BPTJ3QWKFM":3,"skill-same:01M6EGQDB1J6THM0BPTJ3QWKFM":77},{"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":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6EGQDB1J6THM0BPTJ3QWKFM","ln-913-community-debater",null,"Launch RFC\u002Fdebate discussions on GitHub: define topic, classify type, compose structured RFC\u002Fpoll, review, publish via GraphQL","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\u002Fln-913-community-debater\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"ln 913 community debater","community","webfetch","via","debate","type","classify","define","structured","compose","review","read","grep","RFC","Bash","GraphQL","publish","launch","github","2026-11-10 10:12:30",false,"---\nname: ln-913-community-debater\ndescription: \"Launch RFC\u002Fdebate discussions on GitHub: define topic, classify type, compose structured RFC\u002Fpoll, review, publish via GraphQL\"\nlicense: MIT\nallowed-tools: Read, Grep, Glob, Bash, WebFetch\n---\n\n> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n# ln-913-community-debater\n\n**Type:** L3 Worker (standalone)\n**Category:** 9XX Community Engagement\n**Caller:** ln-910-community-engagement (or standalone)\n\nLaunches structured debate discussions in GitHub Discussions for decisions that benefit from community input.\n\n---\n\n## Phase 0: GitHub Discovery\n\n**MANDATORY READ:** Load `..\u002Fln-910-community-engagement\u002Freferences\u002Fgithub_discovery.md`\n\nExecute the discovery protocol. Extract:\n- `{owner}\u002F{repo}` for URLs and codebase context\n- `repo.id` for GraphQL mutation\n- `categories[\"Ideas\"]` for RFC\u002FProposal discussions\n- `categories[\"Polls\"]` for Prioritization polls\n- Verify required categories exist\n\nLoad strategy: check `docs\u002Fcommunity_engagement_strategy.md` in target project, fallback to `..\u002Fln-910-community-engagement\u002Freferences\u002Fcommunity_strategy_template.md`. Extract Section 3 (Debate Triggers) and Section 1 (Decision Matrix).\n\n**MANDATORY READ:** Load `..\u002Fln-910-community-engagement\u002Freferences\u002Fdiscussion_formatting.md`\n\n---\n\n## Phase 1: Define the Topic\n\nIf `$ARGUMENTS` provided, use as the topic seed. Otherwise, ask the user what they want to debate.\n\nGather context:\n1. Read strategy Section 3 -- verify this qualifies as a debate\n2. Grep the codebase for files related to the topic\n3. Read relevant SKILL.md files, docs, or shared references\n4. Identify existing patterns that the proposal might change\n\n---\n\n## Phase 2: Classify Debate Type\n\n| Type | Prefix | Category | When to use |\n|------|--------|----------|-------------|\n| **Maintainer RFC** -- design mostly done, seeking validation | `[RFC]` | Ideas | End of design process, soft announcement |\n| **Community RFC** -- early stage, genuinely open to alternatives | `[RFC]` | Ideas | Beginning of design, kickstart discussion |\n| **Proposal** -- new feature or restructuring | `[Proposal]` | Ideas | Concrete idea with use case |\n| **Workflow Change** -- pipeline, task flow, or conventions | `[RFC]` | Ideas | Affects multiple areas or user workflows |\n| **Prioritization** -- what to build next, feature ranking | `[Poll]` | Polls | Multiple options, need community vote |\n\nIf type is **Prioritization**, switch to Polls flow (Phase 4).\n\n---\n\n## Phase 3: Compose RFC Discussion\n\nUse the **RFC Structure Pattern** from `discussion_formatting.md` (loaded in Phase 0).\n\n**Skill-specific additions beyond the shared pattern:**\n- Add `## Unresolved Details` section after Open Questions — implementation details not yet decided, to be resolved during development\n- Add `## Decision Criteria` section — how the decision will be made (metrics, feedback threshold)\n- Minimum 2 alternatives in the Alternatives table\n\n---\n\n## Phase 4: Compose Poll (for Prioritization type)\n\nGitHub Discussions Polls are created via UI only. Instead, compose a reaction-based voting discussion:\n\n```\n## {Topic}\n\n{1-2 sentence context}\n\n**Vote by reacting to the options below** (each option is posted as a separate comment -- use :+1: to vote).\n\n### Context\n{Why this decision matters now}\n```\n\nAfter creating the discussion, post each option as a separate comment for reaction-based voting.\n\n---\n\n## Phase 5: Review and Publish\n\nPresent the composed title + body to the user. **Wait for explicit approval before publishing.**\n\nAfter approval, publish via GraphQL using discovery context:\n\n```bash\ngh api graphql -f query='\n  mutation($title: String!, $body: String!, $repoId: ID!, $catId: ID!) {\n    createDiscussion(input: {\n      repositoryId: $repoId,\n      categoryId: $catId,\n      title: $title,\n      body: $body\n    }) {\n      discussion { url id }\n    }\n  }\n' -f title=\"TITLE_HERE\" -f body=\"BODY_HERE\" -f repoId=\"{repo.id}\" -f catId=\"{categories.Ideas or categories.Polls}\"\n```\n\nFor **Polls**, after creating the discussion, post each option as a comment:\n\n```bash\ngh api graphql -f query='\n  mutation($discussionId: ID!, $body: String!) {\n    addDiscussionComment(input: {\n      discussionId: $discussionId,\n      body: $body\n    }) {\n      comment { url }\n    }\n  }\n' -f discussionId=\"DISCUSSION_NODE_ID\" -f body=\"**Option N:** {description}\"\n```\n\nReport the discussion URL to the user.\n\n---\n\n## Rules\n\n- Always present the full composed text for user approval before publishing\n- Never publish without explicit user confirmation\n- Title: descriptive, under 80 chars, prefixed with [RFC], [Proposal], or [Poll]\n- Body: factual, not persuasive -- present options neutrally\n- Include links to relevant code\u002Fdocs in the repository\n- Set a decision timeline when applicable\n- Minimum 2 alternatives in the Alternatives table\n- Tone: \"We're considering X. Here are the tradeoffs. What's your take?\"\n\n---\n\n## Definition of Done\n\n- [ ] Topic defined with codebase context gathered\n- [ ] Debate type classified (RFC\u002FProposal\u002FWorkflow\u002FPrioritization)\n- [ ] RFC or poll composed with minimum 2 alternatives\n- [ ] User approved final draft\n- [ ] Published via GraphQL mutation, URL reported\n\n---\n\n**Version:** 1.0.0\n**Last Updated:** 2026-03-13\n","> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n# ln-913-community-debater\n\n**Type:** L3 Worker (standalone)\n**Category:** 9XX Community Engagement\n**Caller:** ln-910-community-engagement (or standalone)\n\nLaunches structured debate discussions in GitHub Discussions for decisions that benefit from community input.\n\n---\n\n## Phase 0: GitHub Discovery\n\n**MANDATORY READ:** Load `..\u002Fln-910-community-engagement\u002Freferences\u002Fgithub_discovery.md`\n\nExecute the discovery protocol. Extract:\n- `{owner}\u002F{repo}` for URLs and codebase context\n- `repo.id` for GraphQL mutation\n- `categories[\"Ideas\"]` for RFC\u002FProposal discussions\n- `categories[\"Polls\"]` for Prioritization polls\n- Verify required categories exist\n\nLoad strategy: check `docs\u002Fcommunity_engagement_strategy.md` in target project, fallback to `..\u002Fln-910-community-engagement\u002Freferences\u002Fcommunity_strategy_template.md`. Extract Section 3 (Debate Triggers) and Section 1 (Decision Matrix).\n\n**MANDATORY READ:** Load `..\u002Fln-910-community-engagement\u002Freferences\u002Fdiscussion_formatting.md`\n\n---\n\n## Phase 1: Define the Topic\n\nIf `$ARGUMENTS` provided, use as the topic seed. Otherwise, ask the user what they want to debate.\n\nGather context:\n1. Read strategy Section 3 -- verify this qualifies as a debate\n2. Grep the codebase for files related to the topic\n3. Read relevant SKILL.md files, docs, or shared references\n4. Identify existing patterns that the proposal might change\n\n---\n\n## Phase 2: Classify Debate Type\n\n| Type | Prefix | Category | When to use |\n|------|--------|----------|-------------|\n| **Maintainer RFC** -- design mostly done, seeking validation | `[RFC]` | Ideas | End of design process, soft announcement |\n| **Community RFC** -- early stage, genuinely open to alternatives | `[RFC]` | Ideas | Beginning of design, kickstart discussion |\n| **Proposal** -- new feature or restructuring | `[Proposal]` | Ideas | Concrete idea with use case |\n| **Workflow Change** -- pipeline, task flow, or conventions | `[RFC]` | Ideas | Affects multiple areas or user workflows |\n| **Prioritization** -- what to build next, feature ranking | `[Poll]` | Polls | Multiple options, need community vote |\n\nIf type is **Prioritization**, switch to Polls flow (Phase 4).\n\n---\n\n## Phase 3: Compose RFC Discussion\n\nUse the **RFC Structure Pattern** from `discussion_formatting.md` (loaded in Phase 0).\n\n**Skill-specific additions beyond the shared pattern:**\n- Add `## Unresolved Details` section after Open Questions — implementation details not yet decided, to be resolved during development\n- Add `## Decision Criteria` section — how the decision will be made (metrics, feedback threshold)\n- Minimum 2 alternatives in the Alternatives table\n\n---\n\n## Phase 4: Compose Poll (for Prioritization type)\n\nGitHub Discussions Polls are created via UI only. Instead, compose a reaction-based voting discussion:\n\n```\n## {Topic}\n\n{1-2 sentence context}\n\n**Vote by reacting to the options below** (each option is posted as a separate comment -- use :+1: to vote).\n\n### Context\n{Why this decision matters now}\n```\n\nAfter creating the discussion, post each option as a separate comment for reaction-based voting.\n\n---\n\n## Phase 5: Review and Publish\n\nPresent the composed title + body to the user. **Wait for explicit approval before publishing.**\n\nAfter approval, publish via GraphQL using discovery context:\n\n```bash\ngh api graphql -f query='\n  mutation($title: String!, $body: String!, $repoId: ID!, $catId: ID!) {\n    createDiscussion(input: {\n      repositoryId: $repoId,\n      categoryId: $catId,\n      title: $title,\n      body: $body\n    }) {\n      discussion { url id }\n    }\n  }\n' -f title=\"TITLE_HERE\" -f body=\"BODY_HERE\" -f repoId=\"{repo.id}\" -f catId=\"{categories.Ideas or categories.Polls}\"\n```\n\nFor **Polls**, after creating the discussion, post each option as a comment:\n\n```bash\ngh api graphql -f query='\n  mutation($discussionId: ID!, $body: String!) {\n    addDiscussionComment(input: {\n      discussionId: $discussionId,\n      body: $body\n    }) {\n      comment { url }\n    }\n  }\n' -f discussionId=\"DISCUSSION_NODE_ID\" -f body=\"**Option N:** {description}\"\n```\n\nReport the discussion URL to the user.\n\n---\n\n## Rules\n\n- Always present the full composed text for user approval before publishing\n- Never publish without explicit user confirmation\n- Title: descriptive, under 80 chars, prefixed with [RFC], [Proposal], or [Poll]\n- Body: factual, not persuasive -- present options neutrally\n- Include links to relevant code\u002Fdocs in the repository\n- Set a decision timeline when applicable\n- Minimum 2 alternatives in the Alternatives table\n- Tone: \"We're considering X. Here are the tradeoffs. What's your take?\"\n\n---\n\n## Definition of Done\n\n- [ ] Topic defined with codebase context gathered\n- [ ] Debate type classified (RFC\u002FProposal\u002FWorkflow\u002FPrioritization)\n- [ ] RFC or poll composed with minimum 2 alternatives\n- [ ] User approved final draft\n- [ ] Published via GraphQL mutation, URL reported\n\n---\n\n**Version:** 1.0.0\n**Last Updated:** 2026-03-13\n",{"name":5,"license":15,"description":7,"allowed-tools":43},"Read, Grep, Glob, Bash, WebFetch","main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-913-community-debater",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-913-community-debater",{"tool":59,"command":60},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-913-community-debater",{"tool":62,"command":63},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-913-community-debater","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-913-community-debater\u002FSKILL.md",true,[67,73],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"existing-app-analysis.md","REFERENCE","参考文档",1216,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fclaude-code-apple-skills\u002Fskills\u002Fmacos\u002Fapp-planner\u002Fexisting-app-analysis.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"new-app-planning.md",1115,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Mobile-Dev\u002Ffrom-article-18-ui-ux\u002Fclaude-code-apple-skills\u002Fskills\u002Fmacos\u002Fapp-planner\u002Fnew-app-planning.md",[78,100,137,164,190,218],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":38},"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",[],[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":119,"publishedAt":38},"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",[106,111,114],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":112,"categoryName":113,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[102,85,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,22,136],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","bulk",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":38},"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",[],[144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163],"twitter","x twitter growth","growth","competitive intelligence","search","analyzing","plan","marketing","web search","competitors","analyze","write","optimize","social","intelligence","viral","growth engine","mechanics","grow","competitive",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":38},"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",[],[171,172,173,174,175,176,177,178,179,180,181,182,128,183,184,185,186,187,188,189],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":199,"publishedAt":38},"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",[196],{"categoryNo":197,"categoryName":198,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000009","前端开发",[200,201,202,203,204,205,206,207,208,209,210,211,212,123,213,214,215,216,217,133],"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":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":234,"publishedAt":38},"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",[224,227,230,231],{"categoryNo":225,"categoryName":226,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":228,"categoryName":229,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":112,"categoryName":113,"taxonomyType":109,"taxonomyTypeDesc":110},{"categoryNo":232,"categoryName":233,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000036","内容创作者",[124,235,236,209,237,238,239,240,33,241,30,155,242,243,244,245,246,247,99,248],"venue templates","research","NeurIPS","ICML","LaTeX","science","access","edit","proposals","Academic","requirements","formatting","journal","chi"]