[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EQNHVB9DWAZGG2Y198VGCM":3,"skill-same:01M7EQNHVB9DWAZGG2Y198VGCM":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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7EQNHVB9DWAZGG2Y198VGCM","production-audit",null,"Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and \"what breaks in prod?\" questions without sending repo data to an external audit service. Use when auditing production readiness before launch, after a merge, or when asked what breaks in prod.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fproduction-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: production-audit\ndescription: Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and \"what breaks in prod?\" questions without sending repo data to an external audit service. Use when auditing production readiness before launch, after a merge, or when asked what breaks in prod.\nmetadata:\n  origin: community\n---\n\n# Production Audit\n\nUse this skill when the user asks whether an application is ready to ship, what\ncould break in production, or what must be fixed before a launch. This is a\nmaintainer-safe rewrite of the stale community production-audit idea: it keeps\nthe useful production-readiness lens and removes unpinned external execution and\nthird-party data sharing.\n\n## When to Use\n\n- The user asks \"is this production-ready\", \"what would break in prod\", \"what\n  did we miss\", \"audit this repo\", or \"ready to ship?\"\n- A feature was merged and needs a pre-deploy or post-merge risk pass.\n- A public launch, demo, customer rollout, or investor walkthrough is close.\n- CI is green but the user wants production risk, not only test status.\n- A deployed URL, release branch, PR, or current checkout is available for\n  evidence gathering.\n\n## When Not to Use\n\n- During active implementation when the right lens is line-level secure coding;\n  use `security-review` first.\n- For pure libraries, templates, docs-only repos, or scaffolds unless the user\n  wants packaging\u002Frelease readiness rather than application readiness.\n- When the user asks for a formal compliance audit. This skill is engineering\n  triage, not legal, financial, medical, or regulatory certification.\n- When the only available evidence is a product idea with no repo, deployment,\n  CI, or runtime surface.\n\n## How It Works\n\nBuild the audit from local and user-authorized evidence. Do not run unpinned\nremote code, upload repository contents to third-party services, or call\nexternal scanners unless the user explicitly approves that specific tool and\ndata flow.\n\nUse this order:\n\n1. Establish the release surface.\n2. Read recent changes and current branch state.\n3. Inspect runtime, auth, data, payment, background-job, AI, and deployment\n   boundaries that actually exist in the repo.\n4. Check CI, tests, migrations, environment documentation, and rollback path.\n5. Produce a short ship\u002Fblock recommendation with specific fixes.\n\n## Evidence Checklist\n\nStart with cheap, local signals:\n\n```text\ngit status --short --branch\ngit log --oneline --decorate -20\ngit diff --stat origin\u002Fmain...HEAD\n```\n\nThen inspect the project-specific surface:\n\n- Package scripts, CI workflows, release scripts, Docker files, and deployment\n  manifests.\n- API routes, webhooks, auth middleware, background workers, cron jobs, and\n  database migrations.\n- Environment variable documentation and startup checks.\n- Observability hooks, error reporting, logs, health checks, and dashboards.\n- Rollback, seed, migration, and backfill instructions.\n- E2E coverage for the user paths that matter most.\n\nIf a deployed URL is in scope, use browser or HTTP checks only against that URL\nand avoid credentialed actions unless the user supplies a safe test account.\n\n## Risk Lenses\n\n### Security And Auth\n\n- Are public routes, API routes, and admin routes clearly separated?\n- Are auth and authorization enforced server-side?\n- Are secrets kept out of client bundles, logs, example output, and checked-in\n  files?\n- Are rate limits, CSRF protections, CORS policy, and upload validation present\n  where the app needs them?\n- Does the AI or agent surface defend against prompt injection, tool abuse, and\n  untrusted content crossing into privileged actions?\n\n### Data Integrity\n\n- Do migrations run forward cleanly and have a rollback or recovery plan?\n- Are destructive migrations, backfills, and data imports staged safely?\n- Do database policies, grants, and service-role boundaries match the app's\n  tenancy model?\n- Are retries idempotent for writes, jobs, and webhook handlers?\n\n### Payments And Webhooks\n\n- Are webhook signatures verified before parsing trusted payload fields?\n- Is each payment, subscription, or fulfillment webhook idempotent?\n- Are replay, duplicate delivery, and out-of-order delivery handled?\n- Are test-mode and live-mode credentials separated?\n\n### Operations\n\n- Can the app start from a clean checkout using documented commands?\n- Are required environment variables named, validated, and fail-fast?\n- Is there a health check that proves dependencies are reachable?\n- Are deploy, rollback, and incident-owner paths documented?\n- Are logs useful without leaking secrets or personal data?\n\n### User Experience\n\n- Are the launch-critical paths covered on desktop and mobile?\n- Are forms usable on mobile without input zoom, layout overlap, or blocked\n  submission states?\n- Do loading, empty, error, and permission-denied states tell the user what\n  happened?\n- Is there a support or recovery path when a critical operation fails?\n\n## Scoring\n\nUse scores to force prioritization, not to imply mathematical certainty.\n\n| Band | Score | Meaning |\n| --- | --- | --- |\n| Blocked | 0-49 | Do not ship until the top risks are fixed |\n| Risky | 50-69 | Ship only behind a small rollout or internal beta |\n| Launchable With Caveats | 70-84 | Ship if owners accept the listed risks |\n| Strong | 85-100 | No obvious launch blockers from available evidence |\n\nCap the score at `69` if any of these are true:\n\n- Authentication or authorization is missing on sensitive data.\n- Payment or fulfillment webhooks are not idempotent.\n- Required migrations cannot be run safely.\n- Secrets are exposed in client bundles, logs, or committed files.\n- There is no rollback path for a high-impact release.\n\nCap the score at `84` if CI is not green or the launch-critical path was not\ntested end to end.\n\n## Output Format\n\nLead with one sentence:\n\n```text\nProduction audit: 76\u002F100, launchable with caveats, with webhook idempotency and rollback docs as the two risks to fix before public launch.\n```\n\nThen list:\n\n- `Blockers`: must-fix items before deploy.\n- `High-value fixes`: next fixes if the user wants to improve the score.\n- `Evidence checked`: files, commands, CI, deployed URL, or PRs inspected.\n- `Evidence missing`: what would change confidence if provided.\n- `Next action`: one concrete fix or verification step.\n\nKeep strengths short. The user asked for readiness, so the useful answer is the\nremaining risk and the next action.\n\n## Example\n\nUser:\n\n```text\nis this ready to ship?\n```\n\nResponse:\n\n```text\nProduction audit: 68\u002F100, risky, because Stripe webhooks are verified but not idempotent and there is no rollback note for the pending migration.\n\nBlockers:\n- Add idempotency for `checkout.session.completed` before fulfilling orders.\n- Write and test the rollback path for `20260511_add_billing_state.sql`.\n\nHigh-value fixes:\n- Add a health check that verifies database and payment-provider reachability.\n- Add one E2E path for upgrade, webhook fulfillment, and billing-page refresh.\n\nEvidence checked:\n- `api\u002Fstripe\u002Fwebhook.ts`\n- `db\u002Fmigrations\u002F20260511_add_billing_state.sql`\n- GitHub Actions run for the release branch\n\nNext action: Want me to patch webhook idempotency first?\n```\n\n## Anti-Patterns\n\n- Running `npx \u003Cpackage>@latest` or a remote scanner as the default audit path.\n- Uploading source, secrets, customer data, or private topology to an external\n  audit service without explicit approval.\n- Producing a score without naming the evidence checked.\n- Treating green CI as production readiness.\n- Ending with a generic \"let me know what you want to do.\"\n\n## See Also\n\n- Skill: `security-review`\n- Skill: `deployment-patterns`\n- Skill: `e2e-testing`\n- Skill: `tdd-workflow`\n- Skill: `verification-loop`\n","# Production Audit\n\nUse this skill when the user asks whether an application is ready to ship, what\ncould break in production, or what must be fixed before a launch. This is a\nmaintainer-safe rewrite of the stale community production-audit idea: it keeps\nthe useful production-readiness lens and removes unpinned external execution and\nthird-party data sharing.\n\n## When to Use\n\n- The user asks \"is this production-ready\", \"what would break in prod\", \"what\n  did we miss\", \"audit this repo\", or \"ready to ship?\"\n- A feature was merged and needs a pre-deploy or post-merge risk pass.\n- A public launch, demo, customer rollout, or investor walkthrough is close.\n- CI is green but the user wants production risk, not only test status.\n- A deployed URL, release branch, PR, or current checkout is available for\n  evidence gathering.\n\n## When Not to Use\n\n- During active implementation when the right lens is line-level secure coding;\n  use `security-review` first.\n- For pure libraries, templates, docs-only repos, or scaffolds unless the user\n  wants packaging\u002Frelease readiness rather than application readiness.\n- When the user asks for a formal compliance audit. This skill is engineering\n  triage, not legal, financial, medical, or regulatory certification.\n- When the only available evidence is a product idea with no repo, deployment,\n  CI, or runtime surface.\n\n## How It Works\n\nBuild the audit from local and user-authorized evidence. Do not run unpinned\nremote code, upload repository contents to third-party services, or call\nexternal scanners unless the user explicitly approves that specific tool and\ndata flow.\n\nUse this order:\n\n1. Establish the release surface.\n2. Read recent changes and current branch state.\n3. Inspect runtime, auth, data, payment, background-job, AI, and deployment\n   boundaries that actually exist in the repo.\n4. Check CI, tests, migrations, environment documentation, and rollback path.\n5. Produce a short ship\u002Fblock recommendation with specific fixes.\n\n## Evidence Checklist\n\nStart with cheap, local signals:\n\n```text\ngit status --short --branch\ngit log --oneline --decorate -20\ngit diff --stat origin\u002Fmain...HEAD\n```\n\nThen inspect the project-specific surface:\n\n- Package scripts, CI workflows, release scripts, Docker files, and deployment\n  manifests.\n- API routes, webhooks, auth middleware, background workers, cron jobs, and\n  database migrations.\n- Environment variable documentation and startup checks.\n- Observability hooks, error reporting, logs, health checks, and dashboards.\n- Rollback, seed, migration, and backfill instructions.\n- E2E coverage for the user paths that matter most.\n\nIf a deployed URL is in scope, use browser or HTTP checks only against that URL\nand avoid credentialed actions unless the user supplies a safe test account.\n\n## Risk Lenses\n\n### Security And Auth\n\n- Are public routes, API routes, and admin routes clearly separated?\n- Are auth and authorization enforced server-side?\n- Are secrets kept out of client bundles, logs, example output, and checked-in\n  files?\n- Are rate limits, CSRF protections, CORS policy, and upload validation present\n  where the app needs them?\n- Does the AI or agent surface defend against prompt injection, tool abuse, and\n  untrusted content crossing into privileged actions?\n\n### Data Integrity\n\n- Do migrations run forward cleanly and have a rollback or recovery plan?\n- Are destructive migrations, backfills, and data imports staged safely?\n- Do database policies, grants, and service-role boundaries match the app's\n  tenancy model?\n- Are retries idempotent for writes, jobs, and webhook handlers?\n\n### Payments And Webhooks\n\n- Are webhook signatures verified before parsing trusted payload fields?\n- Is each payment, subscription, or fulfillment webhook idempotent?\n- Are replay, duplicate delivery, and out-of-order delivery handled?\n- Are test-mode and live-mode credentials separated?\n\n### Operations\n\n- Can the app start from a clean checkout using documented commands?\n- Are required environment variables named, validated, and fail-fast?\n- Is there a health check that proves dependencies are reachable?\n- Are deploy, rollback, and incident-owner paths documented?\n- Are logs useful without leaking secrets or personal data?\n\n### User Experience\n\n- Are the launch-critical paths covered on desktop and mobile?\n- Are forms usable on mobile without input zoom, layout overlap, or blocked\n  submission states?\n- Do loading, empty, error, and permission-denied states tell the user what\n  happened?\n- Is there a support or recovery path when a critical operation fails?\n\n## Scoring\n\nUse scores to force prioritization, not to imply mathematical certainty.\n\n| Band | Score | Meaning |\n| --- | --- | --- |\n| Blocked | 0-49 | Do not ship until the top risks are fixed |\n| Risky | 50-69 | Ship only behind a small rollout or internal beta |\n| Launchable With Caveats | 70-84 | Ship if owners accept the listed risks |\n| Strong | 85-100 | No obvious launch blockers from available evidence |\n\nCap the score at `69` if any of these are true:\n\n- Authentication or authorization is missing on sensitive data.\n- Payment or fulfillment webhooks are not idempotent.\n- Required migrations cannot be run safely.\n- Secrets are exposed in client bundles, logs, or committed files.\n- There is no rollback path for a high-impact release.\n\nCap the score at `84` if CI is not green or the launch-critical path was not\ntested end to end.\n\n## Output Format\n\nLead with one sentence:\n\n```text\nProduction audit: 76\u002F100, launchable with caveats, with webhook idempotency and rollback docs as the two risks to fix before public launch.\n```\n\nThen list:\n\n- `Blockers`: must-fix items before deploy.\n- `High-value fixes`: next fixes if the user wants to improve the score.\n- `Evidence checked`: files, commands, CI, deployed URL, or PRs inspected.\n- `Evidence missing`: what would change confidence if provided.\n- `Next action`: one concrete fix or verification step.\n\nKeep strengths short. The user asked for readiness, so the useful answer is the\nremaining risk and the next action.\n\n## Example\n\nUser:\n\n```text\nis this ready to ship?\n```\n\nResponse:\n\n```text\nProduction audit: 68\u002F100, risky, because Stripe webhooks are verified but not idempotent and there is no rollback note for the pending migration.\n\nBlockers:\n- Add idempotency for `checkout.session.completed` before fulfilling orders.\n- Write and test the rollback path for `20260511_add_billing_state.sql`.\n\nHigh-value fixes:\n- Add a health check that verifies database and payment-provider reachability.\n- Add one E2E path for upgrade, webhook fulfillment, and billing-page refresh.\n\nEvidence checked:\n- `api\u002Fstripe\u002Fwebhook.ts`\n- `db\u002Fmigrations\u002F20260511_add_billing_state.sql`\n- GitHub Actions run for the release branch\n\nNext action: Want me to patch webhook idempotency first?\n```\n\n## Anti-Patterns\n\n- Running `npx \u003Cpackage>@latest` or a remote scanner as the default audit path.\n- Uploading source, secrets, customer data, or private topology to an external\n  audit service without explicit approval.\n- Producing a score without naming the evidence checked.\n- Treating green CI as production readiness.\n- Ending with a generic \"let me know what you want to do.\"\n\n## See Also\n\n- Skill: `security-review`\n- Skill: `deployment-patterns`\n- Skill: `e2e-testing`\n- Skill: `tdd-workflow`\n- Skill: `verification-loop`\n",{"name":5,"metadata":24,"description":7},{"origin":25},"community","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fproduction-audit",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill production-audit",{"tool":40,"command":41},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill production-audit",{"tool":43,"command":44},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill production-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fproduction-audit\u002FSKILL.md",true,[],[49,57,62,69,76,83],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":58,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":56},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":56},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"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":56},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\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":56},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\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":56},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]