[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGJ2GFWPBZ9XWRX65V1EVX":3,"skill-same:01M6EGJ2GFWPBZ9XWRX65V1EVX":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":28,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6EGJ2GFWPBZ9XWRX65V1EVX","ln-636-manual-test-auditor",null,"Audits manual test scripts (tests\u002Fmanual\u002F) for harness adoption, golden file completeness, fail-fast, config sourcing, template compliance, idempotency.","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-636-manual-test-auditor\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"test","ln 636 manual test auditor","config","harness","file","fast","adoption","compliance","Bash","template","grep","read","tests","scripts","completeness","golden","2026-11-10 10:12:30",false,"---\nname: ln-636-manual-test-auditor\ndescription: \"Audits manual test scripts (tests\u002Fmanual\u002F) for harness adoption, golden file completeness, fail-fast, config sourcing, template compliance, idempotency.\"\nallowed-tools: Read, Grep, Glob, Bash\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# Manual Test Quality Auditor (L3 Worker)\n\nSpecialized worker auditing manual test scripts for quality and best-practice compliance.\n\n## Purpose & Scope\n\n- **Worker in ln-630 coordinator pipeline**\n- Audit **Manual Test Quality** (Category 7: Medium Priority)\n- Evaluate bash test scripts in `tests\u002Fmanual\u002F` against quality dimensions\n- Calculate compliance score (X\u002F10)\n\n## Inputs (from Coordinator)\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\nReceives `contextStore` with: `tech_stack`, `testFilesMetadata` (filtered to `type: \"manual\"`), `codebase_root`, `output_dir`.\n\nManual test metadata includes: `suite_dir`, `has_expected_dir`, `harness_sourced`.\n\n## Workflow\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Ftwo_layer_detection.md` for detection methodology.\n\n1) **Parse Context:** Extract manual test file list, output_dir, codebase_root from contextStore\n2) **Discover Infrastructure:** Detect shared infrastructure files:\n   - `tests\u002Fmanual\u002Fconfig.sh` — shared configuration\n   - `tests\u002Fmanual\u002Ftest_harness.sh` — shared test framework (if exists)\n   - `tests\u002Fmanual\u002Ftest-all.sh` — master runner\n   - `tests\u002Fmanual\u002FTEMPLATE-*.sh` — test templates (if exist)\n   - `tests\u002Fmanual\u002Fregenerate-golden.sh` — golden file regeneration (if exists)\n3) **Scan Scripts (Layer 1):** For each manual test script, check 7 quality dimensions (see Audit Rules)\n3b) **Context Analysis (Layer 2 -- MANDATORY):** For each candidate finding, ask:\n   - Is this a setup\u002Futility script (e.g., `00-setup\u002F*.sh`, `tools\u002F*.sh`)? Setup scripts have different requirements -- skip harness\u002Fgolden checks\n   - Is this a master runner (`test-all.sh`)? Master runners orchestrate, not test -- skip all checks except fail-fast\n   - Does the project not use a shared harness at all? If no `test_harness.sh` exists, harness adoption check is N\u002FA\n4) **Collect Findings:** Record violations with severity, location (file:line), effort, recommendation\n5) **Calculate Score:** Count violations by severity, calculate compliance score (X\u002F10)\n6) **Write Report:** Build full markdown report in memory per `shared\u002Ftemplates\u002Faudit_worker_report_template.md`, write to `{output_dir}\u002F636-manual-test-quality.md` in single Write call\n7) **Return Summary:** Return minimal summary to coordinator (see Output Format)\n\n## Audit Rules\n\n### 1. Harness Adoption\n\n**What:** Test script uses shared framework (`run_test`, `init_test_state`) instead of custom assertion logic\n\n**Detection:**\n- Grep for `run_test`, `init_test_state` in script\n- If absent AND script contains custom test loops\u002Fassertions → custom logic\n- If `test_harness.sh` does not exist in project → skip this check entirely\n\n**Severity:** **HIGH** (custom logic = maintenance burden, inconsistent reporting)\n\n**Recommendation:** Refactor to use shared `run_test` from test_harness.sh\n\n**Effort:** M\n\n### 2. Golden File Completeness\n\n**What:** Test suite has `expected\u002F` directory with reference files matching test scenarios\n\n**Detection:**\n- Check if suite directory has `expected\u002F` subdirectory\n- Compare: number of test scenarios (grep `run_test` calls) vs number of expected files\n- If test uses `diff` against expected files but expected dir is missing → finding\n\n**Layer 2:** Not all tests need golden files. Tests validating HTTP status codes, timing, or dynamic data may legitimately skip golden comparison → skip if test has no `diff` or comparison against files\n\n**Severity:** **HIGH** (no golden files = no regression detection for output correctness)\n\n**Recommendation:** Add expected\u002F directory with reference output files\n\n**Effort:** M\n\n### 3. Config Sourcing\n\n**What:** Script sources shared `config.sh` for consistent configuration\n\n**Detection:**\n- Grep for `source.*config.sh` or `. .*config.sh`\n- If absent → script manages its own BASE_URL, tokens, etc.\n\n**Layer 2:** If script is self-contained utility (e.g., `tools\u002F*.sh`) → skip\n\n**Severity:** **MEDIUM**\n\n**Recommendation:** Add `source \"$THIS_DIR\u002F..\u002Fconfig.sh\"` for shared configuration\n\n**Effort:** S\n\n### 4. Fail-Fast Compliance\n\n**What:** Script uses `set -e` and returns exit code 1 on failure\n\n**Detection:**\n- Grep for `set -e` (or `set -eo pipefail`)\n- Check that failure paths lead to non-zero exit (not swallowed by `|| true` everywhere)\n\n**Severity:** **HIGH** (silent failures mask broken tests)\n\n**Recommendation:** Add `set -e` at script start, ensure test failures propagate\n\n**Effort:** S\n\n### 5. Template Compliance\n\n**What:** Script follows project test templates (TEMPLATE-api-endpoint.sh, TEMPLATE-document-format.sh)\n\n**Detection:**\n- If TEMPLATE files exist in `tests\u002Fmanual\u002F`, check structural alignment:\n  - Header comment block with description, ACs tested, prerequisites\n  - Standard variable naming (`THIS_DIR`, `EXPECTED_DIR`)\n  - Standard setup pattern (`source config.sh`, `check_jq`, `setup_auth`)\n- If NO templates exist in project → skip this check entirely\n\n**Layer 2:** Older scripts written before templates may diverge. Flag as MEDIUM, not HIGH\n\n**Severity:** **MEDIUM**\n\n**Recommendation:** Align script structure with project TEMPLATE files\n\n**Effort:** M\n\n### 6. Idempotency\n\n**What:** Script can be rerun safely without side effects from previous runs\n\n**Detection:**\n- Grep for cleanup patterns: `trap.*EXIT`, `rm -f`, `cleanup` functions\n- Check for temp file creation without cleanup\n- Check for hardcoded resource names that would conflict on rerun (e.g., creating user with fixed email without checking existence)\n\n**Layer 2:** Scripts that only READ data (GET requests, queries) are inherently idempotent → skip\n\n**Severity:** **MEDIUM**\n\n**Recommendation:** Add cleanup trap or use unique identifiers per run\n\n**Effort:** S-M\n\n### 7. Documentation\n\n**What:** Test suite directory has README.md explaining purpose and prerequisites\n\n**Detection:**\n- Check if suite directory (`NN-feature\u002F`) contains README.md\n- If missing → finding\n\n**Layer 2:** Setup directories (`00-setup\u002F`) and utility directories (`tools\u002F`) may not need README → skip\n\n**Severity:** **LOW**\n\n**Recommendation:** Add README.md with test purpose, prerequisites, usage\n\n**Effort:** S\n\n## Scoring Algorithm\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md` and `shared\u002Freferences\u002Faudit_scoring.md`.\n\n**Severity mapping:**\n- Missing harness adoption (when harness exists), No golden files (when expected-based), No fail-fast → HIGH\n- Missing config sourcing, Template divergence, No idempotency → MEDIUM\n- Missing README → LOW\n\n## Output Format\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md` and `shared\u002Ftemplates\u002Faudit_worker_report_template.md`.\n\nWrite report to `{output_dir}\u002F636-manual-test-quality.md` with `category: \"Manual Test Quality\"` and checks: harness_adoption, golden_file_completeness, config_sourcing, fail_fast_compliance, template_compliance, idempotency, documentation.\n\nReturn summary to coordinator:\n```\nReport written: docs\u002Fproject\u002F.audit\u002Fln-630\u002F{YYYY-MM-DD}\u002F636-manual-test-quality.md\nScore: X.X\u002F10 | Issues: N (C:N H:N M:N L:N)\n```\n\n## Critical Rules\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\n- **Do not auto-fix:** Report only\n- **Effort realism:** S = \u003C1h, M = 1-4h, L = >4h\n- **Skip when empty:** If no `tests\u002Fmanual\u002F` directory exists, return score 10\u002F10 with zero findings\n- **Exclude non-test files:** Skip `config.sh`, `test_harness.sh`, `test-all.sh`, `regenerate-golden.sh`, `TEMPLATE-*.sh`, files in `tools\u002F`, `results\u002F`, `test-runs\u002F`\n- **Context-aware:** Setup scripts (`00-setup\u002F`) have relaxed requirements (no golden files, no harness needed)\n\n## Definition of Done\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\n- contextStore parsed successfully (including output_dir)\n- Manual test infrastructure discovered (config.sh, harness, templates)\n- All 7 checks completed per test script\n- Layer 2 context analysis applied (setup\u002Futility exclusions)\n- Findings collected with severity, location, effort, recommendation\n- Score calculated using penalty algorithm\n- Report written to `{output_dir}\u002F636-manual-test-quality.md` (atomic single Write call)\n- Summary returned to coordinator\n\n## Reference Files\n\n- **Audit output schema:** `shared\u002Freferences\u002Faudit_output_schema.md`\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# Manual Test Quality Auditor (L3 Worker)\n\nSpecialized worker auditing manual test scripts for quality and best-practice compliance.\n\n## Purpose & Scope\n\n- **Worker in ln-630 coordinator pipeline**\n- Audit **Manual Test Quality** (Category 7: Medium Priority)\n- Evaluate bash test scripts in `tests\u002Fmanual\u002F` against quality dimensions\n- Calculate compliance score (X\u002F10)\n\n## Inputs (from Coordinator)\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\nReceives `contextStore` with: `tech_stack`, `testFilesMetadata` (filtered to `type: \"manual\"`), `codebase_root`, `output_dir`.\n\nManual test metadata includes: `suite_dir`, `has_expected_dir`, `harness_sourced`.\n\n## Workflow\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Ftwo_layer_detection.md` for detection methodology.\n\n1) **Parse Context:** Extract manual test file list, output_dir, codebase_root from contextStore\n2) **Discover Infrastructure:** Detect shared infrastructure files:\n   - `tests\u002Fmanual\u002Fconfig.sh` — shared configuration\n   - `tests\u002Fmanual\u002Ftest_harness.sh` — shared test framework (if exists)\n   - `tests\u002Fmanual\u002Ftest-all.sh` — master runner\n   - `tests\u002Fmanual\u002FTEMPLATE-*.sh` — test templates (if exist)\n   - `tests\u002Fmanual\u002Fregenerate-golden.sh` — golden file regeneration (if exists)\n3) **Scan Scripts (Layer 1):** For each manual test script, check 7 quality dimensions (see Audit Rules)\n3b) **Context Analysis (Layer 2 -- MANDATORY):** For each candidate finding, ask:\n   - Is this a setup\u002Futility script (e.g., `00-setup\u002F*.sh`, `tools\u002F*.sh`)? Setup scripts have different requirements -- skip harness\u002Fgolden checks\n   - Is this a master runner (`test-all.sh`)? Master runners orchestrate, not test -- skip all checks except fail-fast\n   - Does the project not use a shared harness at all? If no `test_harness.sh` exists, harness adoption check is N\u002FA\n4) **Collect Findings:** Record violations with severity, location (file:line), effort, recommendation\n5) **Calculate Score:** Count violations by severity, calculate compliance score (X\u002F10)\n6) **Write Report:** Build full markdown report in memory per `shared\u002Ftemplates\u002Faudit_worker_report_template.md`, write to `{output_dir}\u002F636-manual-test-quality.md` in single Write call\n7) **Return Summary:** Return minimal summary to coordinator (see Output Format)\n\n## Audit Rules\n\n### 1. Harness Adoption\n\n**What:** Test script uses shared framework (`run_test`, `init_test_state`) instead of custom assertion logic\n\n**Detection:**\n- Grep for `run_test`, `init_test_state` in script\n- If absent AND script contains custom test loops\u002Fassertions → custom logic\n- If `test_harness.sh` does not exist in project → skip this check entirely\n\n**Severity:** **HIGH** (custom logic = maintenance burden, inconsistent reporting)\n\n**Recommendation:** Refactor to use shared `run_test` from test_harness.sh\n\n**Effort:** M\n\n### 2. Golden File Completeness\n\n**What:** Test suite has `expected\u002F` directory with reference files matching test scenarios\n\n**Detection:**\n- Check if suite directory has `expected\u002F` subdirectory\n- Compare: number of test scenarios (grep `run_test` calls) vs number of expected files\n- If test uses `diff` against expected files but expected dir is missing → finding\n\n**Layer 2:** Not all tests need golden files. Tests validating HTTP status codes, timing, or dynamic data may legitimately skip golden comparison → skip if test has no `diff` or comparison against files\n\n**Severity:** **HIGH** (no golden files = no regression detection for output correctness)\n\n**Recommendation:** Add expected\u002F directory with reference output files\n\n**Effort:** M\n\n### 3. Config Sourcing\n\n**What:** Script sources shared `config.sh` for consistent configuration\n\n**Detection:**\n- Grep for `source.*config.sh` or `. .*config.sh`\n- If absent → script manages its own BASE_URL, tokens, etc.\n\n**Layer 2:** If script is self-contained utility (e.g., `tools\u002F*.sh`) → skip\n\n**Severity:** **MEDIUM**\n\n**Recommendation:** Add `source \"$THIS_DIR\u002F..\u002Fconfig.sh\"` for shared configuration\n\n**Effort:** S\n\n### 4. Fail-Fast Compliance\n\n**What:** Script uses `set -e` and returns exit code 1 on failure\n\n**Detection:**\n- Grep for `set -e` (or `set -eo pipefail`)\n- Check that failure paths lead to non-zero exit (not swallowed by `|| true` everywhere)\n\n**Severity:** **HIGH** (silent failures mask broken tests)\n\n**Recommendation:** Add `set -e` at script start, ensure test failures propagate\n\n**Effort:** S\n\n### 5. Template Compliance\n\n**What:** Script follows project test templates (TEMPLATE-api-endpoint.sh, TEMPLATE-document-format.sh)\n\n**Detection:**\n- If TEMPLATE files exist in `tests\u002Fmanual\u002F`, check structural alignment:\n  - Header comment block with description, ACs tested, prerequisites\n  - Standard variable naming (`THIS_DIR`, `EXPECTED_DIR`)\n  - Standard setup pattern (`source config.sh`, `check_jq`, `setup_auth`)\n- If NO templates exist in project → skip this check entirely\n\n**Layer 2:** Older scripts written before templates may diverge. Flag as MEDIUM, not HIGH\n\n**Severity:** **MEDIUM**\n\n**Recommendation:** Align script structure with project TEMPLATE files\n\n**Effort:** M\n\n### 6. Idempotency\n\n**What:** Script can be rerun safely without side effects from previous runs\n\n**Detection:**\n- Grep for cleanup patterns: `trap.*EXIT`, `rm -f`, `cleanup` functions\n- Check for temp file creation without cleanup\n- Check for hardcoded resource names that would conflict on rerun (e.g., creating user with fixed email without checking existence)\n\n**Layer 2:** Scripts that only READ data (GET requests, queries) are inherently idempotent → skip\n\n**Severity:** **MEDIUM**\n\n**Recommendation:** Add cleanup trap or use unique identifiers per run\n\n**Effort:** S-M\n\n### 7. Documentation\n\n**What:** Test suite directory has README.md explaining purpose and prerequisites\n\n**Detection:**\n- Check if suite directory (`NN-feature\u002F`) contains README.md\n- If missing → finding\n\n**Layer 2:** Setup directories (`00-setup\u002F`) and utility directories (`tools\u002F`) may not need README → skip\n\n**Severity:** **LOW**\n\n**Recommendation:** Add README.md with test purpose, prerequisites, usage\n\n**Effort:** S\n\n## Scoring Algorithm\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md` and `shared\u002Freferences\u002Faudit_scoring.md`.\n\n**Severity mapping:**\n- Missing harness adoption (when harness exists), No golden files (when expected-based), No fail-fast → HIGH\n- Missing config sourcing, Template divergence, No idempotency → MEDIUM\n- Missing README → LOW\n\n## Output Format\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md` and `shared\u002Ftemplates\u002Faudit_worker_report_template.md`.\n\nWrite report to `{output_dir}\u002F636-manual-test-quality.md` with `category: \"Manual Test Quality\"` and checks: harness_adoption, golden_file_completeness, config_sourcing, fail_fast_compliance, template_compliance, idempotency, documentation.\n\nReturn summary to coordinator:\n```\nReport written: docs\u002Fproject\u002F.audit\u002Fln-630\u002F{YYYY-MM-DD}\u002F636-manual-test-quality.md\nScore: X.X\u002F10 | Issues: N (C:N H:N M:N L:N)\n```\n\n## Critical Rules\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\n- **Do not auto-fix:** Report only\n- **Effort realism:** S = \u003C1h, M = 1-4h, L = >4h\n- **Skip when empty:** If no `tests\u002Fmanual\u002F` directory exists, return score 10\u002F10 with zero findings\n- **Exclude non-test files:** Skip `config.sh`, `test_harness.sh`, `test-all.sh`, `regenerate-golden.sh`, `TEMPLATE-*.sh`, files in `tools\u002F`, `results\u002F`, `test-runs\u002F`\n- **Context-aware:** Setup scripts (`00-setup\u002F`) have relaxed requirements (no golden files, no harness needed)\n\n## Definition of Done\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\n- contextStore parsed successfully (including output_dir)\n- Manual test infrastructure discovered (config.sh, harness, templates)\n- All 7 checks completed per test script\n- Layer 2 context analysis applied (setup\u002Futility exclusions)\n- Findings collected with severity, location, effort, recommendation\n- Score calculated using penalty algorithm\n- Report written to `{output_dir}\u002F636-manual-test-quality.md` (atomic single Write call)\n- Summary returned to coordinator\n\n## Reference Files\n\n- **Audit output schema:** `shared\u002Freferences\u002Faudit_output_schema.md`\n\n---\n**Version:** 1.0.0\n**Last Updated:** 2026-03-13\n",{"name":5,"license":15,"description":7,"allowed-tools":50},"Read, Grep, Glob, Bash","main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-636-manual-test-auditor",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-636-manual-test-auditor",{"tool":66,"command":67},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-636-manual-test-auditor",{"tool":69,"command":70},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-636-manual-test-auditor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-636-manual-test-auditor\u002FSKILL.md",true,[],[75,97,131,158,183,211],{"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":45},"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":112,"publishedAt":45},"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":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[99,82,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":45},"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",[],[138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157],"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":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":45},"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",[],[165,166,29,167,168,169,170,171,172,173,174,175,121,176,177,178,179,180,181,182],"oracle","what if oracle","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":192,"publishedAt":45},"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",[189],{"categoryNo":190,"categoryName":191,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[193,194,195,196,197,198,199,200,201,202,203,204,205,116,206,207,208,209,210,126],"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":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":227,"publishedAt":45},"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",[217,220,223,224],{"categoryNo":218,"categoryName":219,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":221,"categoryName":222,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":225,"categoryName":226,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[117,228,229,202,230,231,232,233,37,234,40,149,235,236,237,238,239,240,96,241],"venue templates","research","NeurIPS","ICML","LaTeX","science","access","edit","proposals","Academic","requirements","formatting","journal","chi"]