[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMZN2HNHM2AP2CMRG0SFZK":3,"skill-same:01M7DMZN2HNHM2AP2CMRG0SFZK":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7DMZN2HNHM2AP2CMRG0SFZK","secret-handling",null,"Never read .env files or write secrets to .squad\u002F committed files","zuwasi\u002Fwazatator","zuwasi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F190716959?v=4","01M7DMZ8MRBNDR8VVP3M1JDTDF","Daniel Liezrowice","01M7DMZ8NVFGJP9Z8BXF127YR0",2,"MIT","https:\u002F\u002Fgithub.com\u002Fzuwasi\u002Fwazatator\u002Fblob\u002Fmain\u002F.copilot\u002Fskills\u002Fsecret-handling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: secret-handling\ndescription: Never read .env files or write secrets to .squad\u002F committed files\ndomain: security, file-operations, team-collaboration\nconfidence: high\nsource: earned (issue #267 — credential leak incident)\n---\n\n## Context\n\nSpawned agents have read access to the entire repository, including `.env` files containing live credentials. If an agent reads secrets and writes them to `.squad\u002F` files (decisions, logs, history), Scribe auto-commits them to git, exposing them in remote history. This skill codifies absolute prohibitions and safe alternatives.\n\n## Patterns\n\n### Prohibited File Reads\n\n**NEVER read these files:**\n- `.env` (production secrets)\n- `.env.local` (local dev secrets)\n- `.env.production` (production environment)\n- `.env.development` (development environment)\n- `.env.staging` (staging environment)\n- `.env.test` (test environment with real credentials)\n- Any file matching `.env.*` UNLESS explicitly allowed (see below)\n\n**Allowed alternatives:**\n- `.env.example` (safe — contains placeholder values, no real secrets)\n- `.env.sample` (safe — documentation template)\n- `.env.template` (safe — schema\u002Fstructure reference)\n\n**If you need config info:**\n1. **Ask the user directly** — \"What's the database connection string?\"\n2. **Read `.env.example`** — shows structure without exposing secrets\n3. **Read documentation** — check `README.md`, `docs\u002F`, config guides\n\n**NEVER assume you can \"just peek at .env to understand the schema.\"** Use `.env.example` or ask.\n\n### Prohibited Output Patterns\n\n**NEVER write these to `.squad\u002F` files:**\n\n| Pattern Type | Examples | Regex Pattern (for scanning) |\n|--------------|----------|-------------------------------|\n| API Keys | `OPENAI_API_KEY=sk-proj-...`, `GITHUB_TOKEN=ghp_...` | `[A-Z_]+(?:KEY|TOKEN|SECRET)=[^\\s]+` |\n| Passwords | `DB_PASSWORD=super_secret_123`, `password: \"...\"` | `(?:PASSWORD|PASS|PWD)[:=]\\s*[\"']?[^\\s\"']+` |\n| Connection Strings | `postgres:\u002F\u002Fuser:pass@host:5432\u002Fdb`, `Server=...;Password=...` | `(?:postgres|mysql|mongodb):\u002F\u002F[^@]+@|(?:Server|Host)=.*(?:Password|Pwd)=` |\n| JWT Tokens | `eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...` | `eyJ[A-Za-z0-9_-]+\\.eyJ[A-Za-z0-9_-]+\\.[A-Za-z0-9_-]+` |\n| Private Keys | `-----BEGIN PRIVATE KEY-----`, `-----BEGIN RSA PRIVATE KEY-----` | `-----BEGIN [A-Z ]+PRIVATE KEY-----` |\n| AWS Credentials | `AKIA...`, `aws_secret_access_key=...` | `AKIA[0-9A-Z]{16}|aws_secret_access_key=[^\\s]+` |\n| Email Addresses | `user@example.com` (PII violation per team decision) | `[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}` |\n\n**What to write instead:**\n- Placeholder values: `DATABASE_URL=\u003Cset in .env>`\n- Redacted references: `API key configured (see .env.example)`\n- Architecture notes: \"App uses JWT auth — token stored in session\"\n- Schema documentation: \"Requires OPENAI_API_KEY, GITHUB_TOKEN (see .env.example for format)\"\n\n### Scribe Pre-Commit Validation\n\n**Before committing `.squad\u002F` changes, Scribe MUST:**\n\n1. **Scan all staged files** for secret patterns (use regex table above)\n2. **Check for prohibited file names** (don't commit `.env` even if manually staged)\n3. **If secrets detected:**\n   - STOP the commit (do NOT proceed)\n   - Remove the file from staging: `git reset HEAD \u003Cfile>`\n   - Report to user:\n     ```\n     🚨 SECRET DETECTED — commit blocked\n     \n     File: .squad\u002Fdecisions\u002Finbox\u002Friver-db-config.md\n     Pattern: DATABASE_URL=postgres:\u002F\u002Fuser:password@localhost:5432\u002Fprod\n     \n     This file contains credentials and MUST NOT be committed.\n     Please remove the secret, replace with placeholder, and try again.\n     ```\n   - Exit with error (never silently skip)\n\n4. **If no secrets detected:**\n   - Proceed with commit as normal\n\n**Implementation note for Scribe:**\n- Run validation AFTER staging files, BEFORE calling `git commit`\n- Use PowerShell `Select-String` or `git diff --cached` to scan staged content\n- Fail loud — secret leaks are unacceptable, blocking the commit is correct behavior\n\n### Remediation — If a Secret Was Already Committed\n\n**If you discover a secret in git history:**\n\n1. **STOP immediately** — do not make more commits\n2. **Alert the user:**\n   ```\n   🚨 CREDENTIAL LEAK DETECTED\n   \n   A secret was found in git history:\n   Commit: abc1234\n   File: .squad\u002Fdecisions\u002Finbox\u002Fagent-config.md\n   Pattern: API_KEY=sk-proj-...\n   \n   This requires immediate remediation:\n   1. Revoke the exposed credential (regenerate API key, rotate password)\n   2. Remove from git history (git filter-repo or BFG)\n   3. Force-push the cleaned history\n   \n   Do NOT proceed with new work until this is resolved.\n   ```\n3. **Do NOT attempt to fix it yourself** — secret removal requires specialized tools\n4. **Wait for user confirmation** before resuming work\n\n## Examples\n\n### ✓ Correct: Reading Config Schema\n\n**Agent needs to know what environment variables are required:**\n\n```\nAgent: \"What environment variables does this app need?\"\n→ Reads `.env.example`:\n    OPENAI_API_KEY=sk-...\n    DATABASE_URL=postgres:\u002F\u002Fuser:pass@localhost:5432\u002Fdb\n    REDIS_URL=redis:\u002F\u002Flocalhost:6379\n\n→ Writes to .squad\u002Fdecisions\u002Finbox\u002Friver-env-setup.md:\n    \"App requires three environment variables:\n    - OPENAI_API_KEY (OpenAI API key, format: sk-...)\n    - DATABASE_URL (Postgres connection string)\n    - REDIS_URL (Redis connection string)\n    See .env.example for full schema.\"\n```\n\n### ✗ Incorrect: Reading Live Credentials\n\n**Agent needs to know database schema:**\n\n```\nAgent: (reads .env)\n    DATABASE_URL=postgres:\u002F\u002Fadmin:super_secret_pw@prod.example.com:5432\u002Fappdb\n\n→ Writes to .squad\u002Fdecisions\u002Finbox\u002Friver-db-schema.md:\n    \"Database connection: postgres:\u002F\u002Fadmin:super_secret_pw@prod.example.com:5432\u002Fappdb\"\n    \n🚨 VIOLATION: Live credential written to committed file\n```\n\n**Correct approach:**\n```\nAgent: (reads .env.example OR asks user)\nUser: \"It's a Postgres database, schema is in migrations\u002F\"\n\n→ Writes to .squad\u002Fdecisions\u002Finbox\u002Friver-db-schema.md:\n    \"Database: Postgres (connection configured in .env). Schema defined in db\u002Fmigrations\u002F.\"\n```\n\n### ✓ Correct: Scribe Pre-Commit Validation\n\n**Scribe is about to commit:**\n\n```powershell\n# Stage files\ngit add .squad\u002F\n\n# Scan staged content for secrets\n$stagedContent = git diff --cached\n$secretPatterns = @(\n    '[A-Z_]+(?:KEY|TOKEN|SECRET)=[^\\s]+',\n    '(?:PASSWORD|PASS|PWD)[:=]\\s*[\"'']?[^\\s\"'']+',\n    'eyJ[A-Za-z0-9_-]+\\.eyJ[A-Za-z0-9_-]+\\.[A-Za-z0-9_-]+'\n)\n\n$detected = $false\nforeach ($pattern in $secretPatterns) {\n    if ($stagedContent -match $pattern) {\n        $detected = $true\n        Write-Host \"🚨 SECRET DETECTED: $($matches[0])\"\n        break\n    }\n}\n\nif ($detected) {\n    # Remove from staging, report, exit\n    git reset HEAD .squad\u002F\n    Write-Error \"Commit blocked — secret detected in staged files\"\n    exit 1\n}\n\n# Safe to commit\ngit commit -F $msgFile\n```\n\n## Anti-Patterns\n\n- ❌ Reading `.env` \"just to check the schema\" — use `.env.example` instead\n- ❌ Writing \"sanitized\" connection strings that still contain credentials\n- ❌ Assuming \"it's just a dev environment\" makes secrets safe to commit\n- ❌ Committing first, scanning later — validation MUST happen before commit\n- ❌ Silently skipping secret detection — fail loud, never silent\n- ❌ Trusting agents to \"know better\" — enforce at multiple layers (prompt, hook, architecture)\n- ❌ Writing secrets to \"temporary\" files in `.squad\u002F` — Scribe commits ALL `.squad\u002F` changes\n- ❌ Extracting \"just the host\" from a connection string — still leaks infrastructure topology\n","## Context\n\nSpawned agents have read access to the entire repository, including `.env` files containing live credentials. If an agent reads secrets and writes them to `.squad\u002F` files (decisions, logs, history), Scribe auto-commits them to git, exposing them in remote history. This skill codifies absolute prohibitions and safe alternatives.\n\n## Patterns\n\n### Prohibited File Reads\n\n**NEVER read these files:**\n- `.env` (production secrets)\n- `.env.local` (local dev secrets)\n- `.env.production` (production environment)\n- `.env.development` (development environment)\n- `.env.staging` (staging environment)\n- `.env.test` (test environment with real credentials)\n- Any file matching `.env.*` UNLESS explicitly allowed (see below)\n\n**Allowed alternatives:**\n- `.env.example` (safe — contains placeholder values, no real secrets)\n- `.env.sample` (safe — documentation template)\n- `.env.template` (safe — schema\u002Fstructure reference)\n\n**If you need config info:**\n1. **Ask the user directly** — \"What's the database connection string?\"\n2. **Read `.env.example`** — shows structure without exposing secrets\n3. **Read documentation** — check `README.md`, `docs\u002F`, config guides\n\n**NEVER assume you can \"just peek at .env to understand the schema.\"** Use `.env.example` or ask.\n\n### Prohibited Output Patterns\n\n**NEVER write these to `.squad\u002F` files:**\n\n| Pattern Type | Examples | Regex Pattern (for scanning) |\n|--------------|----------|-------------------------------|\n| API Keys | `OPENAI_API_KEY=sk-proj-...`, `GITHUB_TOKEN=ghp_...` | `[A-Z_]+(?:KEY|TOKEN|SECRET)=[^\\s]+` |\n| Passwords | `DB_PASSWORD=super_secret_123`, `password: \"...\"` | `(?:PASSWORD|PASS|PWD)[:=]\\s*[\"']?[^\\s\"']+` |\n| Connection Strings | `postgres:\u002F\u002Fuser:pass@host:5432\u002Fdb`, `Server=...;Password=...` | `(?:postgres|mysql|mongodb):\u002F\u002F[^@]+@|(?:Server|Host)=.*(?:Password|Pwd)=` |\n| JWT Tokens | `eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...` | `eyJ[A-Za-z0-9_-]+\\.eyJ[A-Za-z0-9_-]+\\.[A-Za-z0-9_-]+` |\n| Private Keys | `-----BEGIN PRIVATE KEY-----`, `-----BEGIN RSA PRIVATE KEY-----` | `-----BEGIN [A-Z ]+PRIVATE KEY-----` |\n| AWS Credentials | `AKIA...`, `aws_secret_access_key=...` | `AKIA[0-9A-Z]{16}|aws_secret_access_key=[^\\s]+` |\n| Email Addresses | `user@example.com` (PII violation per team decision) | `[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}` |\n\n**What to write instead:**\n- Placeholder values: `DATABASE_URL=\u003Cset in .env>`\n- Redacted references: `API key configured (see .env.example)`\n- Architecture notes: \"App uses JWT auth — token stored in session\"\n- Schema documentation: \"Requires OPENAI_API_KEY, GITHUB_TOKEN (see .env.example for format)\"\n\n### Scribe Pre-Commit Validation\n\n**Before committing `.squad\u002F` changes, Scribe MUST:**\n\n1. **Scan all staged files** for secret patterns (use regex table above)\n2. **Check for prohibited file names** (don't commit `.env` even if manually staged)\n3. **If secrets detected:**\n   - STOP the commit (do NOT proceed)\n   - Remove the file from staging: `git reset HEAD \u003Cfile>`\n   - Report to user:\n     ```\n     🚨 SECRET DETECTED — commit blocked\n     \n     File: .squad\u002Fdecisions\u002Finbox\u002Friver-db-config.md\n     Pattern: DATABASE_URL=postgres:\u002F\u002Fuser:password@localhost:5432\u002Fprod\n     \n     This file contains credentials and MUST NOT be committed.\n     Please remove the secret, replace with placeholder, and try again.\n     ```\n   - Exit with error (never silently skip)\n\n4. **If no secrets detected:**\n   - Proceed with commit as normal\n\n**Implementation note for Scribe:**\n- Run validation AFTER staging files, BEFORE calling `git commit`\n- Use PowerShell `Select-String` or `git diff --cached` to scan staged content\n- Fail loud — secret leaks are unacceptable, blocking the commit is correct behavior\n\n### Remediation — If a Secret Was Already Committed\n\n**If you discover a secret in git history:**\n\n1. **STOP immediately** — do not make more commits\n2. **Alert the user:**\n   ```\n   🚨 CREDENTIAL LEAK DETECTED\n   \n   A secret was found in git history:\n   Commit: abc1234\n   File: .squad\u002Fdecisions\u002Finbox\u002Fagent-config.md\n   Pattern: API_KEY=sk-proj-...\n   \n   This requires immediate remediation:\n   1. Revoke the exposed credential (regenerate API key, rotate password)\n   2. Remove from git history (git filter-repo or BFG)\n   3. Force-push the cleaned history\n   \n   Do NOT proceed with new work until this is resolved.\n   ```\n3. **Do NOT attempt to fix it yourself** — secret removal requires specialized tools\n4. **Wait for user confirmation** before resuming work\n\n## Examples\n\n### ✓ Correct: Reading Config Schema\n\n**Agent needs to know what environment variables are required:**\n\n```\nAgent: \"What environment variables does this app need?\"\n→ Reads `.env.example`:\n    OPENAI_API_KEY=sk-...\n    DATABASE_URL=postgres:\u002F\u002Fuser:pass@localhost:5432\u002Fdb\n    REDIS_URL=redis:\u002F\u002Flocalhost:6379\n\n→ Writes to .squad\u002Fdecisions\u002Finbox\u002Friver-env-setup.md:\n    \"App requires three environment variables:\n    - OPENAI_API_KEY (OpenAI API key, format: sk-...)\n    - DATABASE_URL (Postgres connection string)\n    - REDIS_URL (Redis connection string)\n    See .env.example for full schema.\"\n```\n\n### ✗ Incorrect: Reading Live Credentials\n\n**Agent needs to know database schema:**\n\n```\nAgent: (reads .env)\n    DATABASE_URL=postgres:\u002F\u002Fadmin:super_secret_pw@prod.example.com:5432\u002Fappdb\n\n→ Writes to .squad\u002Fdecisions\u002Finbox\u002Friver-db-schema.md:\n    \"Database connection: postgres:\u002F\u002Fadmin:super_secret_pw@prod.example.com:5432\u002Fappdb\"\n    \n🚨 VIOLATION: Live credential written to committed file\n```\n\n**Correct approach:**\n```\nAgent: (reads .env.example OR asks user)\nUser: \"It's a Postgres database, schema is in migrations\u002F\"\n\n→ Writes to .squad\u002Fdecisions\u002Finbox\u002Friver-db-schema.md:\n    \"Database: Postgres (connection configured in .env). Schema defined in db\u002Fmigrations\u002F.\"\n```\n\n### ✓ Correct: Scribe Pre-Commit Validation\n\n**Scribe is about to commit:**\n\n```powershell\n# Stage files\ngit add .squad\u002F\n\n# Scan staged content for secrets\n$stagedContent = git diff --cached\n$secretPatterns = @(\n    '[A-Z_]+(?:KEY|TOKEN|SECRET)=[^\\s]+',\n    '(?:PASSWORD|PASS|PWD)[:=]\\s*[\"'']?[^\\s\"'']+',\n    'eyJ[A-Za-z0-9_-]+\\.eyJ[A-Za-z0-9_-]+\\.[A-Za-z0-9_-]+'\n)\n\n$detected = $false\nforeach ($pattern in $secretPatterns) {\n    if ($stagedContent -match $pattern) {\n        $detected = $true\n        Write-Host \"🚨 SECRET DETECTED: $($matches[0])\"\n        break\n    }\n}\n\nif ($detected) {\n    # Remove from staging, report, exit\n    git reset HEAD .squad\u002F\n    Write-Error \"Commit blocked — secret detected in staged files\"\n    exit 1\n}\n\n# Safe to commit\ngit commit -F $msgFile\n```\n\n## Anti-Patterns\n\n- ❌ Reading `.env` \"just to check the schema\" — use `.env.example` instead\n- ❌ Writing \"sanitized\" connection strings that still contain credentials\n- ❌ Assuming \"it's just a dev environment\" makes secrets safe to commit\n- ❌ Committing first, scanning later — validation MUST happen before commit\n- ❌ Silently skipping secret detection — fail loud, never silent\n- ❌ Trusting agents to \"know better\" — enforce at multiple layers (prompt, hook, architecture)\n- ❌ Writing secrets to \"temporary\" files in `.squad\u002F` — Scribe commits ALL `.squad\u002F` changes\n- ❌ Extracting \"just the host\" from a connection string — still leaks infrastructure topology\n",{"name":5,"domain":24,"source":25,"confidence":26,"description":7},"security, file-operations, team-collaboration","earned (issue","high","main","862e4c1e1a261338b0e5991ba0795cfe7495aafa",".copilot\u002Fskills\u002Fsecret-handling",1,"https:\u002F\u002Fgithub.com\u002Fzuwasi\u002Fwazatator","https:\u002F\u002Fgithub.com\u002Fzuwasi","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fliezrowice\u002F","It is all started like that:\r\nhttps:\u002F\u002Fzuwasi.github.io\u002FPublic-html-pages\u002Fearly-dos-html\u002F","2026-10-05 02:10:56",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add zuwasi\u002Fwazatator --skill secret-handling",{"tool":42,"command":43},"bunx","bunx skills add zuwasi\u002Fwazatator --skill secret-handling",{"tool":45,"command":46},"pnpm","pnpm dlx skills add zuwasi\u002Fwazatator --skill secret-handling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzuwasi\u002Fwazatator\u002Fblob\u002Fmain\u002F.copilot\u002Fskills\u002Fsecret-handling\u002FSKILL.md",true,[],[51,58,65,72,79,85],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7DN23WD0BPHCQ7TN299NX9X","waza-runner","Run evaluations on Agent Skills to measure their effectiveness. \nUSE FOR: \"run skill evals\", \"evaluate my skill\", \"test skill quality\", \n\"check skill triggers\", \"skill compliance check\", \"measure skill performance\",\n\"run evals on [skill-name]\", \"grade skill execution\".\nDO NOT USE FOR: writing skills (use skill-authoring), improving frontmatter \n(use sensei), or general testing unrelated to skills.","https:\u002F\u002Fgithub.com\u002Fzuwasi\u002Fwazatator\u002Fblob\u002Fmain\u002Fwaza-runner\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":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7DN1WVDHG5TX61GFA2XSDMT","waza","**WORKFLOW SKILL** - Evaluate AI agent skills using structured benchmarks with YAML specs, fixture isolation, and pluggable validators. USE FOR: run waza, waza help, run eval, run benchmark, evaluate skill, test agent, generate eval suite, init eval, compare results, score agent, agent evaluation, skill testing, cross-model comparison. DO NOT USE FOR: improving skill frontmatter (use waza dev), creating new skills from scratch (use skill-creator), token counting or budget checks (use waza tokens). INVOKES: Copilot SDK executor, mock engine, code\u002Fregex validators. FOR SINGLE OPERATIONS: use waza run directly for a single benchmark.","https:\u002F\u002Fgithub.com\u002Fzuwasi\u002Fwazatator\u002Fblob\u002Fmain\u002Fskills\u002Fwaza\u002FSKILL.md",[],[],{"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":19},"01M7DN1QRAVT3B45MBAFKQ1R5T","waza-interactive","Interactive workflow partner for creating, testing, and improving AI agent skills with waza. USE FOR: run my evals, check my skill, compare models, create eval suite, debug failing tests, is my skill ready, ship readiness, interpret results, improve score. DO NOT USE FOR: general coding, non-skill work, writing skill content (use skill-authoring), improving frontmatter only (use sensei).","https:\u002F\u002Fgithub.com\u002Fzuwasi\u002Fwazatator\u002Fblob\u002Fmain\u002Fskills\u002Fwaza-interactive\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7DN1N3VF86B09G7PTCGXTMM","code-explainer","Explains code snippets in plain English, breaking down what the code does step by step. Perfect for learning, code reviews, or documentation.","https:\u002F\u002Fgithub.com\u002Fzuwasi\u002Fwazatator\u002Fblob\u002Fmain\u002Fskills\u002Fcode-explainer\u002FSKILL.md",[],[],{"skillNo":80,"name":74,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7DN1EDND8Q8XNRCFRKQ6P08","**UTILITY SKILL** - Explain code snippets, functions, and algorithms in plain language.\nUSE FOR: explain code, what does this code do, break down this function,\nhelp me understand this, walk through this algorithm, clarify this logic,\nexplain this snippet, describe what happens here.\nDO NOT USE FOR: writing new code (use code generation), fixing bugs (use debugging),\nrefactoring (use refactoring skills), code review with action items.\nINVOKES: file reading tools to access code, language detection for tailored explanations.\nFOR SINGLE OPERATIONS: If the user just needs to see file contents, use file reading tools directly.","https:\u002F\u002Fgithub.com\u002Fzuwasi\u002Fwazatator\u002Fblob\u002Fmain\u002Fexamples\u002Fcode-explainer\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7DN1BBSY9B0GYFNX8XQXSD7","profile-test-skill","**PROFILE TEST** - A skill for testing the profile command.\nUSE FOR: testing profile analysis, verifying structural metrics.\nDO NOT USE FOR: production use.","https:\u002F\u002Fgithub.com\u002Fzuwasi\u002Fwazatator\u002Fblob\u002Fmain\u002Fcmd\u002Fwaza\u002Ftokens\u002Ftestdata\u002Fprofile\u002FSKILL.md",[],[]]