[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBFCPXECXWVBXSQNKGEPAN":3,"skill-same:01M7FBFCPXECXWVBXSQNKGEPAN":53},{"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7FBFCPXECXWVBXSQNKGEPAN","security-architecture-review",null,"Headcount enterprise security architecture review process for corporate systems, vendor integrations, and compliance sign-offs.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fsecurity-architecture-review\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: security-architecture-review\ndescription: \"Headcount enterprise security architecture review process for corporate systems, vendor integrations, and compliance sign-offs.\"\n---\n\n# Security architecture review\n\n## Review in this order\n\nAttention spent in this order finds the most consequential problems first.\n\n**1. Authentication.** How identity is established, how sessions are represented, how they expire,\nwhat happens on password reset and account recovery. Recovery flows are the most commonly weakest\npath into an account and the least reviewed.\n\n**2. Authorization.** The one that matters most and gets least attention. For every endpoint and\nevery object: who is allowed, and where is that checked? The characteristic failure is checking on\nthe way in but not on the object itself, so any authenticated user can reach any record by changing\nan identifier.\n\nCheck multi-tenant isolation explicitly and by test, not by reading. Assume every identifier in a\nrequest is attacker-controlled, because it is.\n\n**3. Data.** What is collected, where it goes, where it rests, and who can read it. Sensitive data\nin logs, in error responses, in analytics payloads, and in client bundles — all four are routine\nfindings.\n\n**4. Input and output.** Untrusted input reaching a query, a template, a command, a deserializer, or\na URL the server fetches. Parameterize rather than escape. Validate against an allowlist rather than\na denylist.\n\n**5. Secrets.** Never in source, never in client bundles, never in build logs. Rotatable, scoped to\nwhat needs them, and with a documented rotation path that someone has actually walked.\n\n**6. Dependencies and supply chain.** What is pulled in, how it is pinned, how updates are reviewed,\nand what would happen if a maintainer account were compromised. Lockfiles committed, builds\nreproducible.\n\n## Reviewing a change rather than a design\n\nLook for: new endpoints without an authorization check, new external input, changed authentication\nor session logic, new dependencies, anything touching cryptography, and anything that widens what a\nrole can do. Everything else is usually lower yield.\n\n**Never write your own cryptography.** Use the vetted primitives, and be suspicious of any diff that\nimplements a comparison, a token, or a signature by hand.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Tooling\n\n- **SAST** catches classes of bug cheaply and produces false positives at volume. Tune it or the\n  team will learn to ignore it, which is worse than not running it.\n- **DAST** and dependency scanning find different things; neither replaces review.\n- **Secret scanning in CI and pre-commit** is the highest-value automation per unit of effort.\n\nBy name today: Semgrep, CodeQL, or SonarQube for SAST; Snyk, Dependabot, or Trivy for\ndependencies; Burp Suite or OWASP ZAP for DAST; gitleaks, TruffleHog, or GitHub secret\nscanning for secrets — and similar in each category.\n\nAutomation is a floor, not a review. It finds known patterns, not design flaws — and design flaws\nare what actually cause the expensive incidents.\n\n## Third-party integrations\n\nWhat data leaves, under what agreement, with what access, and what happens if they are breached.\nScope credentials to the minimum, prefer short-lived tokens, and know how to revoke without an\noutage.\n\n## Never\n\n- Approve a design on the promise of a control with no named owner and no date.\n- Accept \"it is internal\" as an authorization boundary.\n- Review the diagram instead of the change. Read what is actually being built.\n- Sign off on a third-party integration without knowing what data leaves and under what terms.\n\n## Return contract\n\nFindings by severity, each with: the concrete attack, what the attacker gains, whether it blocks\nrelease, and the specific fix. A finding with no attack path stated is a preference.\n","# Security architecture review\n\n## Review in this order\n\nAttention spent in this order finds the most consequential problems first.\n\n**1. Authentication.** How identity is established, how sessions are represented, how they expire,\nwhat happens on password reset and account recovery. Recovery flows are the most commonly weakest\npath into an account and the least reviewed.\n\n**2. Authorization.** The one that matters most and gets least attention. For every endpoint and\nevery object: who is allowed, and where is that checked? The characteristic failure is checking on\nthe way in but not on the object itself, so any authenticated user can reach any record by changing\nan identifier.\n\nCheck multi-tenant isolation explicitly and by test, not by reading. Assume every identifier in a\nrequest is attacker-controlled, because it is.\n\n**3. Data.** What is collected, where it goes, where it rests, and who can read it. Sensitive data\nin logs, in error responses, in analytics payloads, and in client bundles — all four are routine\nfindings.\n\n**4. Input and output.** Untrusted input reaching a query, a template, a command, a deserializer, or\na URL the server fetches. Parameterize rather than escape. Validate against an allowlist rather than\na denylist.\n\n**5. Secrets.** Never in source, never in client bundles, never in build logs. Rotatable, scoped to\nwhat needs them, and with a documented rotation path that someone has actually walked.\n\n**6. Dependencies and supply chain.** What is pulled in, how it is pinned, how updates are reviewed,\nand what would happen if a maintainer account were compromised. Lockfiles committed, builds\nreproducible.\n\n## Reviewing a change rather than a design\n\nLook for: new endpoints without an authorization check, new external input, changed authentication\nor session logic, new dependencies, anything touching cryptography, and anything that widens what a\nrole can do. Everything else is usually lower yield.\n\n**Never write your own cryptography.** Use the vetted primitives, and be suspicious of any diff that\nimplements a comparison, a token, or a signature by hand.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Tooling\n\n- **SAST** catches classes of bug cheaply and produces false positives at volume. Tune it or the\n  team will learn to ignore it, which is worse than not running it.\n- **DAST** and dependency scanning find different things; neither replaces review.\n- **Secret scanning in CI and pre-commit** is the highest-value automation per unit of effort.\n\nBy name today: Semgrep, CodeQL, or SonarQube for SAST; Snyk, Dependabot, or Trivy for\ndependencies; Burp Suite or OWASP ZAP for DAST; gitleaks, TruffleHog, or GitHub secret\nscanning for secrets — and similar in each category.\n\nAutomation is a floor, not a review. It finds known patterns, not design flaws — and design flaws\nare what actually cause the expensive incidents.\n\n## Third-party integrations\n\nWhat data leaves, under what agreement, with what access, and what happens if they are breached.\nScope credentials to the minimum, prefer short-lived tokens, and know how to revoke without an\noutage.\n\n## Never\n\n- Approve a design on the promise of a control with no named owner and no date.\n- Accept \"it is internal\" as an authorization boundary.\n- Review the diagram instead of the change. Read what is actually being built.\n- Sign off on a third-party integration without knowing what data leaves and under what terms.\n\n## Return contract\n\nFindings by severity, each with: the concrete attack, what the attacker gains, whether it blocks\nrelease, and the specific fix. A finding with no attack path stated is a preference.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fsecurity-architecture-review",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add siddu1004\u002FSFP --skill security-architecture-review",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill security-architecture-review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill security-architecture-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fsecurity-architecture-review\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",2738,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fsecurity-architecture-review\u002Freferences\u002Fsources.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"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},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\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},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\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},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]