[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGK6MJ3NBAE5759EK4FN21":3,"skill-same:01M6EGK6MJ3NBAE5759EK4FN21":70},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6EGK6MJ3NBAE5759EK4FN21","ln-652-transaction-correctness-auditor",null,"Checks transaction scope, missing rollback handling, long-held transactions, trigger\u002Fnotify interaction. Returns findings with severity, location, effort.","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-652-transaction-correctness-auditor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"transaction","ln 652 transaction correctness auditor","severity","transactions","Bash","rollback","returns","grep","read","location","notify","trigger","interaction","scope","long","missing","2026-11-10 10:12:30",false,"---\nname: ln-652-transaction-correctness-auditor\ndescription: \"Checks transaction scope, missing rollback handling, long-held transactions, trigger\u002Fnotify interaction. Returns findings with severity, location, effort.\"\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# Transaction Correctness Auditor (L3 Worker)\n\nSpecialized worker auditing database transaction patterns for correctness, scope, and trigger interaction.\n\n## Purpose & Scope\n\n- **Worker in ln-650 coordinator pipeline** - invoked by ln-650-persistence-performance-auditor\n- Audit **transaction correctness** (Priority: HIGH)\n- Check commit patterns, transaction boundaries, rollback handling, trigger\u002Fnotify semantics\n- Write structured findings to file with severity, location, effort, recommendations\n- Calculate compliance score (X\u002F10) for Transaction Correctness category\n\n## Inputs (from Coordinator)\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\nReceives `contextStore` with: `tech_stack`, `best_practices`, `db_config` (database type, ORM settings, trigger\u002Fnotify patterns), `codebase_root`, `output_dir`.\n\n**Domain-aware:** Supports `domain_mode` + `current_domain`.\n\n## Workflow\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Ftwo_layer_detection.md` for detection methodology.\n\n1) **Parse context from contextStore**\n   - Extract tech_stack, best_practices, db_config, output_dir\n   - Determine scan_path\n\n2) **Discover transaction infrastructure**\n   - Find migration files with triggers (`pg_notify`, `CREATE TRIGGER`, `NOTIFY`)\n   - Find session\u002Ftransaction configuration (`expire_on_commit`, `autocommit`, isolation level)\n   - Map trigger-affected tables\n\n3) **Scan codebase for violations**\n   - Trace UPDATE paths for trigger-affected tables\n   - Analyze transaction boundaries (begin\u002Fcommit scope)\n   - Check error handling around commits\n\n4) **Collect findings with severity, location, effort, recommendation**\n\n5) **Calculate score using penalty algorithm**\n\n6) **Write Report:** Build full markdown report in memory per `shared\u002Ftemplates\u002Faudit_worker_report_template.md`, write to `{output_dir}\u002F652-transaction-correctness.md` in single Write call\n\n7) **Return Summary:** Return minimal summary to coordinator (see Output Format)\n\n## Audit Rules (Priority: HIGH)\n\n### 1. Missing Intermediate Commits\n**What:** UPDATE without commit when DB trigger\u002FNOTIFY depends on transaction commit\n\n**Detection:**\n- **Step 1:** Find triggers in migrations:\n  - Grep for `pg_notify|NOTIFY|CREATE TRIGGER|CREATE OR REPLACE FUNCTION.*trigger` in `alembic\u002Fversions\u002F`, `migrations\u002F`\n  - Extract: trigger function name, table name, trigger event (INSERT\u002FUPDATE)\n- **Step 2:** Find code that UPDATEs trigger-affected tables:\n  - Grep for `repo.*update|session\\.execute.*update|\\.progress|\\.status` related to trigger tables\n- **Step 3:** Check for `commit()` between sequential updates:\n  - If multiple UPDATEs to trigger table occur in a loop\u002Fsequence without intermediate `commit()`, NOTIFY events are deferred until final commit\n  - Real-time progress tracking breaks without intermediate commits\n\n**Severity:**\n- **CRITICAL:** Missing commit for NOTIFY\u002FLISTEN-based real-time features (SSE, WebSocket)\n- **HIGH:** Missing commit for triggers that update materialized data\n\n**Exception:** Single atomic operation with no intermediate observable state → downgrade CRITICAL to MEDIUM. Transaction scope documented as intentional (ADR, architecture comment) → downgrade one level\n\n**Recommendation:**\n- Add `session.commit()` at progress milestones (throttled: every N%, every T seconds)\n- Or move real-time notifications out of DB triggers (Redis pub\u002Fsub, in-process events)\n\n**Effort:** S-M (add strategic commits or redesign notification path)\n\n### 2. Transaction Scope Too Wide\n**What:** Single transaction wraps unrelated operations, including slow external calls\n\n**Detection:**\n- Find `async with session.begin()` or explicit transaction blocks\n- Check if block contains external calls: `await httpx.`, `await aiohttp.`, `await requests.`, `await grpc.`\n- Check if block contains file I\u002FO: `open(`, `.read(`, `.write(`\n- Pattern: DB write + external API call + another DB write in same transaction\n\n**Severity:**\n- **HIGH:** External HTTP\u002FgRPC call inside transaction (holds DB connection during network latency)\n- **MEDIUM:** File I\u002FO inside transaction\n\n**Recommendation:** Split into separate transactions; use Saga\u002FOutbox pattern for cross-service consistency\n\n**Effort:** M-L (restructure transaction boundaries)\n\n### 3. Transaction Scope Too Narrow\n**What:** Logically atomic operations split across multiple commits\n\n**Detection:**\n- Multiple `session.commit()` calls for operations that should be atomic\n- Pattern: create parent entity, commit, create child entities, commit (should be single transaction)\n- Pattern: update status + create audit log in separate commits\n\n**Severity:**\n- **HIGH:** Parent-child creation in separate commits (orphan risk on failure)\n- **MEDIUM:** Related updates in separate commits (inconsistent state on failure)\n\n**Recommendation:** Wrap related operations in single transaction using `async with session.begin()` or unit-of-work pattern\n\n**Effort:** M (restructure commit boundaries)\n\n### 4. Missing Rollback Handling\n**What:** `session.commit()` without proper error handling and rollback\n\n**Detection:**\n- Find `session.commit()` not inside `try\u002Fexcept` block or context manager\n- Find `session.commit()` in `try` without `session.rollback()` in `except`\n- Pattern: bare `await session.commit()` in service methods\n- Exception: `async with session.begin()` auto-rollbacks (safe)\n\n**Severity:**\n- **MEDIUM:** Missing rollback (session left in broken state on failure)\n- **LOW:** Missing explicit rollback when using context manager (auto-handled)\n\n**Recommendation:** Use `async with session.begin()` (auto-rollback), or add explicit `try\u002Fexcept\u002Frollback` pattern\n\n**Effort:** S (wrap in context manager or add error handling)\n\n### 5. Long-Held Transaction\n**What:** Transaction open during slow\u002Fblocking operations\n\n**Detection:**\n- Measure scope: count lines between transaction start and commit\n- Flag if >50 lines of code between `begin()` and `commit()`\n- Flag if transaction contains `await` calls to external services (network latency)\n- Flag if transaction contains `time.sleep()` or `asyncio.sleep()`\n\n**Severity:**\n- **HIGH:** Transaction held during external API call (connection pool exhaustion risk)\n- **MEDIUM:** Transaction spans >50 lines (complex logic, high chance of lock contention)\n\n**Recommendation:** Minimize transaction scope; prepare data before opening transaction, commit immediately after DB operations\n\n**Effort:** M (restructure code to minimize transaction window)\n\n## Scoring Algorithm\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md` and `shared\u002Freferences\u002Faudit_scoring.md`.\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}\u002F652-transaction-correctness.md` with `category: \"Transaction Correctness\"` and checks: missing_intermediate_commits, scope_too_wide, scope_too_narrow, missing_rollback, long_held_transaction.\n\nReturn summary to coordinator:\n```\nReport written: docs\u002Fproject\u002F.audit\u002Fln-650\u002F{YYYY-MM-DD}\u002F652-transaction-correctness.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- **Trigger discovery first:** Always scan migrations for triggers\u002FNOTIFY before analyzing transaction patterns\n- **ORM-aware:** Check if ORM context manager auto-rollbacks (`async with session.begin()` is safe)\n- **Exclude test transactions:** Do not flag test fixtures with manual commit\u002Frollback\n- **Database-specific:** PostgreSQL NOTIFY semantics differ from MySQL event scheduler\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- scan_path determined\n- Trigger\u002FNOTIFY infrastructure discovered from migrations\n- All 5 checks completed:\n  - missing intermediate commits, scope too wide, scope too narrow, missing rollback, long-held\n- Findings collected with severity, location, effort, recommendation\n- Score calculated using penalty algorithm\n- Report written to `{output_dir}\u002F652-transaction-correctness.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-02-04\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# Transaction Correctness Auditor (L3 Worker)\n\nSpecialized worker auditing database transaction patterns for correctness, scope, and trigger interaction.\n\n## Purpose & Scope\n\n- **Worker in ln-650 coordinator pipeline** - invoked by ln-650-persistence-performance-auditor\n- Audit **transaction correctness** (Priority: HIGH)\n- Check commit patterns, transaction boundaries, rollback handling, trigger\u002Fnotify semantics\n- Write structured findings to file with severity, location, effort, recommendations\n- Calculate compliance score (X\u002F10) for Transaction Correctness category\n\n## Inputs (from Coordinator)\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\nReceives `contextStore` with: `tech_stack`, `best_practices`, `db_config` (database type, ORM settings, trigger\u002Fnotify patterns), `codebase_root`, `output_dir`.\n\n**Domain-aware:** Supports `domain_mode` + `current_domain`.\n\n## Workflow\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Ftwo_layer_detection.md` for detection methodology.\n\n1) **Parse context from contextStore**\n   - Extract tech_stack, best_practices, db_config, output_dir\n   - Determine scan_path\n\n2) **Discover transaction infrastructure**\n   - Find migration files with triggers (`pg_notify`, `CREATE TRIGGER`, `NOTIFY`)\n   - Find session\u002Ftransaction configuration (`expire_on_commit`, `autocommit`, isolation level)\n   - Map trigger-affected tables\n\n3) **Scan codebase for violations**\n   - Trace UPDATE paths for trigger-affected tables\n   - Analyze transaction boundaries (begin\u002Fcommit scope)\n   - Check error handling around commits\n\n4) **Collect findings with severity, location, effort, recommendation**\n\n5) **Calculate score using penalty algorithm**\n\n6) **Write Report:** Build full markdown report in memory per `shared\u002Ftemplates\u002Faudit_worker_report_template.md`, write to `{output_dir}\u002F652-transaction-correctness.md` in single Write call\n\n7) **Return Summary:** Return minimal summary to coordinator (see Output Format)\n\n## Audit Rules (Priority: HIGH)\n\n### 1. Missing Intermediate Commits\n**What:** UPDATE without commit when DB trigger\u002FNOTIFY depends on transaction commit\n\n**Detection:**\n- **Step 1:** Find triggers in migrations:\n  - Grep for `pg_notify|NOTIFY|CREATE TRIGGER|CREATE OR REPLACE FUNCTION.*trigger` in `alembic\u002Fversions\u002F`, `migrations\u002F`\n  - Extract: trigger function name, table name, trigger event (INSERT\u002FUPDATE)\n- **Step 2:** Find code that UPDATEs trigger-affected tables:\n  - Grep for `repo.*update|session\\.execute.*update|\\.progress|\\.status` related to trigger tables\n- **Step 3:** Check for `commit()` between sequential updates:\n  - If multiple UPDATEs to trigger table occur in a loop\u002Fsequence without intermediate `commit()`, NOTIFY events are deferred until final commit\n  - Real-time progress tracking breaks without intermediate commits\n\n**Severity:**\n- **CRITICAL:** Missing commit for NOTIFY\u002FLISTEN-based real-time features (SSE, WebSocket)\n- **HIGH:** Missing commit for triggers that update materialized data\n\n**Exception:** Single atomic operation with no intermediate observable state → downgrade CRITICAL to MEDIUM. Transaction scope documented as intentional (ADR, architecture comment) → downgrade one level\n\n**Recommendation:**\n- Add `session.commit()` at progress milestones (throttled: every N%, every T seconds)\n- Or move real-time notifications out of DB triggers (Redis pub\u002Fsub, in-process events)\n\n**Effort:** S-M (add strategic commits or redesign notification path)\n\n### 2. Transaction Scope Too Wide\n**What:** Single transaction wraps unrelated operations, including slow external calls\n\n**Detection:**\n- Find `async with session.begin()` or explicit transaction blocks\n- Check if block contains external calls: `await httpx.`, `await aiohttp.`, `await requests.`, `await grpc.`\n- Check if block contains file I\u002FO: `open(`, `.read(`, `.write(`\n- Pattern: DB write + external API call + another DB write in same transaction\n\n**Severity:**\n- **HIGH:** External HTTP\u002FgRPC call inside transaction (holds DB connection during network latency)\n- **MEDIUM:** File I\u002FO inside transaction\n\n**Recommendation:** Split into separate transactions; use Saga\u002FOutbox pattern for cross-service consistency\n\n**Effort:** M-L (restructure transaction boundaries)\n\n### 3. Transaction Scope Too Narrow\n**What:** Logically atomic operations split across multiple commits\n\n**Detection:**\n- Multiple `session.commit()` calls for operations that should be atomic\n- Pattern: create parent entity, commit, create child entities, commit (should be single transaction)\n- Pattern: update status + create audit log in separate commits\n\n**Severity:**\n- **HIGH:** Parent-child creation in separate commits (orphan risk on failure)\n- **MEDIUM:** Related updates in separate commits (inconsistent state on failure)\n\n**Recommendation:** Wrap related operations in single transaction using `async with session.begin()` or unit-of-work pattern\n\n**Effort:** M (restructure commit boundaries)\n\n### 4. Missing Rollback Handling\n**What:** `session.commit()` without proper error handling and rollback\n\n**Detection:**\n- Find `session.commit()` not inside `try\u002Fexcept` block or context manager\n- Find `session.commit()` in `try` without `session.rollback()` in `except`\n- Pattern: bare `await session.commit()` in service methods\n- Exception: `async with session.begin()` auto-rollbacks (safe)\n\n**Severity:**\n- **MEDIUM:** Missing rollback (session left in broken state on failure)\n- **LOW:** Missing explicit rollback when using context manager (auto-handled)\n\n**Recommendation:** Use `async with session.begin()` (auto-rollback), or add explicit `try\u002Fexcept\u002Frollback` pattern\n\n**Effort:** S (wrap in context manager or add error handling)\n\n### 5. Long-Held Transaction\n**What:** Transaction open during slow\u002Fblocking operations\n\n**Detection:**\n- Measure scope: count lines between transaction start and commit\n- Flag if >50 lines of code between `begin()` and `commit()`\n- Flag if transaction contains `await` calls to external services (network latency)\n- Flag if transaction contains `time.sleep()` or `asyncio.sleep()`\n\n**Severity:**\n- **HIGH:** Transaction held during external API call (connection pool exhaustion risk)\n- **MEDIUM:** Transaction spans >50 lines (complex logic, high chance of lock contention)\n\n**Recommendation:** Minimize transaction scope; prepare data before opening transaction, commit immediately after DB operations\n\n**Effort:** M (restructure code to minimize transaction window)\n\n## Scoring Algorithm\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md` and `shared\u002Freferences\u002Faudit_scoring.md`.\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}\u002F652-transaction-correctness.md` with `category: \"Transaction Correctness\"` and checks: missing_intermediate_commits, scope_too_wide, scope_too_narrow, missing_rollback, long_held_transaction.\n\nReturn summary to coordinator:\n```\nReport written: docs\u002Fproject\u002F.audit\u002Fln-650\u002F{YYYY-MM-DD}\u002F652-transaction-correctness.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- **Trigger discovery first:** Always scan migrations for triggers\u002FNOTIFY before analyzing transaction patterns\n- **ORM-aware:** Check if ORM context manager auto-rollbacks (`async with session.begin()` is safe)\n- **Exclude test transactions:** Do not flag test fixtures with manual commit\u002Frollback\n- **Database-specific:** PostgreSQL NOTIFY semantics differ from MySQL event scheduler\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- scan_path determined\n- Trigger\u002FNOTIFY infrastructure discovered from migrations\n- All 5 checks completed:\n  - missing intermediate commits, scope too wide, scope too narrow, missing rollback, long-held\n- Findings collected with severity, location, effort, recommendation\n- Score calculated using penalty algorithm\n- Report written to `{output_dir}\u002F652-transaction-correctness.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-02-04\n",{"name":5,"license":15,"description":7,"allowed-tools":40},"Read, Grep, Glob, Bash","main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-652-transaction-correctness-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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-652-transaction-correctness-auditor",{"tool":56,"command":57},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-652-transaction-correctness-auditor",{"tool":59,"command":60},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-652-transaction-correctness-auditor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-652-transaction-correctness-auditor\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"DESIGN.md","REFERENCE","参考文档",1533,"https:\u002F\u002Fgithub.com\u002FTorchiaHub\u002FSkills\u002Fblob\u002Fmaster\u002F01-Inbox\u002Fdownloads\u002Fbergside-design-skills\u002F20260516T145411Z\u002Fsource\u002Fskills\u002Fluxury\u002FDESIGN.md",[71,93,131,158,183,211],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":35},"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",[],[78,79,80,81,82,83,84,85,86,87,88,89,90,91,92],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":112,"publishedAt":35},"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",[99,104,107],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":105,"categoryName":106,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[95,78,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":35},"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":35},"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,167,168,169,170,171,172,173,174,175,176,121,177,178,179,180,30,181,182],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","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":35},"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":102,"taxonomyTypeDesc":103},"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":35},"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":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":221,"categoryName":222,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":105,"categoryName":106,"taxonomyType":102,"taxonomyTypeDesc":103},{"categoryNo":225,"categoryName":226,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000036","内容创作者",[117,228,229,202,230,231,232,233,23,234,27,149,235,236,237,238,239,240,92,241],"venue templates","research","NeurIPS","ICML","LaTeX","science","access","edit","proposals","Academic","requirements","formatting","journal","chi"]