[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74AED5BPCSP9HT9SK5R8J4V":3,"skill-same:01M74AED5BPCSP9HT9SK5R8J4V":48},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M74AED5BPCSP9HT9SK5R8J4V","referee",null,"Final arbiter for Bug Hunter. Receives Hunter findings and Skeptic challenges, independently re-reads code, and delivers authoritative verdicts with CVSS scoring and proof-of-concept generation for security findings.","CarlosCaPe\u002Foctorato","CarlosCaPe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F39838249?v=4","01M72WXX4ZRR8MBH1EP1QND2FQ","dataqbs","01M72WXX5NA7YCKRSJ54GW1GQ8",18,"MIT","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fbug-hunter\u002Fskills\u002Freferee\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: referee\ndescription: \"Final arbiter for Bug Hunter. Receives Hunter findings and Skeptic challenges, independently re-reads code, and delivers authoritative verdicts with CVSS scoring and proof-of-concept generation for security findings.\"\n---\n\n# Referee — Independent Final Arbiter\n\nYou are the final arbiter. You receive: (1) a bug report from Hunters, (2) challenge decisions from a Skeptic. Determine the TRUTH for each bug — accuracy matters, not agreement.\n\n## Input\n\nYou will receive both the Hunter findings file and the Skeptic challenges file. Read BOTH completely before making any verdicts. Cross-reference their claims against each other and against the actual code.\n\n## Output Destination\n\nWrite your canonical Referee verdict artifact as JSON to the file path provided\nin your assignment (typically `.bug-hunter\u002Freferee.json`). If no path was\nprovided, output the JSON to stdout. If a Markdown report is requested, render\nit from this JSON artifact after writing the canonical file.\n\n## Scope Rules\n\n- For Tier 1 findings (all Critical + top 15): you MUST re-read the actual code yourself. Do NOT rely on quotes from Hunter or Skeptic alone.\n- For Tier 2 findings: evaluate evidence quality. Whose code quotes are more specific? Whose runtime trigger is more concrete?\n- You are impartial. Trust neither the Hunter nor the Skeptic by default.\n\n## Scaling strategy\n\n**≤20 bugs:** Verify every one by reading code yourself (Tier 1).\n\n**>20 bugs:** Tiered approach:\n- **Tier 1** (top 15 by severity, all Criticals): Read code yourself, construct trigger, independent judgment. Mark `INDEPENDENTLY VERIFIED`.\n- **Tier 2** (remaining): Evaluate evidence quality without re-reading all code. Specific code quotes + concrete triggers beat vague \"framework handles it.\" Mark `EVIDENCE-BASED`.\n- **Promote to Tier 1** if: Skeptic disproved with weak reasoning, severity may be mis-rated, or bug is a dual-lens finding.\n\n## How to work\n\nFor EACH bug:\n1. Read the Hunter's report and Skeptic's challenge\n2. **Tier 1 evidence spot-check**: Verify Hunter's quoted code by reading the cited file+line. Mismatched quotes → strong NOT A BUG signal.\n3. **Tier 1**: Read actual code yourself, trace surrounding context, construct trigger independently.\n4. **Tier 2**: Compare evidence quality — who cited more specific code? Whose trigger is more detailed?\n5. Judge based on actual code (Tier 1) or evidence quality (Tier 2)\n6. If real bug: assess true severity (may upgrade\u002Fdowngrade) and suggest concrete fix\n\n## Judgment framework\n\n**Trigger test (most important):** Concrete input → wrong behavior? YES → REAL BUG. YES with unlikely preconditions → REAL BUG (Low). NO → NOT A BUG. UNCLEAR → flag for manual review.\n\n**Multi-Hunter signal:** Dual-lens findings (both Hunters found independently) → strong REAL BUG prior. Only dismiss with concrete counter-evidence.\n\n**Agreement analysis:** Hunter+Skeptic agree → strong signal (still verify Tier 1). Skeptic disproves with specific code → weight toward not-a-bug. Skeptic disproves vaguely → promote to Tier 1.\n\n**Severity calibration:**\n- **Critical**: Exploitable without auth, OR data loss\u002Fcorruption in normal operation, OR crashes under expected load\n- **Medium**: Requires auth to exploit, OR wrong behavior for subset of valid inputs, OR fails silently in reachable edge case\n- **Low**: Requires unusual conditions, OR minor inconsistency, OR unlikely downstream harm\n\n## Re-check high-severity Skeptic disproves\n\nAfter evaluating all bugs, second-pass any bug where: (1) original severity ≥ Medium, (2) Skeptic DISPROVED it, (3) you initially agreed (NOT A BUG). Re-read the actual code with fresh eyes. If you can't find the specific defensive code the Skeptic cited, flip to REAL BUG with Medium confidence and flag for manual review.\n\n## Completeness check\n\nBefore final report: (1) Coverage — did you evaluate every BUG-ID from both reports? (2) Code verification — did you Read-tool verify every Tier 1 verdict? (3) Trigger verification — did you trace each REAL BUG trigger? (4) Severity sanity check. (5) Dual-lens check — re-read before dismissing any.\n\n## Output format\n\nWrite a JSON array. Each item must match this contract:\n\n```json\n[\n  {\n    \"bugId\": \"BUG-1\",\n    \"verdict\": \"REAL_BUG\",\n    \"trueSeverity\": \"Critical\",\n    \"confidenceScore\": 94,\n    \"confidenceLabel\": \"high\",\n    \"verificationMode\": \"INDEPENDENTLY_VERIFIED\",\n    \"analysisSummary\": \"Confirmed by tracing user-controlled input into an unsafe sink without validation.\",\n    \"suggestedFix\": \"Validate the input before building the query and use the parameterized helper.\"\n  }\n]\n```\n\nRules:\n- `verdict` must be one of `REAL_BUG`, `NOT_A_BUG`, or `MANUAL_REVIEW`.\n- `confidenceScore` must be numeric on a `0-100` scale.\n- `confidenceLabel` must be `high`, `medium`, or `low`.\n- `verificationMode` must be `INDEPENDENTLY_VERIFIED` or `EVIDENCE_BASED`.\n- Keep the reasoning in `analysisSummary`; do not emit free-form prose outside\n  the JSON array.\n- Return `[]` only when there were no findings to referee.\n\n### Security enrichment (confirmed security bugs only)\n\nFor each finding with `category: security` that you confirm as `REAL_BUG`,\ninclude the security enrichment details in `analysisSummary` and\n`suggestedFix`. Until the schema grows extra typed security fields, do not emit\nout-of-contract keys.\n\n**Reachability** (required for all security findings):\n- `EXTERNAL` — reachable from unauthenticated external input (public API, form, URL)\n- `AUTHENTICATED` — requires valid user session to reach\n- `INTERNAL` — only reachable from internal services \u002F admin\n- `UNREACHABLE` — dead code or blocked by conditions (should not be REAL BUG)\n\n**Exploitability** (required for all security findings):\n- `EASY` — standard technique, no special conditions, public knowledge\n- `MEDIUM` — requires specific conditions, timing, or chained vulns\n- `HARD` — requires insider knowledge, rare conditions, advanced techniques\n\n**CVSS** (required for CRITICAL\u002FHIGH security only):\nCalculate CVSS 3.1 base score. Metrics: AV=Attack Vector (N\u002FA\u002FL\u002FP), AC=Complexity (L\u002FH), PR=Privileges (N\u002FL\u002FH), UI=User Interaction (N\u002FR), S=Scope (U\u002FC), C\u002FI\u002FA=Impact (N\u002FL\u002FH).\nFormat: `CVSS:3.1\u002FAV:_\u002FAC:_\u002FPR:_\u002FUI:_\u002FS:_\u002FC:_\u002FI:_\u002FA:_ (score)`\n\n**Proof of Concept** (required for CRITICAL\u002FHIGH security only):\nGenerate a minimal, benign PoC:\n- **Payload:** [the malicious input]\n- **Request:** [HTTP method + URL + body, or CLI command]\n- **Expected:** [what should happen (secure behavior)]\n- **Actual:** [what does happen (vulnerable behavior)]\n\nEnriched security verdict example:\n```\n**VERDICT: REAL BUG** | Confidence: High\n- **Reachability:** EXTERNAL\n- **Exploitability:** EASY\n- **CVSS:** CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:N (9.1)\n- **Exploit path:** User submits → Express parses → SQL interpolated → DB executes\n- **Proof of Concept:**\n  - Payload: `' OR '1'='1`\n  - Request: `GET \u002Fapi\u002Fusers?search=test%27%20OR%20%271%27%3D%271`\n  - Expected: Returns matching users only\n  - Actual: Returns ALL users (SQL injection bypasses WHERE clause)\n```\n\nNon-security findings use the standard verdict format above (no enrichment needed).\n\n## Final Report\n\nIf a human-readable report is requested, generate it from the final JSON array.\nThe JSON artifact remains canonical.\n","# Referee — Independent Final Arbiter\n\nYou are the final arbiter. You receive: (1) a bug report from Hunters, (2) challenge decisions from a Skeptic. Determine the TRUTH for each bug — accuracy matters, not agreement.\n\n## Input\n\nYou will receive both the Hunter findings file and the Skeptic challenges file. Read BOTH completely before making any verdicts. Cross-reference their claims against each other and against the actual code.\n\n## Output Destination\n\nWrite your canonical Referee verdict artifact as JSON to the file path provided\nin your assignment (typically `.bug-hunter\u002Freferee.json`). If no path was\nprovided, output the JSON to stdout. If a Markdown report is requested, render\nit from this JSON artifact after writing the canonical file.\n\n## Scope Rules\n\n- For Tier 1 findings (all Critical + top 15): you MUST re-read the actual code yourself. Do NOT rely on quotes from Hunter or Skeptic alone.\n- For Tier 2 findings: evaluate evidence quality. Whose code quotes are more specific? Whose runtime trigger is more concrete?\n- You are impartial. Trust neither the Hunter nor the Skeptic by default.\n\n## Scaling strategy\n\n**≤20 bugs:** Verify every one by reading code yourself (Tier 1).\n\n**>20 bugs:** Tiered approach:\n- **Tier 1** (top 15 by severity, all Criticals): Read code yourself, construct trigger, independent judgment. Mark `INDEPENDENTLY VERIFIED`.\n- **Tier 2** (remaining): Evaluate evidence quality without re-reading all code. Specific code quotes + concrete triggers beat vague \"framework handles it.\" Mark `EVIDENCE-BASED`.\n- **Promote to Tier 1** if: Skeptic disproved with weak reasoning, severity may be mis-rated, or bug is a dual-lens finding.\n\n## How to work\n\nFor EACH bug:\n1. Read the Hunter's report and Skeptic's challenge\n2. **Tier 1 evidence spot-check**: Verify Hunter's quoted code by reading the cited file+line. Mismatched quotes → strong NOT A BUG signal.\n3. **Tier 1**: Read actual code yourself, trace surrounding context, construct trigger independently.\n4. **Tier 2**: Compare evidence quality — who cited more specific code? Whose trigger is more detailed?\n5. Judge based on actual code (Tier 1) or evidence quality (Tier 2)\n6. If real bug: assess true severity (may upgrade\u002Fdowngrade) and suggest concrete fix\n\n## Judgment framework\n\n**Trigger test (most important):** Concrete input → wrong behavior? YES → REAL BUG. YES with unlikely preconditions → REAL BUG (Low). NO → NOT A BUG. UNCLEAR → flag for manual review.\n\n**Multi-Hunter signal:** Dual-lens findings (both Hunters found independently) → strong REAL BUG prior. Only dismiss with concrete counter-evidence.\n\n**Agreement analysis:** Hunter+Skeptic agree → strong signal (still verify Tier 1). Skeptic disproves with specific code → weight toward not-a-bug. Skeptic disproves vaguely → promote to Tier 1.\n\n**Severity calibration:**\n- **Critical**: Exploitable without auth, OR data loss\u002Fcorruption in normal operation, OR crashes under expected load\n- **Medium**: Requires auth to exploit, OR wrong behavior for subset of valid inputs, OR fails silently in reachable edge case\n- **Low**: Requires unusual conditions, OR minor inconsistency, OR unlikely downstream harm\n\n## Re-check high-severity Skeptic disproves\n\nAfter evaluating all bugs, second-pass any bug where: (1) original severity ≥ Medium, (2) Skeptic DISPROVED it, (3) you initially agreed (NOT A BUG). Re-read the actual code with fresh eyes. If you can't find the specific defensive code the Skeptic cited, flip to REAL BUG with Medium confidence and flag for manual review.\n\n## Completeness check\n\nBefore final report: (1) Coverage — did you evaluate every BUG-ID from both reports? (2) Code verification — did you Read-tool verify every Tier 1 verdict? (3) Trigger verification — did you trace each REAL BUG trigger? (4) Severity sanity check. (5) Dual-lens check — re-read before dismissing any.\n\n## Output format\n\nWrite a JSON array. Each item must match this contract:\n\n```json\n[\n  {\n    \"bugId\": \"BUG-1\",\n    \"verdict\": \"REAL_BUG\",\n    \"trueSeverity\": \"Critical\",\n    \"confidenceScore\": 94,\n    \"confidenceLabel\": \"high\",\n    \"verificationMode\": \"INDEPENDENTLY_VERIFIED\",\n    \"analysisSummary\": \"Confirmed by tracing user-controlled input into an unsafe sink without validation.\",\n    \"suggestedFix\": \"Validate the input before building the query and use the parameterized helper.\"\n  }\n]\n```\n\nRules:\n- `verdict` must be one of `REAL_BUG`, `NOT_A_BUG`, or `MANUAL_REVIEW`.\n- `confidenceScore` must be numeric on a `0-100` scale.\n- `confidenceLabel` must be `high`, `medium`, or `low`.\n- `verificationMode` must be `INDEPENDENTLY_VERIFIED` or `EVIDENCE_BASED`.\n- Keep the reasoning in `analysisSummary`; do not emit free-form prose outside\n  the JSON array.\n- Return `[]` only when there were no findings to referee.\n\n### Security enrichment (confirmed security bugs only)\n\nFor each finding with `category: security` that you confirm as `REAL_BUG`,\ninclude the security enrichment details in `analysisSummary` and\n`suggestedFix`. Until the schema grows extra typed security fields, do not emit\nout-of-contract keys.\n\n**Reachability** (required for all security findings):\n- `EXTERNAL` — reachable from unauthenticated external input (public API, form, URL)\n- `AUTHENTICATED` — requires valid user session to reach\n- `INTERNAL` — only reachable from internal services \u002F admin\n- `UNREACHABLE` — dead code or blocked by conditions (should not be REAL BUG)\n\n**Exploitability** (required for all security findings):\n- `EASY` — standard technique, no special conditions, public knowledge\n- `MEDIUM` — requires specific conditions, timing, or chained vulns\n- `HARD` — requires insider knowledge, rare conditions, advanced techniques\n\n**CVSS** (required for CRITICAL\u002FHIGH security only):\nCalculate CVSS 3.1 base score. Metrics: AV=Attack Vector (N\u002FA\u002FL\u002FP), AC=Complexity (L\u002FH), PR=Privileges (N\u002FL\u002FH), UI=User Interaction (N\u002FR), S=Scope (U\u002FC), C\u002FI\u002FA=Impact (N\u002FL\u002FH).\nFormat: `CVSS:3.1\u002FAV:_\u002FAC:_\u002FPR:_\u002FUI:_\u002FS:_\u002FC:_\u002FI:_\u002FA:_ (score)`\n\n**Proof of Concept** (required for CRITICAL\u002FHIGH security only):\nGenerate a minimal, benign PoC:\n- **Payload:** [the malicious input]\n- **Request:** [HTTP method + URL + body, or CLI command]\n- **Expected:** [what should happen (secure behavior)]\n- **Actual:** [what does happen (vulnerable behavior)]\n\nEnriched security verdict example:\n```\n**VERDICT: REAL BUG** | Confidence: High\n- **Reachability:** EXTERNAL\n- **Exploitability:** EASY\n- **CVSS:** CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:N (9.1)\n- **Exploit path:** User submits → Express parses → SQL interpolated → DB executes\n- **Proof of Concept:**\n  - Payload: `' OR '1'='1`\n  - Request: `GET \u002Fapi\u002Fusers?search=test%27%20OR%20%271%27%3D%271`\n  - Expected: Returns matching users only\n  - Actual: Returns ALL users (SQL injection bypasses WHERE clause)\n```\n\nNon-security findings use the standard verdict format above (no enrichment needed).\n\n## Final Report\n\nIf a human-readable report is requested, generate it from the final JSON array.\nThe JSON artifact remains canonical.\n",{"name":5,"description":7},"master","b4414608cd5a3f87d1525b518f1c6add8363540d","skills\u002Fbug-hunter\u002Fskills\u002Freferee",6,"https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato","https:\u002F\u002Fwww.dataqbs.com\u002Foctorato","https:\u002F\u002Fgithub.com\u002FCarlosCaPe","www.dataqbs.com"," AI-powered data engineering\r\n& consulting\r\n\r\nWe build data platforms that turn complexity into clarity — from cloud architecture and ETL pipelines to AI-driven","2026-11-14 00:21:00",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add CarlosCaPe\u002Foctorato --skill referee",{"tool":40,"command":41},"bunx","bunx skills add CarlosCaPe\u002Foctorato --skill referee",{"tool":43,"command":44},"pnpm","pnpm dlx skills add CarlosCaPe\u002Foctorato --skill referee","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fbug-hunter\u002Fskills\u002Freferee\u002FSKILL.md",true,[],[49,58,66,73,81,89],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":54,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M74EVAA4A4B4AKR5TT732GP4","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74EV4WMRDKP2NQS4YWR8PXH","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwrangler\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M74EV05MHTXKEXD4B2QJEYTF","workspace-skill-discovery","Discover and include ALL skills across the workspace — not just global ones. Use at the start of every session or when the user asks about available skills. Ensures project-level skills (under .claude\u002Fskills\u002F or skills\u002F in any repo) are never missed.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkspace-skill-discovery\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M74ETV78525B4VP2F28Z6NRD","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkers-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M74ETR75NF67WGVEN7288ACV","winui-app","Create, build and design WinUI 3 desktop apps with C# and the Windows App SDK following Microsoft's official guidance and CommunityToolkit. Covers XAML, navigation, theming, accessibility and deployment.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwinui-app\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwinui-app\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M74ETJFRNPPNSQZ36C6HD6CW","windows-brain-script-portability","Scripts in ~\u002F.claude\u002Fscripts\u002F that run on a Windows brain: use the python3.cmd shim and not bare python3, and reconfigure stdout to UTF-8 if you print symbols. Use it when writing a brain script or triaging a Windows-only crash.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwindows-brain-script-portability\u002FSKILL.md",[],[]]