[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M788SBFY09QF52JQ8GCS7ST2":3,"skill-same:01M788SBFY09QF52JQ8GCS7ST2":47},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M788SBFY09QF52JQ8GCS7ST2","security-review-gate",null,"A governance gate — when a request touches credentials\u002Fsecrets, user data\u002FPII, network exposure, authentication, or infrastructure\u002FIAM, PAUSE and consult security standards BEFORE writing code or advising, and never emit insecure code even with a disclaimer. Use when a task involves secrets, auth, PII, security groups\u002Fpublic endpoints, file access\u002Fuploads, or IAM\u002Fcloud infrastructure.","jingchaodev\u002Fskills-lab","jingchaodev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8307474?v=4","01M788N3PES0P1DGEKSE9ZYDSD","chao","01M788N3QH1AYYGWKFG9XTX3WF",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjingchaodev\u002Fskills-lab\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-review-gate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: security-review-gate\ndescription: A governance gate — when a request touches credentials\u002Fsecrets, user data\u002FPII, network exposure, authentication, or infrastructure\u002FIAM, PAUSE and consult security standards BEFORE writing code or advising, and never emit insecure code even with a disclaimer. Use when a task involves secrets, auth, PII, security groups\u002Fpublic endpoints, file access\u002Fuploads, or IAM\u002Fcloud infrastructure.\n---\n\n# Security Review Gate\n\nA discipline, not a scanner: when a request enters a security-sensitive domain, you **stop, consult the relevant security standard, then act** — grounding your response in documented guidance rather than intuition alone.\n\n## Why This Exists\n\nYour security instinct is probably good — you already know hardcoded credentials are bad. But knowing the answer isn't the same as *consulting the standard*. Two things go wrong when you skip the pause:\n\n1. **You form an opinion the moment you read code.** Once you've read the implementation, you rationalize what's there instead of checking it against policy.\n2. **Your intuition has gaps.** You'll be confidently right about credentials and quietly wrong about, say, IAM trust-policy scoping or presigned-URL expiry.\n\nSo the query happens **because the domain fired**, not because something \"looked risky.\" It's a recognition trigger, not a judgment call.\n\n## Trigger Domains\n\nPause and consult standards when the request involves any of:\n\n- **Credentials \u002F secrets** — API keys, passwords, tokens, connection strings, private keys.\n- **User data \u002F PII** — personal data, authentication, sessions, database records.\n- **Network exposure** — security groups, ingress\u002Fegress rules, public endpoints, load balancers, CDN origins.\n- **Authentication \u002F authorization** — login flows, session management, authorizers, RBAC, permission checks.\n- **File access** — static file serving, uploads, user-controlled paths (path traversal).\n- **Infrastructure \u002F IAM** — IAM policies and roles, object-store bucket policies, compute permissions, VPC\u002Fsubnet exposure, encryption at rest, KMS\u002Fkey management, IaC (CDK\u002FCloudFormation\u002FTerraform) resources.\n\n## The Mandatory Flow\n\n**Do not examine the code before you consult the standard.** Reading code first means forming an opinion first.\n\n```\nWRONG:  request → grep\u002Fread code → answer from what you found\nRIGHT:  request → recognize trigger → consult standard → read standard →\n        THEN examine code → answer, citing the standard\n```\n\nSteps:\n1. See the request.\n2. Recognize the trigger domain (credentials, PII, network, auth, file access, infra).\n3. **First action: consult the security standard** — before any code examination.\n4. Read the applicable guidance thoroughly (not just a summary — get to the specific requirement).\n5. **Now** examine the code with your search\u002Fread tools.\n6. Form your approach from *standard + code context*.\n7. Respond, citing what the standard says.\n\nIf no relevant guidance exists, note that you checked, then apply standard secure-by-default practices. Don't invent policy that isn't there.\n\n## Where to Consult\n\nUse whatever authoritative source your context provides, in rough priority:\n\n1. **Your organization's security standards \u002F policy docs \u002F governance knowledge base** — the most authoritative and specific. If a dedicated security-guidance search tool or knowledge base is available, that's the first stop.\n2. **Cloud provider security guidance** — the well-architected security pillar, service-specific security best-practices pages, IAM policy guidance.\n3. **Established public standards** — OWASP (Top 10, ASVS, Cheat Sheet Series) for app security; CIS Benchmarks for infrastructure hardening.\n\nCite what you consulted: *\"Guidance on credential storage indicates…\"*, *\"The standard for public bucket policies specifies…\"*, *\"Per OWASP's path-traversal guidance…\"* This grounds the response in documented policy, not vibes.\n\n## The Non-Negotiable Rule: No Insecure Code\n\n**Do not generate insecure code, even with a warning.** If the standard says a pattern violates policy, provide *only* the secure alternative.\n\n- Wrong: \"Here's the insecure version you asked for, but I'd recommend…\"\n- Right: \"I can't generate that configuration. Here's a secure version that achieves the same goal…\"\n\nThe user can modify your output if they choose — but you shouldn't be the author of the insecure version.\n\n## When Users Push Back\n\nUsers sometimes want to skip security \"just to test something.\" Your job doesn't change:\n\n1. The trigger still fired, so you still consult the standard.\n2. Share what the guidance says, plainly.\n3. Offer a compliant alternative that achieves their actual goal.\n4. Help them get there *within* policy.\n\nMeet the underlying need (fast iteration, a working prototype) with a secure path — a local secret store instead of a hardcoded key, a scoped-down role instead of a wildcard, a signed short-lived URL instead of a public bucket.\n\n## Quick Reference: Common Traps → Secure Default\n\n| Domain | Insecure ask | Secure alternative |\n|--------|--------------|--------------------|\n| Credentials | Hardcode key in source\u002Fconfig | Secret manager \u002F env injection; never in the repo |\n| Auth | Roll your own token\u002Fsession check | Vetted library; short-lived tokens; server-side validation |\n| Network | `0.0.0.0\u002F0` ingress \"to unblock\" | Scope to known CIDRs \u002F security groups; private + bastion\u002FVPN |\n| IAM | `Action: \"*\"` \u002F `Resource: \"*\"` | Least privilege: enumerate exact actions and ARNs |\n| Storage | Public bucket for \"easy access\" | Private bucket + presigned short-lived URLs |\n| File access | Serve `basePath + userInput` | Canonicalize and confirm the path stays within an allowlisted root |\n| Data at rest | Skip encryption \"for now\" | Encryption on by default; managed keys unless a reason not to |\n\n## Tips\n- **The trigger is the domain, not the danger.** You consult because it's credentials\u002Fauth\u002Finfra — not because it \"seemed\" risky.\n- **Consult before you read code.** Once you've read the implementation you'll defend it; check the standard first.\n- **Cite the source.** Grounding beats intuition and makes the guidance auditable.\n- **Never author the insecure version.** Provide the secure alternative, full stop.\n- **Push-back doesn't skip the gate** — it changes your job to finding the compliant path to their goal.\n- **No guidance found? Say so, then secure-by-default.** Don't fabricate policy.\n","# Security Review Gate\n\nA discipline, not a scanner: when a request enters a security-sensitive domain, you **stop, consult the relevant security standard, then act** — grounding your response in documented guidance rather than intuition alone.\n\n## Why This Exists\n\nYour security instinct is probably good — you already know hardcoded credentials are bad. But knowing the answer isn't the same as *consulting the standard*. Two things go wrong when you skip the pause:\n\n1. **You form an opinion the moment you read code.** Once you've read the implementation, you rationalize what's there instead of checking it against policy.\n2. **Your intuition has gaps.** You'll be confidently right about credentials and quietly wrong about, say, IAM trust-policy scoping or presigned-URL expiry.\n\nSo the query happens **because the domain fired**, not because something \"looked risky.\" It's a recognition trigger, not a judgment call.\n\n## Trigger Domains\n\nPause and consult standards when the request involves any of:\n\n- **Credentials \u002F secrets** — API keys, passwords, tokens, connection strings, private keys.\n- **User data \u002F PII** — personal data, authentication, sessions, database records.\n- **Network exposure** — security groups, ingress\u002Fegress rules, public endpoints, load balancers, CDN origins.\n- **Authentication \u002F authorization** — login flows, session management, authorizers, RBAC, permission checks.\n- **File access** — static file serving, uploads, user-controlled paths (path traversal).\n- **Infrastructure \u002F IAM** — IAM policies and roles, object-store bucket policies, compute permissions, VPC\u002Fsubnet exposure, encryption at rest, KMS\u002Fkey management, IaC (CDK\u002FCloudFormation\u002FTerraform) resources.\n\n## The Mandatory Flow\n\n**Do not examine the code before you consult the standard.** Reading code first means forming an opinion first.\n\n```\nWRONG:  request → grep\u002Fread code → answer from what you found\nRIGHT:  request → recognize trigger → consult standard → read standard →\n        THEN examine code → answer, citing the standard\n```\n\nSteps:\n1. See the request.\n2. Recognize the trigger domain (credentials, PII, network, auth, file access, infra).\n3. **First action: consult the security standard** — before any code examination.\n4. Read the applicable guidance thoroughly (not just a summary — get to the specific requirement).\n5. **Now** examine the code with your search\u002Fread tools.\n6. Form your approach from *standard + code context*.\n7. Respond, citing what the standard says.\n\nIf no relevant guidance exists, note that you checked, then apply standard secure-by-default practices. Don't invent policy that isn't there.\n\n## Where to Consult\n\nUse whatever authoritative source your context provides, in rough priority:\n\n1. **Your organization's security standards \u002F policy docs \u002F governance knowledge base** — the most authoritative and specific. If a dedicated security-guidance search tool or knowledge base is available, that's the first stop.\n2. **Cloud provider security guidance** — the well-architected security pillar, service-specific security best-practices pages, IAM policy guidance.\n3. **Established public standards** — OWASP (Top 10, ASVS, Cheat Sheet Series) for app security; CIS Benchmarks for infrastructure hardening.\n\nCite what you consulted: *\"Guidance on credential storage indicates…\"*, *\"The standard for public bucket policies specifies…\"*, *\"Per OWASP's path-traversal guidance…\"* This grounds the response in documented policy, not vibes.\n\n## The Non-Negotiable Rule: No Insecure Code\n\n**Do not generate insecure code, even with a warning.** If the standard says a pattern violates policy, provide *only* the secure alternative.\n\n- Wrong: \"Here's the insecure version you asked for, but I'd recommend…\"\n- Right: \"I can't generate that configuration. Here's a secure version that achieves the same goal…\"\n\nThe user can modify your output if they choose — but you shouldn't be the author of the insecure version.\n\n## When Users Push Back\n\nUsers sometimes want to skip security \"just to test something.\" Your job doesn't change:\n\n1. The trigger still fired, so you still consult the standard.\n2. Share what the guidance says, plainly.\n3. Offer a compliant alternative that achieves their actual goal.\n4. Help them get there *within* policy.\n\nMeet the underlying need (fast iteration, a working prototype) with a secure path — a local secret store instead of a hardcoded key, a scoped-down role instead of a wildcard, a signed short-lived URL instead of a public bucket.\n\n## Quick Reference: Common Traps → Secure Default\n\n| Domain | Insecure ask | Secure alternative |\n|--------|--------------|--------------------|\n| Credentials | Hardcode key in source\u002Fconfig | Secret manager \u002F env injection; never in the repo |\n| Auth | Roll your own token\u002Fsession check | Vetted library; short-lived tokens; server-side validation |\n| Network | `0.0.0.0\u002F0` ingress \"to unblock\" | Scope to known CIDRs \u002F security groups; private + bastion\u002FVPN |\n| IAM | `Action: \"*\"` \u002F `Resource: \"*\"` | Least privilege: enumerate exact actions and ARNs |\n| Storage | Public bucket for \"easy access\" | Private bucket + presigned short-lived URLs |\n| File access | Serve `basePath + userInput` | Canonicalize and confirm the path stays within an allowlisted root |\n| Data at rest | Skip encryption \"for now\" | Encryption on by default; managed keys unless a reason not to |\n\n## Tips\n- **The trigger is the domain, not the danger.** You consult because it's credentials\u002Fauth\u002Finfra — not because it \"seemed\" risky.\n- **Consult before you read code.** Once you've read the implementation you'll defend it; check the standard first.\n- **Cite the source.** Grounding beats intuition and makes the guidance auditable.\n- **Never author the insecure version.** Provide the secure alternative, full stop.\n- **Push-back doesn't skip the gate** — it changes your job to finding the compliant path to their goal.\n- **No guidance found? Say so, then secure-by-default.** Don't fabricate policy.\n",{"name":5,"description":7},"main","44b1acb2c22ab1e94663691dda7d7739f1b83cf6","skills\u002Fsecurity-review-gate",0,"https:\u002F\u002Fgithub.com\u002Fjingchaodev\u002Fskills-lab","https:\u002F\u002Fgithub.com\u002Fjingchaodev","https:\u002F\u002Fx.com\u002Fcifra1902","Developer","2026-07-13 09:03:55",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jingchaodev\u002Fskills-lab --skill security-review-gate",{"tool":39,"command":40},"bunx","bunx skills add jingchaodev\u002Fskills-lab --skill security-review-gate",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jingchaodev\u002Fskills-lab --skill security-review-gate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjingchaodev\u002Fskills-lab\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-review-gate\u002FSKILL.md",true,[],[48,55,62,69,75,82],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M788VYAVHEH5QAV7T1Z8QFV9","default-skill","Valid default cwd skill.","https:\u002F\u002Fgithub.com\u002Fjingchaodev\u002Fskills-lab\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fdefault_cwd\u002Fskills\u002Fdefault-skill\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"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":19},"01M788VVHF3TC2RY65NVPR26DN","clean-two","Another valid skill with a quoted trigger phrase \"specific action\".","https:\u002F\u002Fgithub.com\u002Fjingchaodev\u002Fskills-lab\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fclean_skills\u002Fclean-two\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":19},"01M788VRPGJXZ09X9AM1ZPNAHA","clean-one","Use when the user needs a clean example.","https:\u002F\u002Fgithub.com\u002Fjingchaodev\u002Fskills-lab\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fclean_skills\u002Fclean-one\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M788VPP8BFKCBXDFRHMP67WH","wrong-frontmatter","https:\u002F\u002Fgithub.com\u002Fjingchaodev\u002Fskills-lab\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad_skills\u002Fwrong-frontmatter\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M788VKP781ZRGKXVMHZFR062","trigger-two","Use for the exact phrase \"panic button\".","https:\u002F\u002Fgithub.com\u002Fjingchaodev\u002Fskills-lab\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad_skills\u002Ftrigger-two\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M788VJBR5Q14W6MJB2DWRSVE","trigger-one","Use when someone says \"panic button\".","https:\u002F\u002Fgithub.com\u002Fjingchaodev\u002Fskills-lab\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad_skills\u002Ftrigger-one\u002FSKILL.md",[],[]]