[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DEXX7DWAVW71JS826RJ2MH":3,"skill-same:01M7DEXX7DWAVW71JS826RJ2MH":51},{"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":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7DEXX7DWAVW71JS826RJ2MH","security-review",null,"Review a change for risks to trust boundaries, input handling, access control, secrets, sensitive data or dependencies. Use when a change affects input, authorization, data exposure, security configuration or dependencies; use threat-modeling for a design before it is built.","andersonmrodrigues\u002Fpaved","andersonmrodrigues","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13907380?v=4","01M7DEV3FP2VMQZ3FP2FP1TK1C","Anderson Rodrigues","01M7DEV3GC2QAQBW4FMNT98H48",1,"MIT","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fsecurity\u002Fsecurity-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: security-review\ndescription: >-\n  Review a change for risks to trust boundaries, input handling, access control, secrets, sensitive data or dependencies. Use when a change affects input, authorization, data exposure, security configuration or dependencies; use threat-modeling for a design before it is built.\n---\n\n# Security review\n\n## When to use\n\nIn the `review` phase of any change that touches external input, access control,\npersistence of sensitive data, logging, configuration, dependencies or infrastructure.\nWhen the change adds a new component, interface or data flow, run `threat-modeling`\nfirst: a review checks the code against threats someone has named.\n\n## Required context\n\nNone is required. Useful: the integrations and architecture context that identify trust\nboundaries (what is external, who calls what), and project security rules.\n\n## Preconditions\n\nThe diff is final enough to review.\n\n## Procedure\n\n1. **List the trust boundaries** the change touches: where data enters from users, other\n   services, files, queues or configuration.\n2. **Check each entry point**: input is validated at the boundary, and output is encoded\n   for its destination (queries, markup, commands, file paths, logs).\n3. **Check authentication and authorization** on every new or changed operation. A\n   missing check is a finding even if \"the interface does not expose it\".\n4. **Check secrets and sensitive data**: nothing written to code, logs, errors, evidence\n   or test data; nothing returned to a caller who should not see it.\n5. **Check new dependencies**: why they are needed, where they come from, whether they\n   are maintained, and whether they bring known vulnerabilities.\n6. **Check failure behavior**: errors do not leak internals, and a failed security check\n   denies rather than allows.\n7. **Run the security checks** the profile has.\n8. **Trace each candidate** from source to sink before calling it a finding: name the\n   untrusted source, the path it takes through the changed code and the sink it\n   reaches, and confirm no guard on that path already stops it. A candidate with no\n   nameable source, or one stopped by an existing guard, is dropped; one the diff did not\n   introduce is raised separately, not recorded here. When the agent can, have a\n   separate pass re-trace each finding from the code.\n9. **Record each finding so its owner can act on it in one read:** state what the code currently does, the concrete impact, the suggested correction, and the consequence of leaving it as-is. Include severity, the boundary and traced path. Keep hardening ideas without a traced path in notes.\n   Hardening ideas that no traced path demands are notes, kept apart from findings.\n   Fix what is in scope; raise what is not. With no finding, list the boundaries\n   examined and why each holds.\n\n## Tools\n\n`core.repository.diff` to review exactly what changed.\n\n## Rules\n\n`core.security.no-secrets-in-source` always; project security rules by scope.\n\n## Verification\n\nRequired: `security` — a security check when the profile has one, otherwise a gap\nstating that only the manual review below was done. Recommended: `static-analysis`.\n\n## Evidence\n\nA review artifact listing the boundaries examined and the findings. An agent-recorded\nreview supports no claim by itself; it tells the human reviewer where to look.\n\n## Completion criteria\n\n- Every touched boundary was examined and is listed in the review.\n- Every finding carries a traced source-to-sink path.\n- No unresolved finding of high severity remains in scope.\n\n## Failure modes\n\n| Failure | Signal | Response |\n|---|---|---|\n| Review of intent, not code | Findings describe what the code should do | Re-read the diff |\n| Trusting internal callers | \"Only called internally\" with no enforcement | Treat as a boundary or record the assumption |\n| Scanner as the review | Only tool output is reported | Walk steps 1 to 6 as well |\n| Theoretical finding | No source, path or sink can be named for it | Trace it (step 8) or turn it into a note |\n\n## References\n\nNone.\n","# Security review\n\n## When to use\n\nIn the `review` phase of any change that touches external input, access control,\npersistence of sensitive data, logging, configuration, dependencies or infrastructure.\nWhen the change adds a new component, interface or data flow, run `threat-modeling`\nfirst: a review checks the code against threats someone has named.\n\n## Required context\n\nNone is required. Useful: the integrations and architecture context that identify trust\nboundaries (what is external, who calls what), and project security rules.\n\n## Preconditions\n\nThe diff is final enough to review.\n\n## Procedure\n\n1. **List the trust boundaries** the change touches: where data enters from users, other\n   services, files, queues or configuration.\n2. **Check each entry point**: input is validated at the boundary, and output is encoded\n   for its destination (queries, markup, commands, file paths, logs).\n3. **Check authentication and authorization** on every new or changed operation. A\n   missing check is a finding even if \"the interface does not expose it\".\n4. **Check secrets and sensitive data**: nothing written to code, logs, errors, evidence\n   or test data; nothing returned to a caller who should not see it.\n5. **Check new dependencies**: why they are needed, where they come from, whether they\n   are maintained, and whether they bring known vulnerabilities.\n6. **Check failure behavior**: errors do not leak internals, and a failed security check\n   denies rather than allows.\n7. **Run the security checks** the profile has.\n8. **Trace each candidate** from source to sink before calling it a finding: name the\n   untrusted source, the path it takes through the changed code and the sink it\n   reaches, and confirm no guard on that path already stops it. A candidate with no\n   nameable source, or one stopped by an existing guard, is dropped; one the diff did not\n   introduce is raised separately, not recorded here. When the agent can, have a\n   separate pass re-trace each finding from the code.\n9. **Record each finding so its owner can act on it in one read:** state what the code currently does, the concrete impact, the suggested correction, and the consequence of leaving it as-is. Include severity, the boundary and traced path. Keep hardening ideas without a traced path in notes.\n   Hardening ideas that no traced path demands are notes, kept apart from findings.\n   Fix what is in scope; raise what is not. With no finding, list the boundaries\n   examined and why each holds.\n\n## Tools\n\n`core.repository.diff` to review exactly what changed.\n\n## Rules\n\n`core.security.no-secrets-in-source` always; project security rules by scope.\n\n## Verification\n\nRequired: `security` — a security check when the profile has one, otherwise a gap\nstating that only the manual review below was done. Recommended: `static-analysis`.\n\n## Evidence\n\nA review artifact listing the boundaries examined and the findings. An agent-recorded\nreview supports no claim by itself; it tells the human reviewer where to look.\n\n## Completion criteria\n\n- Every touched boundary was examined and is listed in the review.\n- Every finding carries a traced source-to-sink path.\n- No unresolved finding of high severity remains in scope.\n\n## Failure modes\n\n| Failure | Signal | Response |\n|---|---|---|\n| Review of intent, not code | Findings describe what the code should do | Re-read the diff |\n| Trusting internal callers | \"Only called internally\" with no enforcement | Treat as a boundary or record the assumption |\n| Scanner as the review | Only tool output is reported | Walk steps 1 to 6 as well |\n| Theoretical finding | No source, path or sink can be named for it | Trace it (step 8) or turn it into a note |\n\n## References\n\nNone.\n",{"name":5,"description":7},"main","1cd80f05aff924ea609012e864fa5c22c16c7d2d","core\u002Fskills\u002Fsecurity\u002Fsecurity-review",0,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues","2026-11-14 20:09:28",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add andersonmrodrigues\u002Fpaved --skill security-review",{"tool":37,"command":38},"bunx","bunx skills add andersonmrodrigues\u002Fpaved --skill security-review",{"tool":40,"command":41},"pnpm","pnpm dlx skills add andersonmrodrigues\u002Fpaved --skill security-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fsecurity\u002Fsecurity-review\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"skill.yaml","REFERENCE","参考文档",437,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fsecurity\u002Fsecurity-review\u002Fskill.yaml",[52,59,65,71,77,83],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7DFBWJT4T1MPBHTWT19PBEK","sample-skill","Does a sample task. Use when a sample is needed.","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fvalid\u002Fsample-skill\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":55,"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},"01M7DFBS6WTK30PBSW4ZS0NPWT","unexplained-contract","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Funexplained-contract\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7DFBPJGG170V9WTMFWY73R4","shell-block","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fshell-block\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7DFBMZYR20JPTXNE5A8EFG6","project-identifier","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fproject-identifier\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":55,"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},"01M7DFBJ8J533DAKA3FTF54SX3","oversized","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Foversized\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},"01M7DFBFAD0RYCRHTZ2JW4RX7E","no-activation","Does a sample task.","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fno-activation\u002FSKILL.md",[],[]]