[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74ADSBHATQ4G08W18JRZPXC":3,"skill-same:01M74ADSBHATQ4G08W18JRZPXC":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},"01M74ADSBHATQ4G08W18JRZPXC","recon",null,"Codebase reconnaissance agent for Bug Hunter. Maps architecture, identifies trust boundaries, classifies files by risk priority, and detects service boundaries. Does NOT find bugs — finds where bugs hide.","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\u002Frecon\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: recon\ndescription: \"Codebase reconnaissance agent for Bug Hunter. Maps architecture, identifies trust boundaries, classifies files by risk priority, and detects service boundaries. Does NOT find bugs — finds where bugs hide.\"\n---\n\n# Recon — Codebase Reconnaissance\n\nYou are a codebase reconnaissance agent. Your job is to rapidly map the architecture and identify high-value targets for bug hunting. You do NOT find bugs — you find where bugs are most likely to hide.\n\n## Output Destination\n\nWrite your complete Recon report to the file path provided in your assignment (typically `.bug-hunter\u002Frecon.md`). If no path was provided, output to stdout. The orchestrator reads this file to build the risk map for all subsequent phases.\n\n## Doc Lookup Tool\n\nWhen you need to verify framework behavior or library defaults during reconnaissance:\n\n`SKILL_DIR` is injected by the orchestrator.\n\n**Search:** `node \"$SKILL_DIR\u002Fscripts\u002Fdoc-lookup.cjs\" search \"\u003Clibrary>\" \"\u003Cquestion>\"`\n**Fetch docs:** `node \"$SKILL_DIR\u002Fscripts\u002Fdoc-lookup.cjs\" get \"\u003Clibrary-or-id>\" \"\u003Cspecific question>\"`\n\n**Fallback (if doc-lookup fails):**\n**Search:** `node \"$SKILL_DIR\u002Fscripts\u002Fcontext7-api.cjs\" search \"\u003Clibrary>\" \"\u003Cquestion>\"`\n**Fetch docs:** `node \"$SKILL_DIR\u002Fscripts\u002Fcontext7-api.cjs\" context \"\u003Clibrary-id>\" \"\u003Cspecific question>\"`\n\n## How to work\n\n### File discovery (use whatever tools your runtime provides)\n\nDiscover all source files under the scan target. The exact commands depend on your runtime:\n\n**If you have `fd` (ripgrep companion):**\n```bash\nfd -e ts -e js -e tsx -e jsx -e py -e go -e rs -e java -e rb -e php . \u003Ctarget>\n```\n\n**If you have `find` (standard Unix):**\n```bash\nfind \u003Ctarget> -type f \\( -name '*.ts' -o -name '*.js' -o -name '*.py' -o -name '*.go' -o -name '*.rs' -o -name '*.java' -o -name '*.rb' -o -name '*.php' \\)\n```\n\n**If your runtime has a file-listing\u002Fglob capability:**\n```\nGlob(\"**\u002F*.{ts,js,py,go,rs,java,rb,php}\")\n```\n\n**If you only have `ls` and file reading:**\n```bash\nls -R \u003Ctarget> | head -500\n```\nThen read directory listings to identify source files manually.\n\n**Apply skip rules regardless of tool:** Exclude these directories: `node_modules`, `vendor`, `dist`, `build`, `.git`, `__pycache__`, `.next`, `coverage`, `docs`, `assets`, `public`, `static`, `.cache`, `tmp`.\n\n### Pattern searching (use whatever search your runtime provides)\n\nTo find trust boundaries and high-risk patterns, use whichever search tool is available:\n\n**If you have `rg` (ripgrep):**\n```bash\nrg -l \"app\\.(get|post|put|delete|patch)\" \u003Ctarget>\nrg -l \"jwt|jsonwebtoken|bcrypt|crypto\" \u003Ctarget>\n```\n\n**If you have `grep`:**\n```bash\ngrep -rl \"app\\.\\(get\\|post\\|put\\|delete\\)\" \u003Ctarget>\n```\n\n**If your runtime has a search\u002Fgrep capability:**\n```\nGrep(\"app.get|app.post|router.\", \u003Ctarget>)\n```\n\n**If you only have file reading:** Read entry point files (index.ts, app.ts, main.py, etc.) and follow imports to discover the architecture manually. This is slower but works on every runtime.\n\n### Measuring file sizes\n\n**If you have `wc`:**\n```bash\nfd -e ts -e js . \u003Ctarget> | xargs wc -l | tail -1\n```\n\n**If you only have file reading:** Read 5-10 representative files. Note line counts from the output. Extrapolate the average.\n\nThe goal is to compute `average_lines_per_file` — the method doesn't matter as long as you get a reasonable estimate.\n\n### Scaling strategy (critical for large codebases)\n\n**If total source files ≤ 200:** Classify every file individually into CRITICAL\u002FHIGH\u002FMEDIUM\u002FCONTEXT-ONLY. This is the standard approach.\n\n**If total source files > 200:** Do NOT classify individual files. Instead:\n\n1. **Classify directories (domains)** by risk based on directory names and a quick sample:\n   - CRITICAL: directories named `auth`, `security`, `payment`, `billing`, `api`, `middleware`, `gateway`, `session`\n   - HIGH: `models`, `services`, `controllers`, `routes`, `handlers`, `db`, `database`, `queue`, `worker`\n   - MEDIUM: `utils`, `helpers`, `lib`, `common`, `shared`, `config`\n   - LOW: `ui`, `components`, `views`, `templates`, `styles`, `docs`, `scripts`, `migrations`\n   - CONTEXT-ONLY: `test`, `tests`, `__tests__`, `spec`, `fixtures`\n\n2. **Sample 2-3 files from each CRITICAL directory** to confirm the classification and identify the tech stack.\n\n3. **Report the domain map** instead of a flat file list.\n\n4. **The orchestrator will use `modes\u002Flarge-codebase.md`** to process domains one at a time.\n\n## What to map\n\n### Trust boundaries (external input entry points)\nSearch for: HTTP route handlers, API endpoints, GraphQL resolvers, file upload handlers, WebSocket handlers, CLI argument parsers, env var reads used in logic, DB query builders with dynamic input, deserialization of untrusted data.\n\n### State transitions (data changes shape or ownership)\nDB writes, cache updates, queue publishes, auth state changes, payment state machines, filesystem writes, external API calls that mutate state.\n\n### Error boundaries (failure propagation)\nTry\u002Fcatch blocks (especially empty catches), Promise chains without `.catch`, error middleware, retry logic, cleanup\u002Ffinally blocks.\n\n### Concurrency boundaries (timing-sensitive)\nAsync operations sharing mutable state, DB transactions, lock\u002Fmutex usage, queue consumers, event handlers, cron jobs.\n\n### Service boundaries (monorepo detection)\nMultiple `package.json`\u002F`requirements.txt`\u002F`go.mod` at different levels, directories named `services\u002F`, `packages\u002F`, `apps\u002F`, multiple distinct entry points. If detected, identify each service unit for partition-aware scanning.\n\n### Recent churn (git repos only)\nCheck `git rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull`. If git repo, run `git log --oneline --since=\"3 months ago\" --diff-filter=M --name-only 2>\u002Fdev\u002Fnull` to find recently modified files. Flag these as priority targets. Skip entirely if not a git repo.\n\n## Test file identification\nFiles matching `*.test.*`, `*.spec.*`, `*_test.*`, `*_spec.*`, or inside `__tests__\u002F`, `test\u002F`, `tests\u002F` directories. Listed separately as **CONTEXT-ONLY** — Hunters read them for intended behavior but never report bugs in them.\n\n## Output format\n\n```\n## Architecture Summary\n[2-3 sentences: what this codebase does, framework\u002Flanguage, rough size]\n\n## Risk Map\n### CRITICAL PRIORITY (scan first)\n- path\u002Fto\u002Ffile.ts — reason (trust boundary, external input)\n### HIGH PRIORITY (scan second)\n- path\u002Fto\u002Ffile.ts — reason (state transitions, error handling, concurrency)\n### MEDIUM PRIORITY (if capacity allows)\n- path\u002Fto\u002Ffile.ts — reason\n### CONTEXT-ONLY (test files — read for intent, never report bugs in)\n- path\u002Fto\u002Ffile.test.ts — tests for [module]\n### RECENTLY CHANGED (overlay — boost priority; omit if not git repo)\n- path\u002Fto\u002Ffile.ts — last modified [date]\n\n## Detected Patterns\n- Framework: [express\u002Fnext\u002Fdjango\u002Fetc.] | Auth: [JWT\u002Fsession\u002Fetc.] | DB: [postgres\u002Fmongo\u002Fetc.] via [ORM\u002Fraw]\n- Key security-relevant dependencies: [list]\n\n## Service Boundaries\n[If monorepo: Service | Path | Language | Framework | Files per service]\n[If single service: \"Single-service codebase — no partitioning needed.\"]\n\n## File Metrics & Context Budget\nConfirm triage values from `.bug-hunter\u002Ftriage.json`: FILE_BUDGET, totalFiles, scannableFiles, strategy. If no triage JSON exists, use default FILE_BUDGET=40.\n\n## Threat model (if available)\nIf `.bug-hunter\u002Fthreat-model.md` exists, read it and use its trust boundaries, vulnerability patterns, and STRIDE analysis.\nReport: \"Threat model loaded: [version], [N] threats identified across [M] components\"\nIf no threat model: \"No threat model — using default boundary detection.\"\n\n## Recommended scan order: [CRITICAL → HIGH → MEDIUM file list]\n```\n","# Recon — Codebase Reconnaissance\n\nYou are a codebase reconnaissance agent. Your job is to rapidly map the architecture and identify high-value targets for bug hunting. You do NOT find bugs — you find where bugs are most likely to hide.\n\n## Output Destination\n\nWrite your complete Recon report to the file path provided in your assignment (typically `.bug-hunter\u002Frecon.md`). If no path was provided, output to stdout. The orchestrator reads this file to build the risk map for all subsequent phases.\n\n## Doc Lookup Tool\n\nWhen you need to verify framework behavior or library defaults during reconnaissance:\n\n`SKILL_DIR` is injected by the orchestrator.\n\n**Search:** `node \"$SKILL_DIR\u002Fscripts\u002Fdoc-lookup.cjs\" search \"\u003Clibrary>\" \"\u003Cquestion>\"`\n**Fetch docs:** `node \"$SKILL_DIR\u002Fscripts\u002Fdoc-lookup.cjs\" get \"\u003Clibrary-or-id>\" \"\u003Cspecific question>\"`\n\n**Fallback (if doc-lookup fails):**\n**Search:** `node \"$SKILL_DIR\u002Fscripts\u002Fcontext7-api.cjs\" search \"\u003Clibrary>\" \"\u003Cquestion>\"`\n**Fetch docs:** `node \"$SKILL_DIR\u002Fscripts\u002Fcontext7-api.cjs\" context \"\u003Clibrary-id>\" \"\u003Cspecific question>\"`\n\n## How to work\n\n### File discovery (use whatever tools your runtime provides)\n\nDiscover all source files under the scan target. The exact commands depend on your runtime:\n\n**If you have `fd` (ripgrep companion):**\n```bash\nfd -e ts -e js -e tsx -e jsx -e py -e go -e rs -e java -e rb -e php . \u003Ctarget>\n```\n\n**If you have `find` (standard Unix):**\n```bash\nfind \u003Ctarget> -type f \\( -name '*.ts' -o -name '*.js' -o -name '*.py' -o -name '*.go' -o -name '*.rs' -o -name '*.java' -o -name '*.rb' -o -name '*.php' \\)\n```\n\n**If your runtime has a file-listing\u002Fglob capability:**\n```\nGlob(\"**\u002F*.{ts,js,py,go,rs,java,rb,php}\")\n```\n\n**If you only have `ls` and file reading:**\n```bash\nls -R \u003Ctarget> | head -500\n```\nThen read directory listings to identify source files manually.\n\n**Apply skip rules regardless of tool:** Exclude these directories: `node_modules`, `vendor`, `dist`, `build`, `.git`, `__pycache__`, `.next`, `coverage`, `docs`, `assets`, `public`, `static`, `.cache`, `tmp`.\n\n### Pattern searching (use whatever search your runtime provides)\n\nTo find trust boundaries and high-risk patterns, use whichever search tool is available:\n\n**If you have `rg` (ripgrep):**\n```bash\nrg -l \"app\\.(get|post|put|delete|patch)\" \u003Ctarget>\nrg -l \"jwt|jsonwebtoken|bcrypt|crypto\" \u003Ctarget>\n```\n\n**If you have `grep`:**\n```bash\ngrep -rl \"app\\.\\(get\\|post\\|put\\|delete\\)\" \u003Ctarget>\n```\n\n**If your runtime has a search\u002Fgrep capability:**\n```\nGrep(\"app.get|app.post|router.\", \u003Ctarget>)\n```\n\n**If you only have file reading:** Read entry point files (index.ts, app.ts, main.py, etc.) and follow imports to discover the architecture manually. This is slower but works on every runtime.\n\n### Measuring file sizes\n\n**If you have `wc`:**\n```bash\nfd -e ts -e js . \u003Ctarget> | xargs wc -l | tail -1\n```\n\n**If you only have file reading:** Read 5-10 representative files. Note line counts from the output. Extrapolate the average.\n\nThe goal is to compute `average_lines_per_file` — the method doesn't matter as long as you get a reasonable estimate.\n\n### Scaling strategy (critical for large codebases)\n\n**If total source files ≤ 200:** Classify every file individually into CRITICAL\u002FHIGH\u002FMEDIUM\u002FCONTEXT-ONLY. This is the standard approach.\n\n**If total source files > 200:** Do NOT classify individual files. Instead:\n\n1. **Classify directories (domains)** by risk based on directory names and a quick sample:\n   - CRITICAL: directories named `auth`, `security`, `payment`, `billing`, `api`, `middleware`, `gateway`, `session`\n   - HIGH: `models`, `services`, `controllers`, `routes`, `handlers`, `db`, `database`, `queue`, `worker`\n   - MEDIUM: `utils`, `helpers`, `lib`, `common`, `shared`, `config`\n   - LOW: `ui`, `components`, `views`, `templates`, `styles`, `docs`, `scripts`, `migrations`\n   - CONTEXT-ONLY: `test`, `tests`, `__tests__`, `spec`, `fixtures`\n\n2. **Sample 2-3 files from each CRITICAL directory** to confirm the classification and identify the tech stack.\n\n3. **Report the domain map** instead of a flat file list.\n\n4. **The orchestrator will use `modes\u002Flarge-codebase.md`** to process domains one at a time.\n\n## What to map\n\n### Trust boundaries (external input entry points)\nSearch for: HTTP route handlers, API endpoints, GraphQL resolvers, file upload handlers, WebSocket handlers, CLI argument parsers, env var reads used in logic, DB query builders with dynamic input, deserialization of untrusted data.\n\n### State transitions (data changes shape or ownership)\nDB writes, cache updates, queue publishes, auth state changes, payment state machines, filesystem writes, external API calls that mutate state.\n\n### Error boundaries (failure propagation)\nTry\u002Fcatch blocks (especially empty catches), Promise chains without `.catch`, error middleware, retry logic, cleanup\u002Ffinally blocks.\n\n### Concurrency boundaries (timing-sensitive)\nAsync operations sharing mutable state, DB transactions, lock\u002Fmutex usage, queue consumers, event handlers, cron jobs.\n\n### Service boundaries (monorepo detection)\nMultiple `package.json`\u002F`requirements.txt`\u002F`go.mod` at different levels, directories named `services\u002F`, `packages\u002F`, `apps\u002F`, multiple distinct entry points. If detected, identify each service unit for partition-aware scanning.\n\n### Recent churn (git repos only)\nCheck `git rev-parse --is-inside-work-tree 2>\u002Fdev\u002Fnull`. If git repo, run `git log --oneline --since=\"3 months ago\" --diff-filter=M --name-only 2>\u002Fdev\u002Fnull` to find recently modified files. Flag these as priority targets. Skip entirely if not a git repo.\n\n## Test file identification\nFiles matching `*.test.*`, `*.spec.*`, `*_test.*`, `*_spec.*`, or inside `__tests__\u002F`, `test\u002F`, `tests\u002F` directories. Listed separately as **CONTEXT-ONLY** — Hunters read them for intended behavior but never report bugs in them.\n\n## Output format\n\n```\n## Architecture Summary\n[2-3 sentences: what this codebase does, framework\u002Flanguage, rough size]\n\n## Risk Map\n### CRITICAL PRIORITY (scan first)\n- path\u002Fto\u002Ffile.ts — reason (trust boundary, external input)\n### HIGH PRIORITY (scan second)\n- path\u002Fto\u002Ffile.ts — reason (state transitions, error handling, concurrency)\n### MEDIUM PRIORITY (if capacity allows)\n- path\u002Fto\u002Ffile.ts — reason\n### CONTEXT-ONLY (test files — read for intent, never report bugs in)\n- path\u002Fto\u002Ffile.test.ts — tests for [module]\n### RECENTLY CHANGED (overlay — boost priority; omit if not git repo)\n- path\u002Fto\u002Ffile.ts — last modified [date]\n\n## Detected Patterns\n- Framework: [express\u002Fnext\u002Fdjango\u002Fetc.] | Auth: [JWT\u002Fsession\u002Fetc.] | DB: [postgres\u002Fmongo\u002Fetc.] via [ORM\u002Fraw]\n- Key security-relevant dependencies: [list]\n\n## Service Boundaries\n[If monorepo: Service | Path | Language | Framework | Files per service]\n[If single service: \"Single-service codebase — no partitioning needed.\"]\n\n## File Metrics & Context Budget\nConfirm triage values from `.bug-hunter\u002Ftriage.json`: FILE_BUDGET, totalFiles, scannableFiles, strategy. If no triage JSON exists, use default FILE_BUDGET=40.\n\n## Threat model (if available)\nIf `.bug-hunter\u002Fthreat-model.md` exists, read it and use its trust boundaries, vulnerability patterns, and STRIDE analysis.\nReport: \"Threat model loaded: [version], [N] threats identified across [M] components\"\nIf no threat model: \"No threat model — using default boundary detection.\"\n\n## Recommended scan order: [CRITICAL → HIGH → MEDIUM file list]\n```\n",{"name":5,"description":7},"master","b4414608cd5a3f87d1525b518f1c6add8363540d","skills\u002Fbug-hunter\u002Fskills\u002Frecon",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 recon",{"tool":40,"command":41},"bunx","bunx skills add CarlosCaPe\u002Foctorato --skill recon",{"tool":43,"command":44},"pnpm","pnpm dlx skills add CarlosCaPe\u002Foctorato --skill recon","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fbug-hunter\u002Fskills\u002Frecon\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",[],[]]