[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGF7GB2X35SMZFS2SDWR3R":3,"skill-same:01M6EGF7GB2X35SMZFS2SDWR3R":110},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6EGF7GB2X35SMZFS2SDWR3R","ln-514-test-log-analyzer",null,"Analyzes application logs: classifies errors, checks log quality\u002Fformat, maps stack traces to source, recommends fixes.","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-514-test-log-analyzer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33],"test","log","log analyzer","ln 514 test log analyzer","logs","stack","format","quality","maps","application","2026-11-10 10:12:30",false,"---\nname: ln-514-test-log-analyzer\ndescription: \"Analyzes application logs: classifies errors, checks log quality\u002Fformat, maps stack traces to source, recommends fixes.\"\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# Test Log Analyzer\n\nTwo-layer analysis of application logs. Python script handles collection and quantitative analysis; AI handles classification, quality assessment, and fix recommendations.\n\n## Inputs\n\nNo required inputs. Runs in current project directory, auto-detects log sources.\n\nOptional `args` — caller instructions (natural language): time window, expected errors, test context. Example: `\"review logs for last 30min, auth 401 errors expected from negative tests\"`.\n\n## Purpose & Scope\n- Analyze application logs (after test runs, during development, or on demand)\n- Classify errors into 4 categories: Real Bug, Test Artifact, Expected Behavior, Operational Warning\n- Assess log quality: noisiness, completeness, level correctness, format, structured logging\n- Map stack traces to source files; provide fix recommendations\n- Report findings for quality verdict (only Real Bugs block)\n- **No status changes or task creation** — report only\n\n## When to Use\n- Analyze application logs in any project (default: last 1h)\n- After test runs to classify errors and assess log quality\n- Can be invoked with context instructions: `Skill(skill: \"ln-514-test-log-analyzer\", args: \"review last 30min, 401 errors expected\")`\n\n## Workflow\n\n### Phase 0: Parse Instructions\n\nIf `args` provided — extract: time window (default: 1h), expected errors list, test context.\nIf no `args` — use defaults (last 1h, no expected errors).\n\n### Phase 1: Log Source Detection and Script Execution\n\n**MANDATORY READ:** Load `docs\u002Fproject\u002Finfrastructure.md`, `docs\u002Fproject\u002Frunbook.md`\n\n1) Check if `scripts\u002Fanalyze_test_logs.py` exists in target project. If missing, copy from `references\u002Fanalyze_test_logs.py`.\n2) Detect log source mode (auto-detection priority: docker → file → loki):\n\n| Mode | Detection | Source |\n|------|-----------|--------|\n| `docker` | `docker compose ps` returns running containers | `docker compose logs --since {window}` |\n| `file` | `.log` files exist, or `tests\u002Fmanual\u002Fresults\u002F` has output | File paths from infrastructure.md or `*.log` glob |\n| `loki` | `LOKI_URL` env var or `tools_config.md` observability section | Loki HTTP query_range API |\n\n3) Run script: `python scripts\u002Fanalyze_test_logs.py --mode {detected} [options]`\n4) If no log sources found → return `NO_LOG_SOURCES` status, skip to Phase 5.\n\n### Phase 2: 4-Category Error Classification\n\nClassify each error group from script JSON output:\n\n| Category | Action | Criteria |\n|----------|--------|----------|\n| **Real Bug** | Fix | Unexpected crash, data loss, broken pipeline |\n| **Test Artifact** | Skip | From test scripts, deliberate error-path validation |\n| **Expected Behavior** | Skip | Rate limiting, input validation, auth failures from invalid tokens |\n| **Operational Warning** | Monitor | Clock drift, resource pressure, temporary unavailability |\n\n**Test artifact detection heuristics:**\n- Test name contains: `invalid`, `error`, `fail`, `reject`, `unauthorized`, `forbidden`, `not_found`, `bad_request`, `timeout`\n- Test asserts non-2xx status codes (4xx, 5xx)\n- Test uses `pytest.raises`, `expect(...).rejects`, `assertThrows`, `should.throw`\n- Errors correlate with test execution timestamps from regression test output\n- Patterns matching `tests\u002Fmanual\u002F` scripts\n\n**Error taxonomy per** `references\u002Ferror_taxonomy.md` **(9 categories: CRASH, TIMEOUT, AUTH, DB, NETWORK, VALIDATION, CONFIG, RESOURCE, DEPRECATION).**\n\n### Phase 3: Log Quality Assessment\n\n**MANDATORY READ:** Load `references\u002Ferror_taxonomy.md` (per-level criteria table + level correctness reference)\n\n**Step 1: Detect configured log level.** Check in order:\n1. `LOG_LEVEL` \u002F `LOGLEVEL` env var (`.env`, `docker-compose.yml`, `infrastructure.md`)\n2. Framework config: Python `logging.conf` \u002F Django `LOGGING` \u002F Node `LOG_LEVEL`\n3. Default: assume `INFO` if not detected\n\nConfigured level determines WHICH levels appear in logs, but each level has its own noise threshold regardless.\n\n**Step 2: Assess 6 quality dimensions:**\n\n| Dimension | What to Check | Signal |\n|-----------|---------------|--------|\n| **Noisiness** | Per-level noise thresholds from `error_taxonomy.md` section 4: TRACE (zero in prod), DEBUG (>50% monopoly), INFO (>30%), WARNING (>1% of total), ERROR (>0.1% of total) | `NOISY: {level} template \"{msg}\" at {ratio}%` |\n| **Completeness & Traceability** | Critical operations missing log entries + traceability gaps (see table below) | `MISSING: No log for {operation}` \u002F `TRACEABILITY_GAP: {type} in {file}:{line}` |\n| **Level correctness** | Per-level criteria from `error_taxonomy.md` section 4: content, anti-patterns, library rule | `WRONG_LEVEL: should be {level}` |\n| **Structured logging** | Missing trace_id\u002Frequest_id\u002Fuser context; unstructured plaintext | `UNSTRUCTURED: lacks {field}` |\n| **Sensitivity** | PII\u002Fsecrets\u002Ftokens\u002Fpasswords in log messages | `SENSITIVE: {type} exposure` |\n| **Context richness** | Errors without actionable context (order_id, user_id, operation) | `LOW_CONTEXT: lacks context` |\n\n**Traceability gap detection** — scan source code for operations without INFO-level logging:\n\n| Operation Type | Expected Log | Where to Add |\n|---------------|-------------|--------------|\n| Incoming request handling | Request received + response status | Entry\u002Fexit of route handler |\n| External API call | Request sent + response status + duration | Before\u002Fafter HTTP client call |\n| DB write (INSERT\u002FUPDATE\u002FDELETE) | Operation + affected entity + count | Before\u002Fafter ORM\u002Fquery call |\n| Auth decision | Result (allow\u002Fdeny) + reason | After auth check |\n| State transition | Old state → new state + trigger | At transition point |\n| Background job | Start + complete\u002Ffail + duration | Entry\u002Fexit of job handler |\n| File\u002Fresource operation | Open\u002Fclose + path + size | At I\u002FO operation |\n\n**Log Format Quality** (10-criterion checklist per `references\u002Flog_analysis_output_format.md`):\n\n| # | Criterion | Check |\n|---|-----------|-------|\n| 1 | Dual format | JSON in prod, readable in dev |\n| 2 | Timestamp | Consistent, timezone-aware |\n| 3 | Level field | Present, uppercase |\n| 4 | Trace\u002FCorrelation ID | Present in every entry, async-safe |\n| 5 | Service name | Identifies source service |\n| 6 | Source location | module:line + function |\n| 7 | Extra context | Structured fields, not string interpolation |\n| 8 | PII redaction | Passwords, API keys, emails handled |\n| 9 | Noise suppression | Duplicate filters, third-party suppressed |\n| 10 | Parseability | Dev: pipe-delimited; prod: valid JSON per line |\n\nScore: passed criteria \u002F 10.\n\n### Phase 4: Stack Trace Mapping + Fix Recommendations\n\nFor each Real Bug:\n1) Extract stack trace frames; identify origin frame (first frame in project code, not in node_modules\u002Fsite-packages)\n2) Map to source file:line\n3) Generate fix recommendation: what to change, where, effort estimate (S\u002FM\u002FL)\n\n**Prioritize using Sentry-inspired dimensions:**\n- High-volume (occurrence count), Post-test regression (new errors), High-impact path (auth\u002Fpayment\u002FDB), Correlated traces (trace_id across services)\n\n### Phase 5: Generate Report\n\n**MANDATORY READ:** Load `references\u002Flog_analysis_output_format.md`\n\nOutput report to chat with header `## Test Log Analysis`. Include:\n- Signals table (Real Bugs count, Test Artifacts filtered, Log Noise status, Log Format score, Log Quality score)\n- Real Bugs table (priority, category, error, source, fix recommendation)\n- Filtered table (category, count, examples)\n- Log Quality Issues table (dimension, service, issue, recommendation)\n- Noise Report table (count, ratio, service, level, template, action)\n- Machine-readable block `\u003C!-- LOG-ANALYSIS-DATA ... -->` for programmatic consumption\n\n### Phase 6: Meta-Analysis\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Fmeta_analysis_protocol.md`\n\nSkill type: `execution-worker`. Run after all phases complete.\n\n## Verdict Contribution\n\nQuality coordinator normalization matrix component:\n\n| Status | Maps To | Penalty |\n|--------|---------|---------|\n| CLEAN | -- | 0 |\n| WARNINGS_ONLY | -- | 0 |\n| REAL_BUGS_FOUND | FAIL | -20 |\n| SKIPPED \u002F NO_LOG_SOURCES | ignored | 0 |\n\nLog quality\u002Fformat issues are INFORMATIONAL — do not affect quality verdict. Only Real Bugs block.\n\n## Critical Rules\n- No status changes or task creation; report only.\n- Test Artifacts and Expected Behavior are ALWAYS filtered — never count as bugs.\n- Log quality issues are advisory — inform, don't block.\n- Script must handle gracefully: no Docker, no log files, no Loki → `NO_LOG_SOURCES`.\n- Language preservation in comments (EN\u002FRU).\n\n## Definition of Done\n- Script deployed to target project `scripts\u002F` (or already exists).\n- Log source detected and script executed (or NO_LOG_SOURCES returned).\n- Errors classified into 4 categories; Real Bugs identified.\n- Log quality assessed (6 dimensions + 10-criterion format checklist).\n- Stack traces mapped to source files for Real Bugs.\n- Report output to chat with signals table + machine-readable block.\n\n## Reference Files\n- **Error taxonomy:** `references\u002Ferror_taxonomy.md`\n- **Output format:** `references\u002Flog_analysis_output_format.md`\n- **Analysis script:** `references\u002Fanalyze_test_logs.py`\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# Test Log Analyzer\n\nTwo-layer analysis of application logs. Python script handles collection and quantitative analysis; AI handles classification, quality assessment, and fix recommendations.\n\n## Inputs\n\nNo required inputs. Runs in current project directory, auto-detects log sources.\n\nOptional `args` — caller instructions (natural language): time window, expected errors, test context. Example: `\"review logs for last 30min, auth 401 errors expected from negative tests\"`.\n\n## Purpose & Scope\n- Analyze application logs (after test runs, during development, or on demand)\n- Classify errors into 4 categories: Real Bug, Test Artifact, Expected Behavior, Operational Warning\n- Assess log quality: noisiness, completeness, level correctness, format, structured logging\n- Map stack traces to source files; provide fix recommendations\n- Report findings for quality verdict (only Real Bugs block)\n- **No status changes or task creation** — report only\n\n## When to Use\n- Analyze application logs in any project (default: last 1h)\n- After test runs to classify errors and assess log quality\n- Can be invoked with context instructions: `Skill(skill: \"ln-514-test-log-analyzer\", args: \"review last 30min, 401 errors expected\")`\n\n## Workflow\n\n### Phase 0: Parse Instructions\n\nIf `args` provided — extract: time window (default: 1h), expected errors list, test context.\nIf no `args` — use defaults (last 1h, no expected errors).\n\n### Phase 1: Log Source Detection and Script Execution\n\n**MANDATORY READ:** Load `docs\u002Fproject\u002Finfrastructure.md`, `docs\u002Fproject\u002Frunbook.md`\n\n1) Check if `scripts\u002Fanalyze_test_logs.py` exists in target project. If missing, copy from `references\u002Fanalyze_test_logs.py`.\n2) Detect log source mode (auto-detection priority: docker → file → loki):\n\n| Mode | Detection | Source |\n|------|-----------|--------|\n| `docker` | `docker compose ps` returns running containers | `docker compose logs --since {window}` |\n| `file` | `.log` files exist, or `tests\u002Fmanual\u002Fresults\u002F` has output | File paths from infrastructure.md or `*.log` glob |\n| `loki` | `LOKI_URL` env var or `tools_config.md` observability section | Loki HTTP query_range API |\n\n3) Run script: `python scripts\u002Fanalyze_test_logs.py --mode {detected} [options]`\n4) If no log sources found → return `NO_LOG_SOURCES` status, skip to Phase 5.\n\n### Phase 2: 4-Category Error Classification\n\nClassify each error group from script JSON output:\n\n| Category | Action | Criteria |\n|----------|--------|----------|\n| **Real Bug** | Fix | Unexpected crash, data loss, broken pipeline |\n| **Test Artifact** | Skip | From test scripts, deliberate error-path validation |\n| **Expected Behavior** | Skip | Rate limiting, input validation, auth failures from invalid tokens |\n| **Operational Warning** | Monitor | Clock drift, resource pressure, temporary unavailability |\n\n**Test artifact detection heuristics:**\n- Test name contains: `invalid`, `error`, `fail`, `reject`, `unauthorized`, `forbidden`, `not_found`, `bad_request`, `timeout`\n- Test asserts non-2xx status codes (4xx, 5xx)\n- Test uses `pytest.raises`, `expect(...).rejects`, `assertThrows`, `should.throw`\n- Errors correlate with test execution timestamps from regression test output\n- Patterns matching `tests\u002Fmanual\u002F` scripts\n\n**Error taxonomy per** `references\u002Ferror_taxonomy.md` **(9 categories: CRASH, TIMEOUT, AUTH, DB, NETWORK, VALIDATION, CONFIG, RESOURCE, DEPRECATION).**\n\n### Phase 3: Log Quality Assessment\n\n**MANDATORY READ:** Load `references\u002Ferror_taxonomy.md` (per-level criteria table + level correctness reference)\n\n**Step 1: Detect configured log level.** Check in order:\n1. `LOG_LEVEL` \u002F `LOGLEVEL` env var (`.env`, `docker-compose.yml`, `infrastructure.md`)\n2. Framework config: Python `logging.conf` \u002F Django `LOGGING` \u002F Node `LOG_LEVEL`\n3. Default: assume `INFO` if not detected\n\nConfigured level determines WHICH levels appear in logs, but each level has its own noise threshold regardless.\n\n**Step 2: Assess 6 quality dimensions:**\n\n| Dimension | What to Check | Signal |\n|-----------|---------------|--------|\n| **Noisiness** | Per-level noise thresholds from `error_taxonomy.md` section 4: TRACE (zero in prod), DEBUG (>50% monopoly), INFO (>30%), WARNING (>1% of total), ERROR (>0.1% of total) | `NOISY: {level} template \"{msg}\" at {ratio}%` |\n| **Completeness & Traceability** | Critical operations missing log entries + traceability gaps (see table below) | `MISSING: No log for {operation}` \u002F `TRACEABILITY_GAP: {type} in {file}:{line}` |\n| **Level correctness** | Per-level criteria from `error_taxonomy.md` section 4: content, anti-patterns, library rule | `WRONG_LEVEL: should be {level}` |\n| **Structured logging** | Missing trace_id\u002Frequest_id\u002Fuser context; unstructured plaintext | `UNSTRUCTURED: lacks {field}` |\n| **Sensitivity** | PII\u002Fsecrets\u002Ftokens\u002Fpasswords in log messages | `SENSITIVE: {type} exposure` |\n| **Context richness** | Errors without actionable context (order_id, user_id, operation) | `LOW_CONTEXT: lacks context` |\n\n**Traceability gap detection** — scan source code for operations without INFO-level logging:\n\n| Operation Type | Expected Log | Where to Add |\n|---------------|-------------|--------------|\n| Incoming request handling | Request received + response status | Entry\u002Fexit of route handler |\n| External API call | Request sent + response status + duration | Before\u002Fafter HTTP client call |\n| DB write (INSERT\u002FUPDATE\u002FDELETE) | Operation + affected entity + count | Before\u002Fafter ORM\u002Fquery call |\n| Auth decision | Result (allow\u002Fdeny) + reason | After auth check |\n| State transition | Old state → new state + trigger | At transition point |\n| Background job | Start + complete\u002Ffail + duration | Entry\u002Fexit of job handler |\n| File\u002Fresource operation | Open\u002Fclose + path + size | At I\u002FO operation |\n\n**Log Format Quality** (10-criterion checklist per `references\u002Flog_analysis_output_format.md`):\n\n| # | Criterion | Check |\n|---|-----------|-------|\n| 1 | Dual format | JSON in prod, readable in dev |\n| 2 | Timestamp | Consistent, timezone-aware |\n| 3 | Level field | Present, uppercase |\n| 4 | Trace\u002FCorrelation ID | Present in every entry, async-safe |\n| 5 | Service name | Identifies source service |\n| 6 | Source location | module:line + function |\n| 7 | Extra context | Structured fields, not string interpolation |\n| 8 | PII redaction | Passwords, API keys, emails handled |\n| 9 | Noise suppression | Duplicate filters, third-party suppressed |\n| 10 | Parseability | Dev: pipe-delimited; prod: valid JSON per line |\n\nScore: passed criteria \u002F 10.\n\n### Phase 4: Stack Trace Mapping + Fix Recommendations\n\nFor each Real Bug:\n1) Extract stack trace frames; identify origin frame (first frame in project code, not in node_modules\u002Fsite-packages)\n2) Map to source file:line\n3) Generate fix recommendation: what to change, where, effort estimate (S\u002FM\u002FL)\n\n**Prioritize using Sentry-inspired dimensions:**\n- High-volume (occurrence count), Post-test regression (new errors), High-impact path (auth\u002Fpayment\u002FDB), Correlated traces (trace_id across services)\n\n### Phase 5: Generate Report\n\n**MANDATORY READ:** Load `references\u002Flog_analysis_output_format.md`\n\nOutput report to chat with header `## Test Log Analysis`. Include:\n- Signals table (Real Bugs count, Test Artifacts filtered, Log Noise status, Log Format score, Log Quality score)\n- Real Bugs table (priority, category, error, source, fix recommendation)\n- Filtered table (category, count, examples)\n- Log Quality Issues table (dimension, service, issue, recommendation)\n- Noise Report table (count, ratio, service, level, template, action)\n- Machine-readable block `\u003C!-- LOG-ANALYSIS-DATA ... -->` for programmatic consumption\n\n### Phase 6: Meta-Analysis\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Fmeta_analysis_protocol.md`\n\nSkill type: `execution-worker`. Run after all phases complete.\n\n## Verdict Contribution\n\nQuality coordinator normalization matrix component:\n\n| Status | Maps To | Penalty |\n|--------|---------|---------|\n| CLEAN | -- | 0 |\n| WARNINGS_ONLY | -- | 0 |\n| REAL_BUGS_FOUND | FAIL | -20 |\n| SKIPPED \u002F NO_LOG_SOURCES | ignored | 0 |\n\nLog quality\u002Fformat issues are INFORMATIONAL — do not affect quality verdict. Only Real Bugs block.\n\n## Critical Rules\n- No status changes or task creation; report only.\n- Test Artifacts and Expected Behavior are ALWAYS filtered — never count as bugs.\n- Log quality issues are advisory — inform, don't block.\n- Script must handle gracefully: no Docker, no log files, no Loki → `NO_LOG_SOURCES`.\n- Language preservation in comments (EN\u002FRU).\n\n## Definition of Done\n- Script deployed to target project `scripts\u002F` (or already exists).\n- Log source detected and script executed (or NO_LOG_SOURCES returned).\n- Errors classified into 4 categories; Real Bugs identified.\n- Log quality assessed (6 dimensions + 10-criterion format checklist).\n- Stack traces mapped to source files for Real Bugs.\n- Report output to chat with signals table + machine-readable block.\n\n## Reference Files\n- **Error taxonomy:** `references\u002Ferror_taxonomy.md`\n- **Output format:** `references\u002Flog_analysis_output_format.md`\n- **Analysis script:** `references\u002Fanalyze_test_logs.py`\n\n---\n**Version:** 1.0.0\n**Last Updated:** 2026-03-13\n",{"name":5,"license":15,"description":7},"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-514-test-log-analyzer",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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-514-test-log-analyzer",{"tool":54,"command":55},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-514-test-log-analyzer",{"tool":57,"command":58},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-514-test-log-analyzer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-514-test-log-analyzer\u002FSKILL.md",true,[62,68,74,78,82,86,90,94,98,102,106],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fanalyze_test_logs.py","SCRIPT","脚本",20258,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-514-test-log-analyzer\u002Freferences\u002Fanalyze_test_logs.py",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fcomplex-analysis.md","REFERENCE","参考文档",16197,"https:\u002F\u002Fgithub.com\u002Faresbit\u002FAutoAgent\u002Fblob\u002Fmaster\u002Fpackages\u002Fopencc\u002Fsrc\u002Ftools\u002FAnalysisMasterTool\u002Fassets\u002Freferences\u002Fcomplex-analysis.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Ferror_taxonomy.md",7539,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-514-test-log-analyzer\u002Freferences\u002Ferror_taxonomy.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Ffunctional-analysis.md",15576,"https:\u002F\u002Fgithub.com\u002Faresbit\u002FAutoAgent\u002Fblob\u002Fmaster\u002Fpackages\u002Fopencc\u002Fsrc\u002Ftools\u002FAnalysisMasterTool\u002Fassets\u002Freferences\u002Ffunctional-analysis.md",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fgeometric-analysis.md",16174,"https:\u002F\u002Fgithub.com\u002Faresbit\u002FAutoAgent\u002Fblob\u002Fmaster\u002Fpackages\u002Fopencc\u002Fsrc\u002Ftools\u002FAnalysisMasterTool\u002Fassets\u002Freferences\u002Fgeometric-analysis.md",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fharmonic-fourier.md",14273,"https:\u002F\u002Fgithub.com\u002Faresbit\u002FAutoAgent\u002Fblob\u002Fmaster\u002Fpackages\u002Fopencc\u002Fsrc\u002Ftools\u002FAnalysisMasterTool\u002Fassets\u002Freferences\u002Fharmonic-fourier.md",{"path":91,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Flog_analysis_output_format.md",5772,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-514-test-log-analyzer\u002Freferences\u002Flog_analysis_output_format.md",{"path":95,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fmeasure-integration.md",7791,"https:\u002F\u002Fgithub.com\u002Faresbit\u002FAutoAgent\u002Fblob\u002Fmaster\u002Fpackages\u002Fopencc\u002Fsrc\u002Ftools\u002FAnalysisMasterTool\u002Fassets\u002Freferences\u002Fmeasure-integration.md",{"path":99,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Foptimal-transport.md",12931,"https:\u002F\u002Fgithub.com\u002Faresbit\u002FAutoAgent\u002Fblob\u002Fmaster\u002Fpackages\u002Fopencc\u002Fsrc\u002Ftools\u002FAnalysisMasterTool\u002Fassets\u002Freferences\u002Foptimal-transport.md",{"path":103,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fspectral-theory.md",12313,"https:\u002F\u002Fgithub.com\u002Faresbit\u002FAutoAgent\u002Fblob\u002Fmaster\u002Fpackages\u002Fopencc\u002Fsrc\u002Ftools\u002FAnalysisMasterTool\u002Fassets\u002Freferences\u002Fspectral-theory.md",{"path":107,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fvariational-methods.md",9820,"https:\u002F\u002Fgithub.com\u002Faresbit\u002FAutoAgent\u002Fblob\u002Fmaster\u002Fpackages\u002Fopencc\u002Fsrc\u002Ftools\u002FAnalysisMasterTool\u002Fassets\u002Freferences\u002Fvariational-methods.md",[111,133,169,196,221,249],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":34},"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",[],[118,119,120,121,122,123,124,125,126,127,128,129,130,131,132],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":150,"publishedAt":34},"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",[139,142,145],{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":143,"categoryName":144,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[135,118,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":34},"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",[],[176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195],"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":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":34},"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",[],[203,204,24,205,206,207,208,209,210,211,212,213,159,214,215,216,217,218,219,220],"oracle","what if oracle","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":230,"publishedAt":34},"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",[227],{"categoryNo":228,"categoryName":229,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[231,232,233,234,235,236,237,238,239,240,241,242,243,154,244,245,246,247,248,164],"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":250,"name":251,"nameZh":6,"description":252,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":253,"categories":254,"keywords":265,"publishedAt":34},"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",[255,258,261,262],{"categoryNo":256,"categoryName":257,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":259,"categoryName":260,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":143,"categoryName":144,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":263,"categoryName":264,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000036","内容创作者",[155,266,267,240,268,269,270,271,272,273,274,187,275,276,277,278,279,280,132,281],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]