[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EH3X3HFC1M7D6AQQ4FDZ7X":3,"skill-same:01M6EH3X3HFC1M7D6AQQ4FDZ7X":82},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6EH3X3HFC1M7D6AQQ4FDZ7X","seo-audit",null,"When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" or \"SEO health check.\" For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.","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\u002Fmarketingskills-seo-audit\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"audit","seo audit","seo","page","tags","ranking","pages","technical seo","health check","schema","use","check","technical","review","health","Meta Tags","Meta","issues","diagnose","structured data","2026-11-10 10:12:30",false,"---\nname: \"seo-audit\"\ndescription: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" or \"SEO health check.\" For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# SEO Audit\n\nYou are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.\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 auditing, understand:\n\n1. **Site Context**\n   - What type of site? (SaaS, e-commerce, blog, etc.)\n   - What's the primary business goal for SEO?\n   - What keywords\u002Ftopics are priorities?\n\n2. **Current State**\n   - Any known issues or concerns?\n   - Current organic traffic level?\n   - Recent changes or migrations?\n\n3. **Scope**\n   - Full site audit or specific pages?\n   - Technical + on-page, or one focus area?\n   - Access to Search Console \u002F analytics?\n\n---\n\n## Audit Framework\n→ See references\u002Fseo-audit-reference.md for details\n\n## Output Format\n\n### Audit Report Structure\n\n**Executive Summary**\n- Overall health assessment\n- Top 3-5 priority issues\n- Quick wins identified\n\n**Technical SEO Findings**\nFor each issue:\n- **Issue**: What's wrong\n- **Impact**: SEO impact (High\u002FMedium\u002FLow)\n- **Evidence**: How you found it\n- **Fix**: Specific recommendation\n- **Priority**: 1-5 or High\u002FMedium\u002FLow\n\n**On-Page SEO Findings**\nSame format as above\n\n**Content Findings**\nSame format as above\n\n**Prioritized Action Plan**\n1. Critical fixes (blocking indexation\u002Franking)\n2. High-impact improvements\n3. Quick wins (easy, immediate benefit)\n4. Long-term recommendations\n\n---\n\n## References\n\n- [AI Writing Detection](references\u002Fai-writing-detection.md): Common AI writing patterns to avoid (em dashes, overused phrases, filler words)\n- [AEO & GEO Patterns](references\u002Faeo-geo-patterns.md): Content patterns optimized for answer engines and AI citation\n\n---\n\n## Tools Referenced\n\n**Free Tools**\n- Google Search Console (essential)\n- Google PageSpeed Insights\n- Bing Webmaster Tools\n- Rich Results Test\n- Mobile-Friendly Test\n- Schema Validator\n\n**Paid Tools** (if available)\n- Screaming Frog\n- Ahrefs \u002F Semrush\n- Sitebulb\n- ContentKing\n\n---\n\n## Task-Specific Questions\n\n1. What pages\u002Fkeywords matter most?\n2. Do you have Search Console access?\n3. Any recent changes or migrations?\n4. Who are your top organic competitors?\n5. What's your current organic traffic baseline?\n\n---\n\n## Related Skills\n\n- **programmatic-seo** — WHEN: user wants to build SEO pages at scale after the audit identifies keyword gaps. WHEN NOT: don't use for diagnosing existing issues; stay in seo-audit mode.\n- **ai-seo** — WHEN: user wants to optimize for AI answer engines (SGE, Perplexity, ChatGPT) in addition to traditional search. WHEN NOT: don't use for purely technical crawl\u002Findexation issues.\n- **schema-markup** — WHEN: audit reveals missing structured data opportunities (FAQ, HowTo, Product, Review schemas). WHEN NOT: don't use as a standalone fix when core technical SEO is broken.\n- **site-architecture** — WHEN: audit uncovers poor internal linking, orphan pages, or crawl depth issues that need a structural redesign. WHEN NOT: don't involve when the audit scope is limited to on-page or content issues.\n- **content-strategy** — WHEN: audit reveals thin content, keyword gaps, or lack of topical authority requiring a content plan. WHEN NOT: don't use when the problem is purely technical (robots.txt, redirects, speed).\n- **marketing-context** — WHEN: always read first if `.claude\u002Fproduct-marketing-context.md` exists to avoid redundant questions. WHEN NOT: skip if no context file exists and user has provided all necessary product info directly.\n\n---\n\n## Communication\n\nAll audit output follows the **SEO Audit Quality Standard**:\n- Lead with the executive summary (3-5 bullets max)\n- Findings use the Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority format consistently\n- Prioritized Action Plan is always the final deliverable section\n- Avoid jargon without explanation; write for a technically-aware but non-SEO-specialist reader\n- Quick wins are called out explicitly and kept separate from high-effort recommendations\n- Never present recommendations without evidence or rationale\n\n---\n\n## Proactive Triggers\n\nAutomatically surface seo-audit recommendations when:\n\n1. **Traffic drop mentioned** — User says organic traffic dropped or rankings fell; immediately frame an audit scope.\n2. **Site migration or redesign** — User mentions a planned or recent URL change, platform switch, or redesign; flag pre\u002Fpost-migration audit needs.\n3. **\"Why isn't my page ranking?\"** — Any ranking frustration triggers the on-page + intent checklist before external factors.\n4. **Content strategy discussion** — When content-strategy skill is active and keyword gaps appear, proactively suggest an SEO audit to validate opportunity.\n5. **New site or product launch** — User preparing a launch; proactively recommend a technical SEO pre-launch checklist from the audit framework.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Executive Summary | Markdown bullets | 3-5 top issues + quick wins, suitable for sharing with stakeholders |\n| Technical SEO Findings | Structured table | Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority per finding |\n| On-Page SEO Findings | Structured table | Same format, focused on content and metadata |\n| Prioritized Action Plan | Numbered list | Ordered by impact × effort, grouped into Critical \u002F High \u002F Quick Wins |\n| Keyword Cannibalization Map | Table | Pages competing for same keyword with recommended canonical or redirect actions |\n","# SEO Audit\n\nYou are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.\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 auditing, understand:\n\n1. **Site Context**\n   - What type of site? (SaaS, e-commerce, blog, etc.)\n   - What's the primary business goal for SEO?\n   - What keywords\u002Ftopics are priorities?\n\n2. **Current State**\n   - Any known issues or concerns?\n   - Current organic traffic level?\n   - Recent changes or migrations?\n\n3. **Scope**\n   - Full site audit or specific pages?\n   - Technical + on-page, or one focus area?\n   - Access to Search Console \u002F analytics?\n\n---\n\n## Audit Framework\n→ See references\u002Fseo-audit-reference.md for details\n\n## Output Format\n\n### Audit Report Structure\n\n**Executive Summary**\n- Overall health assessment\n- Top 3-5 priority issues\n- Quick wins identified\n\n**Technical SEO Findings**\nFor each issue:\n- **Issue**: What's wrong\n- **Impact**: SEO impact (High\u002FMedium\u002FLow)\n- **Evidence**: How you found it\n- **Fix**: Specific recommendation\n- **Priority**: 1-5 or High\u002FMedium\u002FLow\n\n**On-Page SEO Findings**\nSame format as above\n\n**Content Findings**\nSame format as above\n\n**Prioritized Action Plan**\n1. Critical fixes (blocking indexation\u002Franking)\n2. High-impact improvements\n3. Quick wins (easy, immediate benefit)\n4. Long-term recommendations\n\n---\n\n## References\n\n- [AI Writing Detection](references\u002Fai-writing-detection.md): Common AI writing patterns to avoid (em dashes, overused phrases, filler words)\n- [AEO & GEO Patterns](references\u002Faeo-geo-patterns.md): Content patterns optimized for answer engines and AI citation\n\n---\n\n## Tools Referenced\n\n**Free Tools**\n- Google Search Console (essential)\n- Google PageSpeed Insights\n- Bing Webmaster Tools\n- Rich Results Test\n- Mobile-Friendly Test\n- Schema Validator\n\n**Paid Tools** (if available)\n- Screaming Frog\n- Ahrefs \u002F Semrush\n- Sitebulb\n- ContentKing\n\n---\n\n## Task-Specific Questions\n\n1. What pages\u002Fkeywords matter most?\n2. Do you have Search Console access?\n3. Any recent changes or migrations?\n4. Who are your top organic competitors?\n5. What's your current organic traffic baseline?\n\n---\n\n## Related Skills\n\n- **programmatic-seo** — WHEN: user wants to build SEO pages at scale after the audit identifies keyword gaps. WHEN NOT: don't use for diagnosing existing issues; stay in seo-audit mode.\n- **ai-seo** — WHEN: user wants to optimize for AI answer engines (SGE, Perplexity, ChatGPT) in addition to traditional search. WHEN NOT: don't use for purely technical crawl\u002Findexation issues.\n- **schema-markup** — WHEN: audit reveals missing structured data opportunities (FAQ, HowTo, Product, Review schemas). WHEN NOT: don't use as a standalone fix when core technical SEO is broken.\n- **site-architecture** — WHEN: audit uncovers poor internal linking, orphan pages, or crawl depth issues that need a structural redesign. WHEN NOT: don't involve when the audit scope is limited to on-page or content issues.\n- **content-strategy** — WHEN: audit reveals thin content, keyword gaps, or lack of topical authority requiring a content plan. WHEN NOT: don't use when the problem is purely technical (robots.txt, redirects, speed).\n- **marketing-context** — WHEN: always read first if `.claude\u002Fproduct-marketing-context.md` exists to avoid redundant questions. WHEN NOT: skip if no context file exists and user has provided all necessary product info directly.\n\n---\n\n## Communication\n\nAll audit output follows the **SEO Audit Quality Standard**:\n- Lead with the executive summary (3-5 bullets max)\n- Findings use the Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority format consistently\n- Prioritized Action Plan is always the final deliverable section\n- Avoid jargon without explanation; write for a technically-aware but non-SEO-specialist reader\n- Quick wins are called out explicitly and kept separate from high-effort recommendations\n- Never present recommendations without evidence or rationale\n\n---\n\n## Proactive Triggers\n\nAutomatically surface seo-audit recommendations when:\n\n1. **Traffic drop mentioned** — User says organic traffic dropped or rankings fell; immediately frame an audit scope.\n2. **Site migration or redesign** — User mentions a planned or recent URL change, platform switch, or redesign; flag pre\u002Fpost-migration audit needs.\n3. **\"Why isn't my page ranking?\"** — Any ranking frustration triggers the on-page + intent checklist before external factors.\n4. **Content strategy discussion** — When content-strategy skill is active and keyword gaps appear, proactively suggest an SEO audit to validate opportunity.\n5. **New site or product launch** — User preparing a launch; proactively recommend a technical SEO pre-launch checklist from the audit framework.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Executive Summary | Markdown bullets | 3-5 top issues + quick wins, suitable for sharing with stakeholders |\n| Technical SEO Findings | Structured table | Issue \u002F Impact \u002F Evidence \u002F Fix \u002F Priority per finding |\n| On-Page SEO Findings | Structured table | Same format, focused on content and metadata |\n| Prioritized Action Plan | Numbered list | Ordered by impact × effort, grouped into Critical \u002F High \u002F Quick Wins |\n| Keyword Cannibalization Map | Table | Pages competing for same keyword with recommended canonical or redirect actions |\n",{"name":5,"license":15,"metadata":54,"description":7},{"author":55,"updated":56,"version":57,"category":58},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fmarketingskills-seo-audit",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":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add levalencia\u002Fagent-god-mode --skill seo-audit",{"tool":74,"command":75},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill seo-audit",{"tool":77,"command":78},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill seo-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fmarketingskills-seo-audit\u002FSKILL.md",true,[],[83,105,138,164,190,217],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":49},"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",[],[90,91,92,93,94,95,96,97,98,99,100,101,102,103,104],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":120,"publishedAt":49},"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",[111,114,117],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":118,"categoryName":119,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[107,90,121,122,123,124,125,126,127,128,39,129,130,131,132,133,134,135,136,137],"automation","window management","monitoring","data","templates","api","system","operations","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":49},"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",[],[145,146,147,148,149,150,151,58,152,153,154,155,156,157,158,159,160,161,162,163],"twitter","x twitter growth","growth","competitive intelligence","search","analyzing","plan","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":49},"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,39,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":49},"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":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[200,201,202,203,204,205,206,207,208,209,210,211,212,124,213,214,215,216,35,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",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":233,"publishedAt":49},"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",[223,226,229,230],{"categoryNo":224,"categoryName":225,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":227,"categoryName":228,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":231,"categoryName":232,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[125,234,235,209,236,237,238,239,240,241,242,155,243,244,245,246,247,248,104,249],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]