[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGMBG2AP5RCF3A847DEKPX":3,"skill-same:01M6EGMBG2AP5RCF3A847DEKPX":74},{"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":23,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6EGMBG2AP5RCF3A847DEKPX","ln-732-cicd-generator",null,"Generates GitHub Actions CI workflow configuration","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-732-cicd-generator\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31],"cicd","ln 732 cicd generator","github","workflow","actions","ci","github actions","configuration","2026-11-10 10:12:30",false,"---\nname: ln-732-cicd-generator\ndescription: Generates GitHub Actions CI workflow configuration\nlicense: MIT\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-732-cicd-generator\n\n**Type:** L3 Worker\n**Category:** 7XX Project Bootstrap\n**Parent:** ln-730-devops-setup\n\nGenerates GitHub Actions CI pipeline for automated testing and validation.\n\n---\n\n## Purpose & Scope\n\nCreates CI\u002FCD workflow for GitHub:\n- **Does**: Generate .github\u002Fworkflows\u002Fci.yml with lint, test, build, docker jobs\n- **Does NOT**: Configure deployment, manage secrets, set up CD pipelines\n\n---\n\n## Inputs\n\n| Input | Source | Description |\n|-------|--------|-------------|\n| **Stack Type** | ln-730 coordinator | backend-dotnet, backend-python |\n| **Versions** | Auto-detected | Node.js, .NET or Python versions |\n| **Frontend Path** | Auto-detected | Path to frontend directory |\n| **Build Commands** | Auto-detected | npm scripts, dotnet\u002Fpytest commands |\n\n---\n\n## Outputs\n\n| File | Purpose | Template |\n|------|---------|----------|\n| `.github\u002Fworkflows\u002Fci.yml` | Main CI pipeline | [github_ci_dotnet.template.yml](references\u002Fgithub_ci_dotnet.template.yml) or [github_ci_python.template.yml](references\u002Fgithub_ci_python.template.yml) |\n\n---\n\n## Workflow\n\n### Phase 1: Stack Analysis\n\nDetermine which template to use:\n\n| Detection | Backend Template |\n|-----------|------------------|\n| `.sln` or `.csproj` present | github_ci_dotnet.template.yml |\n| `requirements.txt` or `pyproject.toml` present | github_ci_python.template.yml |\n\nDetect commands:\n- Frontend: Read scripts from package.json (lint, build, test)\n- .NET: Standard dotnet restore\u002Fbuild\u002Ftest\n- Python: pip install, ruff lint, pytest\n\n### Phase 2: Variable Substitution\n\nReplace template variables:\n\n| Variable | Source | Default |\n|----------|--------|---------|\n| `{{NODE_VERSION}}` | package.json engines | 22 |\n| `{{DOTNET_VERSION}}` | *.csproj TargetFramework | 9.0.x |\n| `{{PYTHON_VERSION}}` | pyproject.toml | 3.12 |\n| `{{FRONTEND_PATH}}` | Directory detection | src\u002Ffrontend |\n\n### Phase 3: Directory Creation\n\nCreate `.github\u002Fworkflows\u002F` directory if not exists.\n\n### Phase 4: File Generation\n\nGenerate ci.yml from selected template:\n1. Check if workflow already exists (warn before overwrite)\n2. Apply variable substitution\n3. Write to `.github\u002Fworkflows\u002Fci.yml`\n4. Validate YAML syntax\n\n---\n\n## Generated Pipeline Structure\n\n### Jobs Overview\n\n| Job | Purpose | Dependencies |\n|-----|---------|--------------|\n| **frontend** | Lint, build, test React\u002FVite | None |\n| **backend** | Build, test .NET or Python | None |\n| **docker** | Build images, health checks | frontend, backend |\n\n### Frontend Job Steps\n\n1. Checkout code\n2. Setup Node.js with caching\n3. Install dependencies (`npm ci`)\n4. Run linter (`npm run lint`)\n5. Build application (`npm run build`)\n6. Run tests (`npm test`)\n\n### Backend Job Steps (.NET)\n\n1. Checkout code\n2. Setup .NET SDK\n3. Restore dependencies (`dotnet restore`)\n4. Build (`dotnet build`)\n5. Run tests (`dotnet test`)\n\n### Backend Job Steps (Python)\n\n1. Checkout code\n2. Setup Python with pip caching\n3. Install dependencies (`pip install -r requirements.txt`)\n4. Run linter (`ruff check`)\n5. Run tests (`pytest`)\n\n### Docker Job Steps\n\n1. Checkout code\n2. Build images (`docker compose build`)\n3. Start containers (`docker compose up -d`)\n4. Wait for startup (30 seconds)\n5. Health check frontend (port 3000)\n6. Health check backend (port 5000\u002F8000)\n7. Show logs on failure\n8. Stop containers (`docker compose down`)\n\n---\n\n## Triggers\n\n| Event | Branches |\n|-------|----------|\n| **Push** | main, develop |\n| **Pull Request** | main |\n\n---\n\n## Best Practices Applied\n\n| Practice | Implementation |\n|----------|----------------|\n| **Dependency caching** | npm cache, pip cache |\n| **Pinned versions** | actions\u002Fcheckout@v4, setup-node@v4 |\n| **Parallel jobs** | frontend and backend run in parallel |\n| **Fail fast** | docker job waits for both to succeed |\n| **Clean up** | docker compose down runs always |\n| **Debug support** | logs shown on failure |\n\n---\n\n## Quality Criteria\n\nGenerated workflow must:\n- [ ] Pass YAML syntax validation\n- [ ] Use pinned action versions (not `@latest`)\n- [ ] Include dependency caching\n- [ ] Have health checks for docker job\n- [ ] Clean up resources on completion\n\n---\n\n## Critical Notes\n\n1. **GitHub Actions Only**: This skill generates only GitHub Actions workflows. No Azure\u002FGitLab support.\n2. **Template-based**: Use templates from references\u002F. Do NOT hardcode workflow contents.\n3. **Idempotent**: Check if .github\u002Fworkflows\u002F exists. Warn before overwriting ci.yml.\n4. **Version Detection**: Use detected versions, not hardcoded defaults.\n\n---\n\n## Reference Files\n\n| File | Purpose |\n|------|---------|\n| [github_ci.template.yml](references\u002Fgithub_ci.template.yml) | Full template with comments |\n| [github_ci_dotnet.template.yml](references\u002Fgithub_ci_dotnet.template.yml) | Compact .NET stack template |\n| [github_ci_python.template.yml](references\u002Fgithub_ci_python.template.yml) | Compact Python stack template |\n\n---\n\n**Version:** 1.1.0\n**Last Updated:** 2026-01-10\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-732-cicd-generator\n\n**Type:** L3 Worker\n**Category:** 7XX Project Bootstrap\n**Parent:** ln-730-devops-setup\n\nGenerates GitHub Actions CI pipeline for automated testing and validation.\n\n---\n\n## Purpose & Scope\n\nCreates CI\u002FCD workflow for GitHub:\n- **Does**: Generate .github\u002Fworkflows\u002Fci.yml with lint, test, build, docker jobs\n- **Does NOT**: Configure deployment, manage secrets, set up CD pipelines\n\n---\n\n## Inputs\n\n| Input | Source | Description |\n|-------|--------|-------------|\n| **Stack Type** | ln-730 coordinator | backend-dotnet, backend-python |\n| **Versions** | Auto-detected | Node.js, .NET or Python versions |\n| **Frontend Path** | Auto-detected | Path to frontend directory |\n| **Build Commands** | Auto-detected | npm scripts, dotnet\u002Fpytest commands |\n\n---\n\n## Outputs\n\n| File | Purpose | Template |\n|------|---------|----------|\n| `.github\u002Fworkflows\u002Fci.yml` | Main CI pipeline | [github_ci_dotnet.template.yml](references\u002Fgithub_ci_dotnet.template.yml) or [github_ci_python.template.yml](references\u002Fgithub_ci_python.template.yml) |\n\n---\n\n## Workflow\n\n### Phase 1: Stack Analysis\n\nDetermine which template to use:\n\n| Detection | Backend Template |\n|-----------|------------------|\n| `.sln` or `.csproj` present | github_ci_dotnet.template.yml |\n| `requirements.txt` or `pyproject.toml` present | github_ci_python.template.yml |\n\nDetect commands:\n- Frontend: Read scripts from package.json (lint, build, test)\n- .NET: Standard dotnet restore\u002Fbuild\u002Ftest\n- Python: pip install, ruff lint, pytest\n\n### Phase 2: Variable Substitution\n\nReplace template variables:\n\n| Variable | Source | Default |\n|----------|--------|---------|\n| `{{NODE_VERSION}}` | package.json engines | 22 |\n| `{{DOTNET_VERSION}}` | *.csproj TargetFramework | 9.0.x |\n| `{{PYTHON_VERSION}}` | pyproject.toml | 3.12 |\n| `{{FRONTEND_PATH}}` | Directory detection | src\u002Ffrontend |\n\n### Phase 3: Directory Creation\n\nCreate `.github\u002Fworkflows\u002F` directory if not exists.\n\n### Phase 4: File Generation\n\nGenerate ci.yml from selected template:\n1. Check if workflow already exists (warn before overwrite)\n2. Apply variable substitution\n3. Write to `.github\u002Fworkflows\u002Fci.yml`\n4. Validate YAML syntax\n\n---\n\n## Generated Pipeline Structure\n\n### Jobs Overview\n\n| Job | Purpose | Dependencies |\n|-----|---------|--------------|\n| **frontend** | Lint, build, test React\u002FVite | None |\n| **backend** | Build, test .NET or Python | None |\n| **docker** | Build images, health checks | frontend, backend |\n\n### Frontend Job Steps\n\n1. Checkout code\n2. Setup Node.js with caching\n3. Install dependencies (`npm ci`)\n4. Run linter (`npm run lint`)\n5. Build application (`npm run build`)\n6. Run tests (`npm test`)\n\n### Backend Job Steps (.NET)\n\n1. Checkout code\n2. Setup .NET SDK\n3. Restore dependencies (`dotnet restore`)\n4. Build (`dotnet build`)\n5. Run tests (`dotnet test`)\n\n### Backend Job Steps (Python)\n\n1. Checkout code\n2. Setup Python with pip caching\n3. Install dependencies (`pip install -r requirements.txt`)\n4. Run linter (`ruff check`)\n5. Run tests (`pytest`)\n\n### Docker Job Steps\n\n1. Checkout code\n2. Build images (`docker compose build`)\n3. Start containers (`docker compose up -d`)\n4. Wait for startup (30 seconds)\n5. Health check frontend (port 3000)\n6. Health check backend (port 5000\u002F8000)\n7. Show logs on failure\n8. Stop containers (`docker compose down`)\n\n---\n\n## Triggers\n\n| Event | Branches |\n|-------|----------|\n| **Push** | main, develop |\n| **Pull Request** | main |\n\n---\n\n## Best Practices Applied\n\n| Practice | Implementation |\n|----------|----------------|\n| **Dependency caching** | npm cache, pip cache |\n| **Pinned versions** | actions\u002Fcheckout@v4, setup-node@v4 |\n| **Parallel jobs** | frontend and backend run in parallel |\n| **Fail fast** | docker job waits for both to succeed |\n| **Clean up** | docker compose down runs always |\n| **Debug support** | logs shown on failure |\n\n---\n\n## Quality Criteria\n\nGenerated workflow must:\n- [ ] Pass YAML syntax validation\n- [ ] Use pinned action versions (not `@latest`)\n- [ ] Include dependency caching\n- [ ] Have health checks for docker job\n- [ ] Clean up resources on completion\n\n---\n\n## Critical Notes\n\n1. **GitHub Actions Only**: This skill generates only GitHub Actions workflows. No Azure\u002FGitLab support.\n2. **Template-based**: Use templates from references\u002F. Do NOT hardcode workflow contents.\n3. **Idempotent**: Check if .github\u002Fworkflows\u002F exists. Warn before overwriting ci.yml.\n4. **Version Detection**: Use detected versions, not hardcoded defaults.\n\n---\n\n## Reference Files\n\n| File | Purpose |\n|------|---------|\n| [github_ci.template.yml](references\u002Fgithub_ci.template.yml) | Full template with comments |\n| [github_ci_dotnet.template.yml](references\u002Fgithub_ci_dotnet.template.yml) | Compact .NET stack template |\n| [github_ci_python.template.yml](references\u002Fgithub_ci_python.template.yml) | Compact Python stack template |\n\n---\n\n**Version:** 1.1.0\n**Last Updated:** 2026-01-10\n",{"name":5,"license":15,"description":7},"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-732-cicd-generator",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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-732-cicd-generator",{"tool":52,"command":53},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-732-cicd-generator",{"tool":55,"command":56},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-732-cicd-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-732-cicd-generator\u002FSKILL.md",true,[60,66,70],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fgithub_ci_dotnet.template.yml","REFERENCE","参考文档",1546,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-732-cicd-generator\u002Freferences\u002Fgithub_ci_dotnet.template.yml",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fgithub_ci_python.template.yml",1708,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-732-cicd-generator\u002Freferences\u002Fgithub_ci_python.template.yml",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fgithub_ci.template.yml",4826,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-732-cicd-generator\u002Freferences\u002Fgithub_ci.template.yml",[75,97,133,160,186,214],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":32},"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",[],[82,83,84,85,86,87,88,89,90,91,92,93,94,95,96],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":114,"publishedAt":32},"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",[103,106,109],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[99,82,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":32},"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",[],[140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159],"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":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":32},"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",[],[167,168,169,170,171,172,173,174,175,176,177,178,123,179,180,181,182,183,184,185],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":195,"publishedAt":32},"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",[192],{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[196,197,198,199,200,201,202,203,204,205,206,207,208,118,209,210,211,212,213,128],"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":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":230,"publishedAt":32},"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",[220,223,226,227],{"categoryNo":221,"categoryName":222,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":224,"categoryName":225,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":228,"categoryName":229,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000036","内容创作者",[119,231,232,205,233,234,235,236,237,238,239,151,240,241,242,243,244,245,96,246],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]