[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73HBRAYN5BMAC4TXY3S3WQ4":3,"skill-same:01M73HBRAYN5BMAC4TXY3S3WQ4":68},{"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":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M73HBRAYN5BMAC4TXY3S3WQ4","production-audit",null,"Audit a shipped repo for production-readiness gaps across RLS, webhooks, secrets, grants, Stripe idempotency, mobile UX, and deployment health.","qhjqhj00\u002Fresearch-skills-pool","qhjqhj00","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29684092?v=4","01M72AE0ZGXVM5C57N512DGQG8","Tommy Chien","01M72AE107ESJMHT7QC5SXX144",3,"MIT","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fsickn33--antigravity-awesome-skills--skills__production-audit\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: production-audit\ndescription: \"Audit a shipped repo for production-readiness gaps across RLS, webhooks, secrets, grants, Stripe idempotency, mobile UX, and deployment health.\"\ncategory: security\nrisk: safe\nsource: community\nsource_repo: commitshow\u002Fproduction-audit\nsource_type: community\ndate_added: \"2026-05-04\"\nauthor: commitshow\ntags: [security, audit, production, vibe-coding, rls, webhook, stripe, supabase, mobile]\ntools: [claude, cursor, gemini, codex, antigravity]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fcommitshow\u002Fproduction-audit\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# Production Audit\n\n## Overview\n\nA skill that runs an external audit on a shipped repo's deployed state — live URL, GitHub signals, secrets exposure, RLS gaps, webhook idempotency, indexes, observability, prompt injection, and ten other failure modes that AI-assisted projects routinely miss.\n\nThis is **complementary** to in-session security skills (`security-review`, OWASP-style, VibeSec, Trail of Bits). Those scan the editor buffer at write-time. This scans the deployed product after you commit. Different timing, different inputs, different findings. Run both for serious launches.\n\nThe skill wraps the [commit.show](https:\u002F\u002Fcommit.show) audit engine via the public CLI (`npx commitshow audit . --json`). Stable JSON envelope (`schema_version: \"1\"`, additive-only). Writes a `.commitshow\u002Faudit.{md,json}` sidecar so future agent sessions can read prior state without re-running the engine.\n\n## When to Use This Skill\n\n- Use when the user asks \"is this production-ready\", \"what would break in prod\", \"score my project\", \"what did I miss\", \"audit my repo\", \"ready to ship\".\n- Use right after merging a feature branch to `main` (helpful as a pre-deploy gate).\n- Use before a public launch \u002F Show HN post \u002F investor demo.\n- Use when `git log` shows >20 commits since the last `.commitshow\u002Faudit.md` was written.\n\n### Skip when\n\n- During active in-session coding — use `security-review` \u002F OWASP-style for line-level patterns. This skill is for post-merge \u002F pre-ship review.\n- For library \u002F scaffold-form repos — the engine handles **app form** best; libraries get a partial-substitute score.\n- If `.commitshow\u002Faudit.json` already exists and is \u003C 1 hour old, read that instead of re-running. Audit is rate-limited (anonymous: 20\u002FIP\u002Fday · 5\u002Frepo\u002Fday · 2000\u002Fday global).\n- Inside a private \u002F non-GitHub repo — the audit pulls public GitHub signals, so private repos return a `not_found` error.\n\n## How It Works\n\n### Step 1: Run the audit\n\nFrom the repo root. The CLI is pinned to a known-good range (an attacker-pushed `0.4.x` won't be picked up silently — bumping the floor is a deliberate edit), the sidecar directory is created up-front, and stderr is split off so install\u002Fdeprecation warnings can't corrupt the JSON envelope:\n\n```bash\nmkdir -p .commitshow\nnpx commitshow@^0.3.23 audit . --json \\\n  > .commitshow\u002Faudit.json \\\n  2> .commitshow\u002Faudit.stderr.log\n```\n\nThis also writes a human-readable `.commitshow\u002Faudit.md` next to it. Subsequent invocations should diff against the prior `audit.json` if it exists, so you can lead with \"+5 since yesterday's audit\" instead of just an absolute number.\n\nIf the user pointed at a remote URL instead of `.`, swap `.` for the URL — keep the same `mkdir -p` + version pin + stderr split:\n\n```bash\nmkdir -p .commitshow\nnpx commitshow@^0.3.23 audit github.com\u002Fowner\u002Frepo --json \\\n  > .commitshow\u002Faudit.json \\\n  2> .commitshow\u002Faudit.stderr.log\n```\n\n### Step 2: Parse the envelope\n\nThe JSON envelope is stable (`schema_version: \"1\"`, additive-only). Read these fields:\n\n| Field | Meaning |\n|---|---|\n| `score.total` | 0-100 production-readiness score |\n| `score.delta_since_last` | change vs. parent snapshot · positive = improving |\n| `score.band` | `strong` (80+) · `mid` (60-79) · `early` (\u003C60) |\n| `concerns[]` | top issues, ordered by impact · each has `axis` + `bullet` |\n| `strengths[]` | top 3 things that work · for context only |\n| `standing` | optional · only when the project is auditioning on commit.show |\n| `snapshot.created_at` \u002F `trigger_type` | when the audit ran |\n\nConcerns are sorted by decision-impact, not severity. Position 1 is the bullet to lead with.\n\n### Step 3: Surface to the user\n\nLead with score + trajectory in **one sentence**, then the top concerns. Do not dump the full JSON. Format:\n\n```\nScore: 82\u002F100 (+5 since yesterday) · band: strong\n\nTop concerns:\n  ↓ [Security] No API rate limiting on \u002Fauth — IP cap missing\n  ↓ [Infrastructure] webhook handler at api\u002Fstripe.ts — signature verified, but no\n    idempotency-key check (replay attack window open)\n\nWant me to fix the webhook idempotency gap first?\n```\n\nRules:\n- Use the exact bullet from `concerns[].bullet` — the audit engine already wrote action-oriented copy.\n- Don't list strengths unless the user explicitly asks. They're not actionable in this context.\n- Always end with a follow-up question that names a specific concern. Don't ask \"what do you want to do?\" — ask \"fix X first?\".\n- If `score.delta_since_last` is negative or null, lead with the absolute score only.\n\n### Step 4: If the user picks a concern, scope a fix\n\nFor the chosen concern:\n1. Read the file(s) cited in the bullet.\n2. Confirm the gap matches the description (the engine occasionally over-flags when the issue is mitigated elsewhere).\n3. Propose a minimal patch — single-file when possible.\n4. **Don't apply without explicit approval.** Show the diff first. The user is deciding what to ship; you're a lens.\n\nAfter applying a fix, suggest re-running with `--refresh` (same canonical form as Step 1, so `audit.json` stays the source of truth for delta calculations):\n\n```bash\nmkdir -p .commitshow\nnpx commitshow@^0.3.23 audit . --json --refresh \\\n  > .commitshow\u002Faudit.json \\\n  2> .commitshow\u002Faudit.stderr.log\n```\n\n## Examples\n\n### Example 1: User asks \"is this production-ready?\"\n\n```bash\nmkdir -p .commitshow\nnpx commitshow@^0.3.23 audit . --json \\\n  > .commitshow\u002Faudit.json \\\n  2> .commitshow\u002Faudit.stderr.log\n```\n\nThen surface:\n\n```\nScore: 67\u002F100 · band: mid\n\nTop concerns:\n  ↓ [Security] members table uses column-level GRANT but paid_audits_credit\n    column lacks SELECT grant — silent 42501 on every read\n  ↓ [Infrastructure] stripe.checkout.sessions.create called without\n    idempotencyKey — duplicate-charge surface\n\nWant me to fix the column GRANT first? Single SQL line.\n```\n\n### Example 2: Cross-check a specific concern\n\nUser: \"show me where the webhook idempotency gap is\"\n\n```bash\ncat .commitshow\u002Faudit.json | jq '.concerns[] | select(.axis==\"Infrastructure\")'\n```\n\nFind the file path in the bullet, read it, confirm the gap matches.\n\n## Best Practices\n\n- ✅ Always cite the exact bullet from `concerns[].bullet` — they're already action-oriented\n- ✅ Lead with score + delta in a single sentence, then concerns\n- ✅ End with a specific follow-up question naming a concern\n- ✅ Read prior `.commitshow\u002Faudit.json` before re-running (within 1h)\n- ✅ Use `--refresh` after the user merges a fix so the next audit reflects it\n- ❌ Don't dump full JSON to the user\n- ❌ Don't list strengths unless the user explicitly asks\n- ❌ Don't apply fixes without approval — show diff first\n- ❌ Don't fault private repos for not auditing — explain why and suggest making public\n\n## Limitations\n\n- This skill does not replace environment-specific validation, testing, or expert review.\n- The audit engine is calibrated for **deployed apps** with a live URL. CLI \u002F library \u002F scaffold form gets a partial-substitute score (max ~45\u002F50 on the audit pillar) — fair but not flattering.\n- Behind a corporate firewall blocking `*.supabase.co`, the API call fails. There is no offline mode — the audit relies on the public engine.\n- Cold audit takes 60-90s. Cached audits (within 7 days) return instantly. `--refresh` force-bypasses cache (counts against rate limits).\n\n## Security & Safety Notes\n\n- The skill executes `npx commitshow@latest audit ...` which is a network call to a public API at `https:\u002F\u002Fapi.commit.show` (proxied to Supabase Edge Functions). No credentials are sent — anonymous usage subject to per-IP \u002F per-URL \u002F global rate limits.\n- The CLI writes `.commitshow\u002Faudit.{md,json}` in the current working directory. These files are safe to commit (no secrets) but conventionally gitignored as transient artifacts.\n- The audit engine **only reads** public GitHub signals. It does not modify the user's repo or push commits.\n- All per-finding fix proposals must be shown as diffs and approved by the user before any edit. Never apply without explicit confirmation.\n\n## Common Pitfalls\n\n- **Problem:** Audit returns `not_found` for a private repo\n  **Solution:** The engine pulls public GitHub signals only. Either make the repo public or use `--no-network` for local-only deterministic checks.\n\n- **Problem:** Rate limit hit (`429`)\n  **Solution:** Wait until next day (limits reset 00:00 UTC) or sign in at commit.show for higher per-repo caps.\n\n- **Problem:** Score seems too low for a polished library \u002F CLI\n  **Solution:** The engine biases toward app form. CLI \u002F library \u002F scaffold gets a partial substitute score capped around 45\u002F50 on the audit pillar. Calibration acknowledged trade-off.\n\n- **Problem:** `concerns[]` is empty after re-running\n  **Solution:** Re-audit may have hit cache. Use `--refresh` to force-bypass.\n\n## Related Skills\n\n- `@security-review` — In-session line-level security patterns. Run alongside this skill, not in place of.\n- `@vibesec` — Editor-buffer security review for vibe-coded projects. Different lens.\n- `@owasp-security` — OWASP Top 10 coverage during coding. Companion.\n- `@trail-of-bits-skills` — CodeQL \u002F Semgrep static analysis. Different layer.\n\n## Additional Resources\n\n- Canonical repo: \u003Chttps:\u002F\u002Fgithub.com\u002Fcommitshow\u002Fproduction-audit>\n- Audit engine source: \u003Chttps:\u002F\u002Fgithub.com\u002Fcommitshow\u002Fcommitshow\u002Fblob\u002Fmain\u002Fsupabase\u002Ffunctions\u002Fanalyze-project\u002Findex.ts>\n- 14-frame failure framework documented in the engine source above.\n- JSON schema: stable at `schema_version: \"1\"` · additive-only changes.\n- CLI: \u003Chttps:\u002F\u002Fgithub.com\u002Fcommitshow\u002Fcli>\n- Public REST API: `https:\u002F\u002Fapi.commit.show\u002Faudit?repo=...&format=json`\n- skills.sh listing: \u003Chttps:\u002F\u002Fskills.sh\u002Fcommitshow\u002Fproduction-audit>\n","# Production Audit\n\n## Overview\n\nA skill that runs an external audit on a shipped repo's deployed state — live URL, GitHub signals, secrets exposure, RLS gaps, webhook idempotency, indexes, observability, prompt injection, and ten other failure modes that AI-assisted projects routinely miss.\n\nThis is **complementary** to in-session security skills (`security-review`, OWASP-style, VibeSec, Trail of Bits). Those scan the editor buffer at write-time. This scans the deployed product after you commit. Different timing, different inputs, different findings. Run both for serious launches.\n\nThe skill wraps the [commit.show](https:\u002F\u002Fcommit.show) audit engine via the public CLI (`npx commitshow audit . --json`). Stable JSON envelope (`schema_version: \"1\"`, additive-only). Writes a `.commitshow\u002Faudit.{md,json}` sidecar so future agent sessions can read prior state without re-running the engine.\n\n## When to Use This Skill\n\n- Use when the user asks \"is this production-ready\", \"what would break in prod\", \"score my project\", \"what did I miss\", \"audit my repo\", \"ready to ship\".\n- Use right after merging a feature branch to `main` (helpful as a pre-deploy gate).\n- Use before a public launch \u002F Show HN post \u002F investor demo.\n- Use when `git log` shows >20 commits since the last `.commitshow\u002Faudit.md` was written.\n\n### Skip when\n\n- During active in-session coding — use `security-review` \u002F OWASP-style for line-level patterns. This skill is for post-merge \u002F pre-ship review.\n- For library \u002F scaffold-form repos — the engine handles **app form** best; libraries get a partial-substitute score.\n- If `.commitshow\u002Faudit.json` already exists and is \u003C 1 hour old, read that instead of re-running. Audit is rate-limited (anonymous: 20\u002FIP\u002Fday · 5\u002Frepo\u002Fday · 2000\u002Fday global).\n- Inside a private \u002F non-GitHub repo — the audit pulls public GitHub signals, so private repos return a `not_found` error.\n\n## How It Works\n\n### Step 1: Run the audit\n\nFrom the repo root. The CLI is pinned to a known-good range (an attacker-pushed `0.4.x` won't be picked up silently — bumping the floor is a deliberate edit), the sidecar directory is created up-front, and stderr is split off so install\u002Fdeprecation warnings can't corrupt the JSON envelope:\n\n```bash\nmkdir -p .commitshow\nnpx commitshow@^0.3.23 audit . --json \\\n  > .commitshow\u002Faudit.json \\\n  2> .commitshow\u002Faudit.stderr.log\n```\n\nThis also writes a human-readable `.commitshow\u002Faudit.md` next to it. Subsequent invocations should diff against the prior `audit.json` if it exists, so you can lead with \"+5 since yesterday's audit\" instead of just an absolute number.\n\nIf the user pointed at a remote URL instead of `.`, swap `.` for the URL — keep the same `mkdir -p` + version pin + stderr split:\n\n```bash\nmkdir -p .commitshow\nnpx commitshow@^0.3.23 audit github.com\u002Fowner\u002Frepo --json \\\n  > .commitshow\u002Faudit.json \\\n  2> .commitshow\u002Faudit.stderr.log\n```\n\n### Step 2: Parse the envelope\n\nThe JSON envelope is stable (`schema_version: \"1\"`, additive-only). Read these fields:\n\n| Field | Meaning |\n|---|---|\n| `score.total` | 0-100 production-readiness score |\n| `score.delta_since_last` | change vs. parent snapshot · positive = improving |\n| `score.band` | `strong` (80+) · `mid` (60-79) · `early` (\u003C60) |\n| `concerns[]` | top issues, ordered by impact · each has `axis` + `bullet` |\n| `strengths[]` | top 3 things that work · for context only |\n| `standing` | optional · only when the project is auditioning on commit.show |\n| `snapshot.created_at` \u002F `trigger_type` | when the audit ran |\n\nConcerns are sorted by decision-impact, not severity. Position 1 is the bullet to lead with.\n\n### Step 3: Surface to the user\n\nLead with score + trajectory in **one sentence**, then the top concerns. Do not dump the full JSON. Format:\n\n```\nScore: 82\u002F100 (+5 since yesterday) · band: strong\n\nTop concerns:\n  ↓ [Security] No API rate limiting on \u002Fauth — IP cap missing\n  ↓ [Infrastructure] webhook handler at api\u002Fstripe.ts — signature verified, but no\n    idempotency-key check (replay attack window open)\n\nWant me to fix the webhook idempotency gap first?\n```\n\nRules:\n- Use the exact bullet from `concerns[].bullet` — the audit engine already wrote action-oriented copy.\n- Don't list strengths unless the user explicitly asks. They're not actionable in this context.\n- Always end with a follow-up question that names a specific concern. Don't ask \"what do you want to do?\" — ask \"fix X first?\".\n- If `score.delta_since_last` is negative or null, lead with the absolute score only.\n\n### Step 4: If the user picks a concern, scope a fix\n\nFor the chosen concern:\n1. Read the file(s) cited in the bullet.\n2. Confirm the gap matches the description (the engine occasionally over-flags when the issue is mitigated elsewhere).\n3. Propose a minimal patch — single-file when possible.\n4. **Don't apply without explicit approval.** Show the diff first. The user is deciding what to ship; you're a lens.\n\nAfter applying a fix, suggest re-running with `--refresh` (same canonical form as Step 1, so `audit.json` stays the source of truth for delta calculations):\n\n```bash\nmkdir -p .commitshow\nnpx commitshow@^0.3.23 audit . --json --refresh \\\n  > .commitshow\u002Faudit.json \\\n  2> .commitshow\u002Faudit.stderr.log\n```\n\n## Examples\n\n### Example 1: User asks \"is this production-ready?\"\n\n```bash\nmkdir -p .commitshow\nnpx commitshow@^0.3.23 audit . --json \\\n  > .commitshow\u002Faudit.json \\\n  2> .commitshow\u002Faudit.stderr.log\n```\n\nThen surface:\n\n```\nScore: 67\u002F100 · band: mid\n\nTop concerns:\n  ↓ [Security] members table uses column-level GRANT but paid_audits_credit\n    column lacks SELECT grant — silent 42501 on every read\n  ↓ [Infrastructure] stripe.checkout.sessions.create called without\n    idempotencyKey — duplicate-charge surface\n\nWant me to fix the column GRANT first? Single SQL line.\n```\n\n### Example 2: Cross-check a specific concern\n\nUser: \"show me where the webhook idempotency gap is\"\n\n```bash\ncat .commitshow\u002Faudit.json | jq '.concerns[] | select(.axis==\"Infrastructure\")'\n```\n\nFind the file path in the bullet, read it, confirm the gap matches.\n\n## Best Practices\n\n- ✅ Always cite the exact bullet from `concerns[].bullet` — they're already action-oriented\n- ✅ Lead with score + delta in a single sentence, then concerns\n- ✅ End with a specific follow-up question naming a concern\n- ✅ Read prior `.commitshow\u002Faudit.json` before re-running (within 1h)\n- ✅ Use `--refresh` after the user merges a fix so the next audit reflects it\n- ❌ Don't dump full JSON to the user\n- ❌ Don't list strengths unless the user explicitly asks\n- ❌ Don't apply fixes without approval — show diff first\n- ❌ Don't fault private repos for not auditing — explain why and suggest making public\n\n## Limitations\n\n- This skill does not replace environment-specific validation, testing, or expert review.\n- The audit engine is calibrated for **deployed apps** with a live URL. CLI \u002F library \u002F scaffold form gets a partial-substitute score (max ~45\u002F50 on the audit pillar) — fair but not flattering.\n- Behind a corporate firewall blocking `*.supabase.co`, the API call fails. There is no offline mode — the audit relies on the public engine.\n- Cold audit takes 60-90s. Cached audits (within 7 days) return instantly. `--refresh` force-bypasses cache (counts against rate limits).\n\n## Security & Safety Notes\n\n- The skill executes `npx commitshow@latest audit ...` which is a network call to a public API at `https:\u002F\u002Fapi.commit.show` (proxied to Supabase Edge Functions). No credentials are sent — anonymous usage subject to per-IP \u002F per-URL \u002F global rate limits.\n- The CLI writes `.commitshow\u002Faudit.{md,json}` in the current working directory. These files are safe to commit (no secrets) but conventionally gitignored as transient artifacts.\n- The audit engine **only reads** public GitHub signals. It does not modify the user's repo or push commits.\n- All per-finding fix proposals must be shown as diffs and approved by the user before any edit. Never apply without explicit confirmation.\n\n## Common Pitfalls\n\n- **Problem:** Audit returns `not_found` for a private repo\n  **Solution:** The engine pulls public GitHub signals only. Either make the repo public or use `--no-network` for local-only deterministic checks.\n\n- **Problem:** Rate limit hit (`429`)\n  **Solution:** Wait until next day (limits reset 00:00 UTC) or sign in at commit.show for higher per-repo caps.\n\n- **Problem:** Score seems too low for a polished library \u002F CLI\n  **Solution:** The engine biases toward app form. CLI \u002F library \u002F scaffold gets a partial substitute score capped around 45\u002F50 on the audit pillar. Calibration acknowledged trade-off.\n\n- **Problem:** `concerns[]` is empty after re-running\n  **Solution:** Re-audit may have hit cache. Use `--refresh` to force-bypass.\n\n## Related Skills\n\n- `@security-review` — In-session line-level security patterns. Run alongside this skill, not in place of.\n- `@vibesec` — Editor-buffer security review for vibe-coded projects. Different lens.\n- `@owasp-security` — OWASP Top 10 coverage during coding. Companion.\n- `@trail-of-bits-skills` — CodeQL \u002F Semgrep static analysis. Different layer.\n\n## Additional Resources\n\n- Canonical repo: \u003Chttps:\u002F\u002Fgithub.com\u002Fcommitshow\u002Fproduction-audit>\n- Audit engine source: \u003Chttps:\u002F\u002Fgithub.com\u002Fcommitshow\u002Fcommitshow\u002Fblob\u002Fmain\u002Fsupabase\u002Ffunctions\u002Fanalyze-project\u002Findex.ts>\n- 14-frame failure framework documented in the engine source above.\n- JSON schema: stable at `schema_version: \"1\"` · additive-only changes.\n- CLI: \u003Chttps:\u002F\u002Fgithub.com\u002Fcommitshow\u002Fcli>\n- Public REST API: `https:\u002F\u002Fapi.commit.show\u002Faudit?repo=...&format=json`\n- skills.sh listing: \u003Chttps:\u002F\u002Fskills.sh\u002Fcommitshow\u002Fproduction-audit>\n",{"name":5,"risk":24,"tags":25,"tools":35,"author":41,"source":42,"license":15,"category":26,"date_added":43,"description":7,"source_repo":44,"source_type":42,"license_source":45},"safe",[26,27,28,29,30,31,32,33,34],"security","audit","production","vibe-coding","rls","webhook","stripe","supabase","mobile",[36,37,38,39,40],"claude","cursor","gemini","codex","antigravity","commitshow","community","2026-05-04","commitshow\u002Fproduction-audit","https:\u002F\u002Fgithub.com\u002Fcommitshow\u002Fproduction-audit\u002Fblob\u002Fmain\u002FLICENSE","master","c247302c836de6438d746b45670990eb71691166","skills_collected\u002Fsickn33--antigravity-awesome-skills--skills__production-audit",1,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool","https:\u002F\u002Fgithub.com\u002Fqhjqhj00","chien.io","2026-05-11 15:07:59",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add qhjqhj00\u002Fresearch-skills-pool --skill production-audit",{"tool":60,"command":61},"bunx","bunx skills add qhjqhj00\u002Fresearch-skills-pool --skill production-audit",{"tool":63,"command":64},"pnpm","pnpm dlx skills add qhjqhj00\u002Fresearch-skills-pool --skill production-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fsickn33--antigravity-awesome-skills--skills__production-audit\u002FSKILL.md",true,[],[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M73JJB6EQPFPPVQK2Y9N67Q0","transformer-lens-interpretability","Provides guidance for mechanistic interpretability research using TransformerLens to inspect and manipulate transformer internals via HookPoints and activation caching. Use when reverse-engineering model algorithms, studying attention patterns, or performing activation patching experiments.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F130-transformer-lens\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M73JHTANRRWEE9HP98TPEHAY","wiki-vitepress","Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsable website from generated wiki pages.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F126-wiki-vitepress\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M73JHJBMVFW46F1Y8K3SBF43","phoenix-observability","Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F124-phoenix\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M73JHFPA3A2806PMP42ZN86Q","frontend-ui-dark-ts","Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F123-frontend-ui-dark-ts\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M73JFVBVK57NRJS49TT2VDCT","tensorboard","Visualize training metrics, debug models with histograms, compare experiments, visualize model graphs, and profile performance with TensorBoard - Google's ML visualization toolkit","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F113-tensorboard\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":108,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M73JFF6PK6ZCN41C89J7HS2B","markdown-mermaid-writing","Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F110-markdown-mermaid-writing\u002FSKILL.md",[],[]]