[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGG82PFWM4P77H8CKD6BMY":3,"skill-same:01M6EGG82PFWM4P77H8CKD6BMY":64},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M6EGG82PFWM4P77H8CKD6BMY","ln-614-docs-fact-checker",null,"Extracts verifiable claims from ALL .md files (paths, versions, counts, configs, names, endpoints), verifies each against codebase, cross-checks between documents for contradictions.","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-614-docs-fact-checker\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"docs","fact checker","ln 614 docs fact checker","documents","Bash","grep","read","files","endpoints","paths","2026-11-10 10:12:30",false,"---\nname: ln-614-docs-fact-checker\ndescription: \"Extracts verifiable claims from ALL .md files (paths, versions, counts, configs, names, endpoints), verifies each against codebase, cross-checks between documents for contradictions.\"\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# Documentation Fact-Checker (L3 Worker)\n\nSpecialized worker that extracts verifiable claims from documentation and validates each against the actual codebase.\n\n## Purpose & Scope\n\n- **Worker in ln-610 coordinator pipeline** - invoked by ln-610-docs-auditor\n- Extract **all verifiable claims** from ALL `.md` files in project\n- Verify each claim against codebase (Grep\u002FGlob\u002FRead\u002FBash)\n- Detect **cross-document contradictions** (same fact stated differently)\n- Includes `docs\u002Freference\u002F`, `docs\u002Ftasks\u002F`, `tests\u002F` in scope\n- Single invocation (not per-document) — cross-doc checks require global view\n- Does NOT check scope alignment or structural quality\n\n## Inputs (from Coordinator)\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\nReceives `contextStore` with: `tech_stack`, `project_root`, `output_dir`.\n\n## Workflow\n\n### Phase 1: Parse Context\n\nExtract tech stack, project root, output_dir from contextStore.\n\n### Phase 2: Discover Documents\n\nGlob ALL `.md` files in project. Exclude:\n- `node_modules\u002F`, `.git\u002F`, `dist\u002F`, `build\u002F`\n- `docs\u002Fproject\u002F.audit\u002F` (audit output, not project docs)\n- `CHANGELOG.md` (historical by design)\n\n### Phase 3: Extract Claims (Layer 1)\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Ftwo_layer_detection.md` for detection methodology.\n\nFor each document, extract verifiable claims using Grep\u002Fregex patterns.\n\n**MANDATORY READ:** Load [references\u002Fclaim_extraction_rules.md](references\u002Fclaim_extraction_rules.md) for detailed extraction patterns per claim type.\n\n9 claim types:\n\n| # | Claim Type | What to Extract | Extraction Pattern |\n|---|-----------|-----------------|-------------------|\n| 1 | **File paths** | Paths to source files, dirs, configs | Backtick paths, link targets matching `src\u002F`, `lib\u002F`, `app\u002F`, `docs\u002F`, `config\u002F`, `tests\u002F` |\n| 2 | **Versions** | Package\u002Ftool\u002Fimage versions | Semver patterns near dependency\u002Fpackage\u002Fimage names |\n| 3 | **Counts\u002FStatistics** | Numeric claims about codebase | `\\d+ (modules|formats|endpoints|services|tables|parsers|files|workers)` |\n| 4 | **API endpoints** | HTTP method + path | `(GET|POST|PUT|DELETE|PATCH) \u002F[\\w\u002F{}:]+` |\n| 5 | **Config keys\u002Fenv vars** | Environment variables, config keys | `[A-Z][A-Z_]{2,}` in config context, `process.env.`, `os.environ` |\n| 6 | **CLI commands** | Shell commands | `npm run`, `python`, `docker`, `make` in backtick blocks |\n| 7 | **Function\u002Fclass names** | Code entity references | CamelCase\u002Fsnake_case in backticks or code context |\n| 8 | **Line number refs** | file:line patterns | `[\\w\u002F.]+:\\d+` patterns |\n| 9 | **Docker\u002Finfra claims** | Image tags, ports, service names | Image names with tags, port mappings in docker context |\n\nOutput per claim: `{doc_path, line, claim_type, claim_value, raw_context}`.\n\n### Phase 4: Verify Claims (Layer 2)\n\nFor each extracted claim, verify against codebase:\n\n| Claim Type | Verification Method | Finding Type |\n|------------|-------------------|--------------|\n| File paths | Glob or `ls` for existence | PATH_NOT_FOUND |\n| Versions | Grep package files (package.json, requirements.txt, docker-compose.yml), compare | VERSION_MISMATCH |\n| Counts | Glob\u002FGrep to count actual entities, compare with claimed number | COUNT_MISMATCH |\n| API endpoints | Grep route\u002Fcontroller definitions | ENDPOINT_NOT_FOUND |\n| Config keys | Grep in source for actual usage | CONFIG_NOT_FOUND |\n| CLI commands | Check package.json scripts, Makefile targets, binary existence | COMMAND_NOT_FOUND |\n| Function\u002Fclass | Grep in source for definition | ENTITY_NOT_FOUND |\n| Line numbers | Read file at line, check content matches claimed context | LINE_MISMATCH |\n| Docker\u002Finfra | Grep docker-compose.yml for image tags, ports | INFRA_MISMATCH |\n\n**False positive filtering (Layer 2 reasoning):**\n- Template placeholders (`{placeholder}`, `YOUR_*`, `\u003Cproject>`, `xxx`) — skip\n- Example\u002Fhypothetical paths (preceded by \"e.g.\", \"for example\", \"such as\") — skip\n- Future-tense claims (\"will add\", \"planned\", \"TODO\") — skip or LOW\n- Conditional claims (\"if using X, configure Y\") — verify only if X detected in tech_stack\n- External service paths (URLs, external repos) — skip\n- Paths in SCOPE\u002Fcomment HTML blocks describing other projects — skip\n- `.env.example` values — skip (expected to differ from actual)\n\n### Phase 5: Cross-Document Consistency\n\nCompare extracted claims across documents to find contradictions:\n\n| Check | Method | Finding Type |\n|-------|--------|--------------|\n| Same path, different locations | Group file path claims, check if all point to same real path | CROSS_DOC_PATH_CONFLICT |\n| Same entity, different version | Group version claims by entity name, compare values | CROSS_DOC_VERSION_CONFLICT |\n| Same metric, different count | Group count claims by subject, compare values | CROSS_DOC_COUNT_CONFLICT |\n| Endpoint in spec but not in guide | Compare endpoint claims across api_spec.md vs guides\u002Frunbook | CROSS_DOC_ENDPOINT_GAP |\n\nAlgorithm:\n```\nclaim_index = {}  # key: normalized(claim_type + entity), value: [{doc, line, value}]\nFOR claim IN all_verified_claims WHERE claim.verified == true:\n  key = normalize(claim.claim_type, claim.entity_name)\n  claim_index[key].append({doc: claim.doc_path, line: claim.line, value: claim.claim_value})\n\nFOR key, entries IN claim_index:\n  unique_values = set(entry.value for entry in entries)\n  IF len(unique_values) > 1:\n    CREATE finding(type=CROSS_DOC_*_CONFLICT, severity=HIGH,\n      location=entries[0].doc + \":\" + entries[0].line,\n      issue=\"'\" + key + \"' stated as '\" + val1 + \"' in \" + doc1 + \" but '\" + val2 + \"' in \" + doc2)\n```\n\n### Phase 6: Score & Report\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md` and `shared\u002Freferences\u002Faudit_scoring.md`.\n\nCalculate score using penalty formula. Write report.\n\n## Audit Categories (for Checks table)\n\n| ID | Check | What It Covers |\n|----|-------|---------------|\n| `path_claims` | File\u002FDirectory Paths | All path references verified against filesystem |\n| `version_claims` | Version Numbers | Package, tool, image versions against manifests |\n| `count_claims` | Counts & Statistics | Numeric assertions against actual counts |\n| `endpoint_claims` | API Endpoints | Route definitions against controllers\u002Frouters |\n| `config_claims` | Config & Env Vars | Environment variables, config keys against source |\n| `command_claims` | CLI Commands | Scripts, commands against package.json\u002FMakefile |\n| `entity_claims` | Code Entity Names | Functions, classes against source definitions |\n| `line_ref_claims` | Line Number References | file:line against actual file content |\n| `cross_doc` | Cross-Document Consistency | Same facts across documents agree |\n\n## Severity Mapping\n\n| Issue Type | Severity | Rationale |\n|------------|----------|-----------|\n| PATH_NOT_FOUND (critical file: CLAUDE.md, runbook, api_spec) | CRITICAL | Setup\u002Fonboarding fails |\n| PATH_NOT_FOUND (other docs) | HIGH | Misleading reference |\n| VERSION_MISMATCH (major version) | HIGH | Fundamentally wrong |\n| VERSION_MISMATCH (minor\u002Fpatch) | MEDIUM | Cosmetic drift |\n| COUNT_MISMATCH | MEDIUM | Misleading metric |\n| ENDPOINT_NOT_FOUND | HIGH | API consumers affected |\n| CONFIG_NOT_FOUND | HIGH | Deployment breaks |\n| COMMAND_NOT_FOUND | HIGH | Setup\u002FCI breaks |\n| ENTITY_NOT_FOUND | MEDIUM | Confusion |\n| LINE_MISMATCH | LOW | Minor inaccuracy |\n| INFRA_MISMATCH | HIGH | Docker\u002Fdeployment affected |\n| CROSS_DOC_*_CONFLICT | HIGH | Trust erosion, contradictory docs |\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}\u002F614-fact-checker.md` with `category: \"Fact Accuracy\"` and checks: path_claims, version_claims, count_claims, endpoint_claims, config_claims, command_claims, entity_claims, line_ref_claims, cross_doc.\n\nReturn summary to coordinator:\n```\nReport written: docs\u002Fproject\u002F.audit\u002Fln-610\u002F{YYYY-MM-DD}\u002F614-fact-checker.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 violations only; coordinator aggregates for user\n- **Code is truth:** When docs contradict code, document is wrong (unless code is a bug)\n- **Evidence required:** Every finding includes verification command used and result\n- **No false positives:** Better to miss an issue than report incorrectly. When uncertain, classify as LOW with note\n- **Location precision:** Always include `file:line` for programmatic navigation\n- **Broad scope:** Scan ALL .md files — do not skip docs\u002Freference\u002F, tests\u002F, or task docs\n- **Cross-doc matters:** Contradictions between documents erode trust more than single-doc errors\n- **Batch efficiently:** Extract all claims first, then verify in batches by type (all paths together, all versions together)\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- All `.md` files discovered (broad scope)\n- Claims extracted across 9 types\n- Each claim verified against codebase with evidence\n- Cross-document consistency checked\n- False positives filtered via Layer 2 reasoning\n- Score calculated using penalty algorithm\n- Report written to `{output_dir}\u002F614-fact-checker.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- **Detection methodology:** `shared\u002Freferences\u002Ftwo_layer_detection.md`\n- Claim extraction rules: [references\u002Fclaim_extraction_rules.md](references\u002Fclaim_extraction_rules.md)\n\n---\n**Version:** 1.0.0\n**Last Updated:** 2026-03-06\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# Documentation Fact-Checker (L3 Worker)\n\nSpecialized worker that extracts verifiable claims from documentation and validates each against the actual codebase.\n\n## Purpose & Scope\n\n- **Worker in ln-610 coordinator pipeline** - invoked by ln-610-docs-auditor\n- Extract **all verifiable claims** from ALL `.md` files in project\n- Verify each claim against codebase (Grep\u002FGlob\u002FRead\u002FBash)\n- Detect **cross-document contradictions** (same fact stated differently)\n- Includes `docs\u002Freference\u002F`, `docs\u002Ftasks\u002F`, `tests\u002F` in scope\n- Single invocation (not per-document) — cross-doc checks require global view\n- Does NOT check scope alignment or structural quality\n\n## Inputs (from Coordinator)\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\nReceives `contextStore` with: `tech_stack`, `project_root`, `output_dir`.\n\n## Workflow\n\n### Phase 1: Parse Context\n\nExtract tech stack, project root, output_dir from contextStore.\n\n### Phase 2: Discover Documents\n\nGlob ALL `.md` files in project. Exclude:\n- `node_modules\u002F`, `.git\u002F`, `dist\u002F`, `build\u002F`\n- `docs\u002Fproject\u002F.audit\u002F` (audit output, not project docs)\n- `CHANGELOG.md` (historical by design)\n\n### Phase 3: Extract Claims (Layer 1)\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Ftwo_layer_detection.md` for detection methodology.\n\nFor each document, extract verifiable claims using Grep\u002Fregex patterns.\n\n**MANDATORY READ:** Load [references\u002Fclaim_extraction_rules.md](references\u002Fclaim_extraction_rules.md) for detailed extraction patterns per claim type.\n\n9 claim types:\n\n| # | Claim Type | What to Extract | Extraction Pattern |\n|---|-----------|-----------------|-------------------|\n| 1 | **File paths** | Paths to source files, dirs, configs | Backtick paths, link targets matching `src\u002F`, `lib\u002F`, `app\u002F`, `docs\u002F`, `config\u002F`, `tests\u002F` |\n| 2 | **Versions** | Package\u002Ftool\u002Fimage versions | Semver patterns near dependency\u002Fpackage\u002Fimage names |\n| 3 | **Counts\u002FStatistics** | Numeric claims about codebase | `\\d+ (modules|formats|endpoints|services|tables|parsers|files|workers)` |\n| 4 | **API endpoints** | HTTP method + path | `(GET|POST|PUT|DELETE|PATCH) \u002F[\\w\u002F{}:]+` |\n| 5 | **Config keys\u002Fenv vars** | Environment variables, config keys | `[A-Z][A-Z_]{2,}` in config context, `process.env.`, `os.environ` |\n| 6 | **CLI commands** | Shell commands | `npm run`, `python`, `docker`, `make` in backtick blocks |\n| 7 | **Function\u002Fclass names** | Code entity references | CamelCase\u002Fsnake_case in backticks or code context |\n| 8 | **Line number refs** | file:line patterns | `[\\w\u002F.]+:\\d+` patterns |\n| 9 | **Docker\u002Finfra claims** | Image tags, ports, service names | Image names with tags, port mappings in docker context |\n\nOutput per claim: `{doc_path, line, claim_type, claim_value, raw_context}`.\n\n### Phase 4: Verify Claims (Layer 2)\n\nFor each extracted claim, verify against codebase:\n\n| Claim Type | Verification Method | Finding Type |\n|------------|-------------------|--------------|\n| File paths | Glob or `ls` for existence | PATH_NOT_FOUND |\n| Versions | Grep package files (package.json, requirements.txt, docker-compose.yml), compare | VERSION_MISMATCH |\n| Counts | Glob\u002FGrep to count actual entities, compare with claimed number | COUNT_MISMATCH |\n| API endpoints | Grep route\u002Fcontroller definitions | ENDPOINT_NOT_FOUND |\n| Config keys | Grep in source for actual usage | CONFIG_NOT_FOUND |\n| CLI commands | Check package.json scripts, Makefile targets, binary existence | COMMAND_NOT_FOUND |\n| Function\u002Fclass | Grep in source for definition | ENTITY_NOT_FOUND |\n| Line numbers | Read file at line, check content matches claimed context | LINE_MISMATCH |\n| Docker\u002Finfra | Grep docker-compose.yml for image tags, ports | INFRA_MISMATCH |\n\n**False positive filtering (Layer 2 reasoning):**\n- Template placeholders (`{placeholder}`, `YOUR_*`, `\u003Cproject>`, `xxx`) — skip\n- Example\u002Fhypothetical paths (preceded by \"e.g.\", \"for example\", \"such as\") — skip\n- Future-tense claims (\"will add\", \"planned\", \"TODO\") — skip or LOW\n- Conditional claims (\"if using X, configure Y\") — verify only if X detected in tech_stack\n- External service paths (URLs, external repos) — skip\n- Paths in SCOPE\u002Fcomment HTML blocks describing other projects — skip\n- `.env.example` values — skip (expected to differ from actual)\n\n### Phase 5: Cross-Document Consistency\n\nCompare extracted claims across documents to find contradictions:\n\n| Check | Method | Finding Type |\n|-------|--------|--------------|\n| Same path, different locations | Group file path claims, check if all point to same real path | CROSS_DOC_PATH_CONFLICT |\n| Same entity, different version | Group version claims by entity name, compare values | CROSS_DOC_VERSION_CONFLICT |\n| Same metric, different count | Group count claims by subject, compare values | CROSS_DOC_COUNT_CONFLICT |\n| Endpoint in spec but not in guide | Compare endpoint claims across api_spec.md vs guides\u002Frunbook | CROSS_DOC_ENDPOINT_GAP |\n\nAlgorithm:\n```\nclaim_index = {}  # key: normalized(claim_type + entity), value: [{doc, line, value}]\nFOR claim IN all_verified_claims WHERE claim.verified == true:\n  key = normalize(claim.claim_type, claim.entity_name)\n  claim_index[key].append({doc: claim.doc_path, line: claim.line, value: claim.claim_value})\n\nFOR key, entries IN claim_index:\n  unique_values = set(entry.value for entry in entries)\n  IF len(unique_values) > 1:\n    CREATE finding(type=CROSS_DOC_*_CONFLICT, severity=HIGH,\n      location=entries[0].doc + \":\" + entries[0].line,\n      issue=\"'\" + key + \"' stated as '\" + val1 + \"' in \" + doc1 + \" but '\" + val2 + \"' in \" + doc2)\n```\n\n### Phase 6: Score & Report\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md` and `shared\u002Freferences\u002Faudit_scoring.md`.\n\nCalculate score using penalty formula. Write report.\n\n## Audit Categories (for Checks table)\n\n| ID | Check | What It Covers |\n|----|-------|---------------|\n| `path_claims` | File\u002FDirectory Paths | All path references verified against filesystem |\n| `version_claims` | Version Numbers | Package, tool, image versions against manifests |\n| `count_claims` | Counts & Statistics | Numeric assertions against actual counts |\n| `endpoint_claims` | API Endpoints | Route definitions against controllers\u002Frouters |\n| `config_claims` | Config & Env Vars | Environment variables, config keys against source |\n| `command_claims` | CLI Commands | Scripts, commands against package.json\u002FMakefile |\n| `entity_claims` | Code Entity Names | Functions, classes against source definitions |\n| `line_ref_claims` | Line Number References | file:line against actual file content |\n| `cross_doc` | Cross-Document Consistency | Same facts across documents agree |\n\n## Severity Mapping\n\n| Issue Type | Severity | Rationale |\n|------------|----------|-----------|\n| PATH_NOT_FOUND (critical file: CLAUDE.md, runbook, api_spec) | CRITICAL | Setup\u002Fonboarding fails |\n| PATH_NOT_FOUND (other docs) | HIGH | Misleading reference |\n| VERSION_MISMATCH (major version) | HIGH | Fundamentally wrong |\n| VERSION_MISMATCH (minor\u002Fpatch) | MEDIUM | Cosmetic drift |\n| COUNT_MISMATCH | MEDIUM | Misleading metric |\n| ENDPOINT_NOT_FOUND | HIGH | API consumers affected |\n| CONFIG_NOT_FOUND | HIGH | Deployment breaks |\n| COMMAND_NOT_FOUND | HIGH | Setup\u002FCI breaks |\n| ENTITY_NOT_FOUND | MEDIUM | Confusion |\n| LINE_MISMATCH | LOW | Minor inaccuracy |\n| INFRA_MISMATCH | HIGH | Docker\u002Fdeployment affected |\n| CROSS_DOC_*_CONFLICT | HIGH | Trust erosion, contradictory docs |\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}\u002F614-fact-checker.md` with `category: \"Fact Accuracy\"` and checks: path_claims, version_claims, count_claims, endpoint_claims, config_claims, command_claims, entity_claims, line_ref_claims, cross_doc.\n\nReturn summary to coordinator:\n```\nReport written: docs\u002Fproject\u002F.audit\u002Fln-610\u002F{YYYY-MM-DD}\u002F614-fact-checker.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 violations only; coordinator aggregates for user\n- **Code is truth:** When docs contradict code, document is wrong (unless code is a bug)\n- **Evidence required:** Every finding includes verification command used and result\n- **No false positives:** Better to miss an issue than report incorrectly. When uncertain, classify as LOW with note\n- **Location precision:** Always include `file:line` for programmatic navigation\n- **Broad scope:** Scan ALL .md files — do not skip docs\u002Freference\u002F, tests\u002F, or task docs\n- **Cross-doc matters:** Contradictions between documents erode trust more than single-doc errors\n- **Batch efficiently:** Extract all claims first, then verify in batches by type (all paths together, all versions together)\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- All `.md` files discovered (broad scope)\n- Claims extracted across 9 types\n- Each claim verified against codebase with evidence\n- Cross-document consistency checked\n- False positives filtered via Layer 2 reasoning\n- Score calculated using penalty algorithm\n- Report written to `{output_dir}\u002F614-fact-checker.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- **Detection methodology:** `shared\u002Freferences\u002Ftwo_layer_detection.md`\n- Claim extraction rules: [references\u002Fclaim_extraction_rules.md](references\u002Fclaim_extraction_rules.md)\n\n---\n**Version:** 1.0.0\n**Last Updated:** 2026-03-06\n",{"name":5,"license":15,"description":7,"allowed-tools":34},"Read, Grep, Glob, Bash","main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-614-docs-fact-checker",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":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-614-docs-fact-checker",{"tool":50,"command":51},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-614-docs-fact-checker",{"tool":53,"command":54},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-614-docs-fact-checker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-614-docs-fact-checker\u002FSKILL.md",true,[58],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fclaim_extraction_rules.md","REFERENCE","参考文档",7830,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-614-docs-fact-checker\u002Freferences\u002Fclaim_extraction_rules.md",[65,87,125,152,178,206],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":29},"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",[],[72,73,74,75,76,77,78,79,80,81,82,83,84,85,86],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":106,"publishedAt":29},"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",[93,98,101],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[89,72,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":29},"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",[],[132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151],"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":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":29},"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",[],[159,160,161,162,163,164,165,166,167,168,169,170,115,171,172,173,174,175,176,177],"oracle","what if oracle","test","planning","ux","futures","risk","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":29},"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":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000009","前端开发",[188,189,190,191,192,193,194,195,196,197,198,199,200,110,201,202,203,204,205,120],"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":29},"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":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":216,"categoryName":217,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},{"categoryNo":220,"categoryName":221,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000036","内容创作者",[111,223,224,197,225,226,227,228,23,229,25,143,230,231,232,233,234,235,86,236],"venue templates","research","NeurIPS","ICML","LaTeX","science","access","edit","proposals","Academic","requirements","formatting","journal","chi"]