[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGHM6WPD5KT6SZRWQKN9QF":3,"skill-same:01M6EGHM6WPD5KT6SZRWQKN9QF":69},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6EGHM6WPD5KT6SZRWQKN9QF","ln-632-test-e2e-priority-auditor",null,"E2E Critical Coverage audit worker. Validates E2E coverage for critical paths (Money 20+, Security 20+, Data 15+). Pure risk-based - no pyramid percentages.","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-632-test-e2e-priority-auditor\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"test","e2e","ln 632 test e2e priority auditor","security","audit","data","risk","risk-based","Bash","grep","read","coverage","money","worker","critical","paths","2026-11-10 10:12:30",false,"---\nname: ln-632-test-e2e-priority-auditor\ndescription: E2E Critical Coverage audit worker. Validates E2E coverage for critical paths (Money 20+, Security 20+, Data 15+). Pure risk-based - no pyramid percentages.\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# E2E Critical Coverage Auditor (L3 Worker)\n\nSpecialized worker auditing E2E test coverage for critical paths (risk-based).\n\n## Purpose & Scope\n\n- **Worker in ln-630 coordinator pipeline**\n- Audit **E2E Critical Coverage** (Category 2: High Priority)\n- Validate E2E coverage for critical paths (Money\u002FSecurity\u002FData Priority ≥20)\n- Validate E2E coverage for core user journeys (Priority 15-19)\n- Identify wasteful E2E tests (Usefulness Score \u003C15)\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`, `codebase_root`, `output_dir`.\n\n## Workflow\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Ftwo_layer_detection.md` for detection methodology.\n\n1) **Parse Context:** Extract tech stack, critical paths, user journeys, test file list, output_dir from contextStore\n2) **Identify Critical Paths (Layer 1):** Scan codebase for critical paths (Money, Security, Data)\n2b) **Context Analysis (Layer 2 — MANDATORY):** For each candidate critical path, ask:\n   - Is this a helper function called from an already-E2E-tested path? → **downgrade to MEDIUM**\n   - Is this already covered by integration test with real assertions? → **downgrade to LOW**\n   - Is keyword match a false positive (e.g., `calculateDiscount()` is pure math, already unit-tested)? → **skip**\n3) **Identify Core Journeys:** Identify core user journeys (multi-step flows)\n4) **Check Critical Path Coverage:** Check E2E coverage for critical paths (Priority >=20)\n5) **Check Journey Coverage:** Check E2E coverage for user journeys (Priority 15-19)\n6) **Validate E2E Tests:** Validate existing E2E tests (Usefulness Score >=15)\n7) **Collect Findings:** Record each violation with severity, location (file:line), effort estimate (S\u002FM\u002FL), recommendation\n8) **Calculate Score:** Count violations by severity, calculate compliance score (X\u002F10)\n9) **Write Report:** Build full markdown report in memory per `shared\u002Ftemplates\u002Faudit_worker_report_template.md`, write to `{output_dir}\u002F632-e2e-priority.md` in single Write call\n10) **Return Summary:** Return minimal summary to coordinator (see Output Format)\n\n## Audit Rules\n\n### 1. Critical Path E2E Coverage\n\n**Rule:** Every critical path MUST have E2E test\n\n**Critical Paths (Priority ≥20):**\n- **Money** (Priority 25): Payment processing, refunds, discounts, tax calculation\n- **Security** (Priority 25): Login, auth, password reset, token refresh, permissions\n- **Data Export** (Priority 20): Reports, CSV generation, data migration\n\n**Detection:**\n1. Scan codebase for critical keywords: `payment`, `refund`, `login`, `auth`, `export`\n2. Extract critical functions\u002Fendpoints\n3. Check if E2E test exists for each critical path\n4. Missing E2E for Priority ≥20 → CRITICAL severity\n\n**Severity:**\n- **CRITICAL:** No E2E for Priority 25 (Money, Security)\n- **HIGH:** No E2E for Priority 20 (Data Export)\n- **Downgrade when:** Function is helper called from already-E2E-tested path → MEDIUM. Already covered by integration test → LOW\n\n**Recommendation:** Add E2E tests for critical paths immediately\n\n**Effort:** M\n\n### 2. Core User Journey E2E Coverage\n\n**Rule:** Multi-step critical flows MUST have E2E test\n\n**Core Journeys (Priority 15-19):**\n- Registration → Email verification → First login (Priority 16)\n- Product search → Add to cart → Checkout (Priority 18)\n- File upload → Processing → Download result (Priority 15)\n\n**Detection:**\n1. Identify multi-step flows in routes\u002Fcontrollers\n2. Check if end-to-end journey test exists\n3. Missing E2E for Priority ≥15 → HIGH severity\n\n**Severity:**\n- **HIGH:** Missing E2E for core user journey (Priority ≥15)\n- **MEDIUM:** Incomplete journey coverage (only partial steps tested)\n\n**Recommendation:** Add end-to-end journey tests\n\n**Effort:** M-L\n\n### 3. E2E Test Usefulness Validation\n\n**Rule:** Every E2E test MUST justify Priority ≥15\n\n**Check:**\nFor each E2E test, calculate Usefulness Score = Impact × Probability\n- If Score \u003C15 → Flag as \"Potentially wasteful E2E\"\n- Recommendation: Convert to Integration or Unit test (cheaper)\n\n**Example:**\n- E2E test for \"API returns 200 OK\" → Impact 2, Probability 1 → Score 2 → **WASTEFUL**\n- E2E test for \"Payment with discount calculates correctly\" → Impact 5, Probability 5 → Score 25 → **VALUABLE**\n\n**Severity:**\n- **MEDIUM:** E2E test with Usefulness Score \u003C15\n- **LOW:** E2E test with Score 10-14 (review needed)\n\n**Recommendation:** Convert low-value E2E to Integration\u002FUnit or remove\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 E2E for Priority 25 (Money, Security) → CRITICAL\n- Missing E2E for Priority 20 (Data Export) → HIGH\n- Missing E2E for Priority 15-19 (Core Journeys) → HIGH\n- Wasteful E2E (Score \u003C15) → MEDIUM\n- Incomplete journey coverage → 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}\u002F632-e2e-priority.md` with `category: \"E2E Critical Coverage\"` and checks: critical_path_coverage, user_journey_coverage, e2e_usefulness_validation.\n\nReturn summary to coordinator:\n```\nReport written: docs\u002Fproject\u002F.audit\u002Fln-630\u002F{YYYY-MM-DD}\u002F632-e2e-priority.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- **Risk-based only:** Prioritize by business impact (Money > Security > Data), not by code coverage percentage\n- **Effort realism:** S = \u003C1h, M = 1-4h, L = >4h\n- **Usefulness Score threshold:** Only flag E2E tests with Score \u003C15 as wasteful\n- **No pyramid enforcement:** Do not recommend E2E\u002FIntegration\u002FUnit ratios — focus on critical path coverage\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- Critical paths identified (Money, Security, Data) with Priority scores\n- All 3 checks completed (critical path coverage, user journey coverage, E2E usefulness validation)\n- Findings collected with severity, location, effort, recommendation\n- Score calculated using penalty algorithm\n- Report written to `{output_dir}\u002F632-e2e-priority.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:** 3.0.0\n**Last Updated:** 2025-12-23\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# E2E Critical Coverage Auditor (L3 Worker)\n\nSpecialized worker auditing E2E test coverage for critical paths (risk-based).\n\n## Purpose & Scope\n\n- **Worker in ln-630 coordinator pipeline**\n- Audit **E2E Critical Coverage** (Category 2: High Priority)\n- Validate E2E coverage for critical paths (Money\u002FSecurity\u002FData Priority ≥20)\n- Validate E2E coverage for core user journeys (Priority 15-19)\n- Identify wasteful E2E tests (Usefulness Score \u003C15)\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`, `codebase_root`, `output_dir`.\n\n## Workflow\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Ftwo_layer_detection.md` for detection methodology.\n\n1) **Parse Context:** Extract tech stack, critical paths, user journeys, test file list, output_dir from contextStore\n2) **Identify Critical Paths (Layer 1):** Scan codebase for critical paths (Money, Security, Data)\n2b) **Context Analysis (Layer 2 — MANDATORY):** For each candidate critical path, ask:\n   - Is this a helper function called from an already-E2E-tested path? → **downgrade to MEDIUM**\n   - Is this already covered by integration test with real assertions? → **downgrade to LOW**\n   - Is keyword match a false positive (e.g., `calculateDiscount()` is pure math, already unit-tested)? → **skip**\n3) **Identify Core Journeys:** Identify core user journeys (multi-step flows)\n4) **Check Critical Path Coverage:** Check E2E coverage for critical paths (Priority >=20)\n5) **Check Journey Coverage:** Check E2E coverage for user journeys (Priority 15-19)\n6) **Validate E2E Tests:** Validate existing E2E tests (Usefulness Score >=15)\n7) **Collect Findings:** Record each violation with severity, location (file:line), effort estimate (S\u002FM\u002FL), recommendation\n8) **Calculate Score:** Count violations by severity, calculate compliance score (X\u002F10)\n9) **Write Report:** Build full markdown report in memory per `shared\u002Ftemplates\u002Faudit_worker_report_template.md`, write to `{output_dir}\u002F632-e2e-priority.md` in single Write call\n10) **Return Summary:** Return minimal summary to coordinator (see Output Format)\n\n## Audit Rules\n\n### 1. Critical Path E2E Coverage\n\n**Rule:** Every critical path MUST have E2E test\n\n**Critical Paths (Priority ≥20):**\n- **Money** (Priority 25): Payment processing, refunds, discounts, tax calculation\n- **Security** (Priority 25): Login, auth, password reset, token refresh, permissions\n- **Data Export** (Priority 20): Reports, CSV generation, data migration\n\n**Detection:**\n1. Scan codebase for critical keywords: `payment`, `refund`, `login`, `auth`, `export`\n2. Extract critical functions\u002Fendpoints\n3. Check if E2E test exists for each critical path\n4. Missing E2E for Priority ≥20 → CRITICAL severity\n\n**Severity:**\n- **CRITICAL:** No E2E for Priority 25 (Money, Security)\n- **HIGH:** No E2E for Priority 20 (Data Export)\n- **Downgrade when:** Function is helper called from already-E2E-tested path → MEDIUM. Already covered by integration test → LOW\n\n**Recommendation:** Add E2E tests for critical paths immediately\n\n**Effort:** M\n\n### 2. Core User Journey E2E Coverage\n\n**Rule:** Multi-step critical flows MUST have E2E test\n\n**Core Journeys (Priority 15-19):**\n- Registration → Email verification → First login (Priority 16)\n- Product search → Add to cart → Checkout (Priority 18)\n- File upload → Processing → Download result (Priority 15)\n\n**Detection:**\n1. Identify multi-step flows in routes\u002Fcontrollers\n2. Check if end-to-end journey test exists\n3. Missing E2E for Priority ≥15 → HIGH severity\n\n**Severity:**\n- **HIGH:** Missing E2E for core user journey (Priority ≥15)\n- **MEDIUM:** Incomplete journey coverage (only partial steps tested)\n\n**Recommendation:** Add end-to-end journey tests\n\n**Effort:** M-L\n\n### 3. E2E Test Usefulness Validation\n\n**Rule:** Every E2E test MUST justify Priority ≥15\n\n**Check:**\nFor each E2E test, calculate Usefulness Score = Impact × Probability\n- If Score \u003C15 → Flag as \"Potentially wasteful E2E\"\n- Recommendation: Convert to Integration or Unit test (cheaper)\n\n**Example:**\n- E2E test for \"API returns 200 OK\" → Impact 2, Probability 1 → Score 2 → **WASTEFUL**\n- E2E test for \"Payment with discount calculates correctly\" → Impact 5, Probability 5 → Score 25 → **VALUABLE**\n\n**Severity:**\n- **MEDIUM:** E2E test with Usefulness Score \u003C15\n- **LOW:** E2E test with Score 10-14 (review needed)\n\n**Recommendation:** Convert low-value E2E to Integration\u002FUnit or remove\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 E2E for Priority 25 (Money, Security) → CRITICAL\n- Missing E2E for Priority 20 (Data Export) → HIGH\n- Missing E2E for Priority 15-19 (Core Journeys) → HIGH\n- Wasteful E2E (Score \u003C15) → MEDIUM\n- Incomplete journey coverage → 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}\u002F632-e2e-priority.md` with `category: \"E2E Critical Coverage\"` and checks: critical_path_coverage, user_journey_coverage, e2e_usefulness_validation.\n\nReturn summary to coordinator:\n```\nReport written: docs\u002Fproject\u002F.audit\u002Fln-630\u002F{YYYY-MM-DD}\u002F632-e2e-priority.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- **Risk-based only:** Prioritize by business impact (Money > Security > Data), not by code coverage percentage\n- **Effort realism:** S = \u003C1h, M = 1-4h, L = >4h\n- **Usefulness Score threshold:** Only flag E2E tests with Score \u003C15 as wasteful\n- **No pyramid enforcement:** Do not recommend E2E\u002FIntegration\u002FUnit ratios — focus on critical path coverage\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- Critical paths identified (Money, Security, Data) with Priority scores\n- All 3 checks completed (critical path coverage, user journey coverage, E2E usefulness validation)\n- Findings collected with severity, location, effort, recommendation\n- Score calculated using penalty algorithm\n- Report written to `{output_dir}\u002F632-e2e-priority.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:** 3.0.0\n**Last Updated:** 2025-12-23\n",{"name":5,"license":15,"description":7,"allowed-tools":45},"Read, Grep, Glob, Bash","main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-632-test-e2e-priority-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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-632-test-e2e-priority-auditor",{"tool":61,"command":62},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-632-test-e2e-priority-auditor",{"tool":64,"command":65},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-632-test-e2e-priority-auditor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-632-test-e2e-priority-auditor\u002FSKILL.md",true,[],[70,92,127,154,178,206],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":40},"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",[],[77,78,79,80,81,82,83,84,85,86,87,88,89,90,91],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":109,"publishedAt":40},"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",[98,101,104],{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[94,77,110,111,112,29,113,114,115,116,117,118,119,120,121,122,123,124,125,126],"automation","window management","monitoring","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":40},"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",[],[134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153],"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":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":40},"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",[],[161,162,24,163,164,165,30,166,167,168,169,170,117,171,172,173,174,175,176,177],"oracle","what if oracle","planning","ux","futures","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":187,"publishedAt":40},"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",[184],{"categoryNo":185,"categoryName":186,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[188,189,190,191,192,193,194,195,196,197,198,199,200,29,201,202,203,204,205,122],"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":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":222,"publishedAt":40},"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",[212,215,218,219],{"categoryNo":213,"categoryName":214,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":216,"categoryName":217,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":220,"categoryName":221,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000036","内容创作者",[113,223,224,197,225,226,227,228,32,229,34,145,230,231,232,233,234,235,91,236],"venue templates","research","NeurIPS","ICML","LaTeX","science","access","edit","proposals","Academic","requirements","formatting","journal","chi"]