[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGNS4JY3F5VT8VQ4X9QRHD":3,"skill-same:01M6EGNS4JY3F5VT8VQ4X9QRHD":51},{"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":23,"linkOnly":24,"markdownContent":25,"markdownBody":26,"frontMatter":27,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M6EGNS4JY3F5VT8VQ4X9QRHD","ln-781-build-verifier",null,"Builds all detected projects and verifies successful compilation","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-781-build-verifier\u002FSKILL.md",[],[19,20,21,22],"build","verifier","ln 781 build verifier","projects","2026-11-10 10:12:30",false,"---\nname: ln-781-build-verifier\ndescription: Builds all detected projects and verifies successful compilation\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-781-build-verifier\n\n**Type:** L3 Worker\n**Category:** 7XX Project Bootstrap\n**Parent:** ln-780-bootstrap-verifier\n\n---\n\n## Purpose\n\nDetects project types, restores dependencies, executes builds, and verifies successful compilation.\n\n**Scope:**\n- Auto-detect project types from file markers\n- Restore dependencies using appropriate package manager\n- Execute build commands for each project\n- Verify build artifacts exist\n\n**Out of Scope:**\n- Running tests (handled by ln-782)\n- Container operations (handled by ln-783)\n- Workflow orchestration (handled by ln-780)\n\n---\n\n## When to Use\n\n| Scenario | Use This Skill |\n|----------|---------------|\n| Called by ln-780 orchestrator | Yes |\n| Standalone build verification | Yes |\n| CI\u002FCD pipeline build step | Yes |\n| Test execution needed | No, use ln-782 |\n\n---\n\n## Workflow\n\n### Step 1: Detect Project Types\n\nScan project root for type markers.\n\n| Marker File | Project Type | Build System |\n|------------|--------------|--------------|\n| package.json | Node.js\u002FFrontend | npm\u002Fyarn\u002Fpnpm |\n| *.csproj | .NET | dotnet |\n| setup.py \u002F pyproject.toml | Python | pip\u002Fpoetry |\n| go.mod | Go | go build |\n| Cargo.toml | Rust | cargo |\n| pom.xml | Java\u002FMaven | mvn |\n| build.gradle | Java\u002FGradle | gradle |\n\n### Step 2: Restore Dependencies\n\nFor each detected project, restore dependencies before building.\n\n| Project Type | Dependency Restoration |\n|--------------|----------------------|\n| Node.js | Install packages from lock file |\n| .NET | Restore NuGet packages |\n| Python | Install from requirements or pyproject |\n| Go | Download modules |\n| Rust | Fetch crates |\n\n### Step 3: Build Projects\n\nExecute build for each project type in Release\u002FProduction mode.\n\n| Project Type | Build Mode | Expected Outcome |\n|--------------|-----------|------------------|\n| Node.js | Production | Bundled assets in dist\u002F or build\u002F |\n| .NET | Release | Compiled DLLs in bin\u002FRelease\u002F |\n| Python | Editable install | Package installed in environment |\n| Go | Production | Compiled binary |\n| Rust | Release | Optimized binary in target\u002Frelease\u002F |\n\n### Step 4: Verify Build Artifacts\n\nConfirm build outputs exist.\n\n| Project Type | Artifact Check |\n|--------------|---------------|\n| Node.js | dist\u002F or build\u002F directory exists, contains files |\n| .NET | DLL files in bin\u002FRelease\u002F{framework}\u002F |\n| Python | Package importable |\n| Go | Binary executable exists |\n| Rust | Binary in target\u002Frelease\u002F |\n\n### Step 5: Report Results\n\nReturn structured results to orchestrator.\n\n**Result Structure:**\n\n| Field | Description |\n|-------|-------------|\n| projectName | Name of the project |\n| projectType | Detected type (nodejs, dotnet, python, etc.) |\n| status | success \u002F failed |\n| duration | Build time in seconds |\n| outputPath | Path to build artifacts |\n| errorMessage | Error details if failed |\n\n---\n\n## Error Handling\n\n| Error Type | Recovery Action |\n|------------|----------------|\n| Dependency restore failed | Check network, verify lock file integrity |\n| Compilation errors | Log full error output, report as failed |\n| Missing build tool | Report required tool installation |\n| Timeout | Report timeout, suggest increasing limit |\n\n---\n\n## Critical Rules\n\n1. **Always restore dependencies first** - builds may fail without fresh dependencies\n2. **Use production\u002Frelease mode** - development builds may hide issues\n3. **Verify artifacts exist** - successful exit code is not sufficient\n4. **Report all projects** - include both successful and failed builds\n\n---\n\n## Definition of Done\n\n- [ ] All project types detected\n- [ ] Dependencies restored for each project\n- [ ] Build executed for each project\n- [ ] Artifacts verified to exist\n- [ ] Results returned to orchestrator\n\n---\n\n## Reference Files\n\n- Parent: `..\u002Fln-780-bootstrap-verifier\u002FSKILL.md`\n\n---\n\n**Version:** 2.0.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-781-build-verifier\n\n**Type:** L3 Worker\n**Category:** 7XX Project Bootstrap\n**Parent:** ln-780-bootstrap-verifier\n\n---\n\n## Purpose\n\nDetects project types, restores dependencies, executes builds, and verifies successful compilation.\n\n**Scope:**\n- Auto-detect project types from file markers\n- Restore dependencies using appropriate package manager\n- Execute build commands for each project\n- Verify build artifacts exist\n\n**Out of Scope:**\n- Running tests (handled by ln-782)\n- Container operations (handled by ln-783)\n- Workflow orchestration (handled by ln-780)\n\n---\n\n## When to Use\n\n| Scenario | Use This Skill |\n|----------|---------------|\n| Called by ln-780 orchestrator | Yes |\n| Standalone build verification | Yes |\n| CI\u002FCD pipeline build step | Yes |\n| Test execution needed | No, use ln-782 |\n\n---\n\n## Workflow\n\n### Step 1: Detect Project Types\n\nScan project root for type markers.\n\n| Marker File | Project Type | Build System |\n|------------|--------------|--------------|\n| package.json | Node.js\u002FFrontend | npm\u002Fyarn\u002Fpnpm |\n| *.csproj | .NET | dotnet |\n| setup.py \u002F pyproject.toml | Python | pip\u002Fpoetry |\n| go.mod | Go | go build |\n| Cargo.toml | Rust | cargo |\n| pom.xml | Java\u002FMaven | mvn |\n| build.gradle | Java\u002FGradle | gradle |\n\n### Step 2: Restore Dependencies\n\nFor each detected project, restore dependencies before building.\n\n| Project Type | Dependency Restoration |\n|--------------|----------------------|\n| Node.js | Install packages from lock file |\n| .NET | Restore NuGet packages |\n| Python | Install from requirements or pyproject |\n| Go | Download modules |\n| Rust | Fetch crates |\n\n### Step 3: Build Projects\n\nExecute build for each project type in Release\u002FProduction mode.\n\n| Project Type | Build Mode | Expected Outcome |\n|--------------|-----------|------------------|\n| Node.js | Production | Bundled assets in dist\u002F or build\u002F |\n| .NET | Release | Compiled DLLs in bin\u002FRelease\u002F |\n| Python | Editable install | Package installed in environment |\n| Go | Production | Compiled binary |\n| Rust | Release | Optimized binary in target\u002Frelease\u002F |\n\n### Step 4: Verify Build Artifacts\n\nConfirm build outputs exist.\n\n| Project Type | Artifact Check |\n|--------------|---------------|\n| Node.js | dist\u002F or build\u002F directory exists, contains files |\n| .NET | DLL files in bin\u002FRelease\u002F{framework}\u002F |\n| Python | Package importable |\n| Go | Binary executable exists |\n| Rust | Binary in target\u002Frelease\u002F |\n\n### Step 5: Report Results\n\nReturn structured results to orchestrator.\n\n**Result Structure:**\n\n| Field | Description |\n|-------|-------------|\n| projectName | Name of the project |\n| projectType | Detected type (nodejs, dotnet, python, etc.) |\n| status | success \u002F failed |\n| duration | Build time in seconds |\n| outputPath | Path to build artifacts |\n| errorMessage | Error details if failed |\n\n---\n\n## Error Handling\n\n| Error Type | Recovery Action |\n|------------|----------------|\n| Dependency restore failed | Check network, verify lock file integrity |\n| Compilation errors | Log full error output, report as failed |\n| Missing build tool | Report required tool installation |\n| Timeout | Report timeout, suggest increasing limit |\n\n---\n\n## Critical Rules\n\n1. **Always restore dependencies first** - builds may fail without fresh dependencies\n2. **Use production\u002Frelease mode** - development builds may hide issues\n3. **Verify artifacts exist** - successful exit code is not sufficient\n4. **Report all projects** - include both successful and failed builds\n\n---\n\n## Definition of Done\n\n- [ ] All project types detected\n- [ ] Dependencies restored for each project\n- [ ] Build executed for each project\n- [ ] Artifacts verified to exist\n- [ ] Results returned to orchestrator\n\n---\n\n## Reference Files\n\n- Parent: `..\u002Fln-780-bootstrap-verifier\u002FSKILL.md`\n\n---\n\n**Version:** 2.0.0\n**Last Updated:** 2026-01-10\n",{"name":5,"license":15,"description":7},"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-781-build-verifier",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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-781-build-verifier",{"tool":43,"command":44},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-781-build-verifier",{"tool":46,"command":47},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-781-build-verifier","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-781-build-verifier\u002FSKILL.md",true,[],[52,74,112,139,165,193],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":23},"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",[],[59,60,61,62,63,64,65,66,67,68,69,70,71,72,73],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":93,"publishedAt":23},"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",[80,85,88],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":86,"categoryName":87,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[76,59,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":23},"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",[],[119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138],"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":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":23},"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",[],[146,147,148,149,150,151,152,153,154,155,156,157,102,158,159,160,161,162,163,164],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":23},"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",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000009","前端开发",[175,176,177,178,179,180,181,182,183,184,185,186,187,97,188,189,190,191,192,107],"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":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":209,"publishedAt":23},"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",[199,202,205,206],{"categoryNo":200,"categoryName":201,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":203,"categoryName":204,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":86,"categoryName":87,"taxonomyType":83,"taxonomyTypeDesc":84},{"categoryNo":207,"categoryName":208,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000036","内容创作者",[98,210,211,184,212,213,214,215,216,217,218,130,219,220,221,222,223,224,73,225],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]