[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAZVTC50WSA68RSM09NBXM":3,"skill-same:01M7FAZVTC50WSA68RSM09NBXM":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},"01M7FAZVTC50WSA68RSM09NBXM","enterprise-risk",null,"Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, and preparing for audit. Use this to stand up a risk program, assess the risk in a decision or initiative, prepare for a certification or audit, decide whether a risk should be accepted, mitigated, transferred, or avoided, or report risk posture to leadership.","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\u002Fenterprise-risk\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: enterprise-risk\ndescription: Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, and preparing for audit. Use this to stand up a risk program, assess the risk in a decision or initiative, prepare for a certification or audit, decide whether a risk should be accepted, mitigated, transferred, or avoided, or report risk posture to leadership.\n---\n\n# Enterprise risk\n\n## The register is the artifact\n\nA risk that is not written down with an owner is not managed. Each entry carries:\n\n- **The risk stated as a cause and consequence** — \"if X happens, then Y.\" \"Cybersecurity\" is a\n  category, not a risk. \"If an employee's credentials are phished, an attacker reaches customer\n  records\" is a risk you can do something about.\n- **Likelihood and impact**, on a stated scale, with the reasoning. The reasoning matters more than\n  the score.\n- **Current controls** and an honest view of whether they work.\n- **Residual risk** after those controls — the number that actually matters and the one most often\n  omitted.\n- **A named owner.** A person, not a department.\n- **Treatment and a date.**\n\n## Treatment is a decision with four options\n\n**Mitigate** (reduce it), **transfer** (insure or contract it away), **avoid** (do not do the\nthing), or **accept**. Accepting is legitimate and often correct — but acceptance must be explicit,\nat the right level of authority, and recorded. Risk accepted by silence is risk nobody owns.\n\nAnything above the threshold that only the chief executive can accept goes to them. Never let an\nunacceptable risk be quietly downgraded to fit an existing authority.\n\n## Scoring honestly\n\nTwo failure modes, both common:\n\n- **Everything is high.** The register stops discriminating and gets ignored.\n- **Scores drift downward** as items age without the underlying exposure changing.\n\nRe-assess on a schedule and require evidence for any reduction. A control's existence is not\nevidence it works; a test of the control is.\n\n## Audit readiness\n\nContinuous, not a project. What auditors need: documented policies, evidence they are followed,\nrecords of exceptions and approvals, and a clear line from the framework's requirement to your\ncontrol to the evidence.\n\nCollect evidence as work happens. Assembling a year of it retrospectively is expensive, and gaps\nfound then cannot be fixed retroactively.\n\n## Reporting\n\nLeadership needs the few risks whose residual exposure is above appetite, what is being done, and\nwhat needs a decision. Not the whole register. A risk report that requires reading forty rows to\nfind the three that matter will not be read.\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\nA risk register is a table, and for most organizations a spreadsheet or a database in\nNotion, Airtable, or Confluence is the honest answer. Dedicated platforms — LogicGate,\nAuditBoard, Riskonnect, ServiceNow IRM, and similar — earn their place when the register\nhas to reconcile with audit findings and control testing in one system.\n\nCompliance automation tools cover control evidence, not enterprise risk. Do not let one\nstand in for the other.\n\n## Never\n\n- Score residual risk on controls that are planned rather than operating.\n- Accept a risk without naming who accepted it and when it is reviewed again.\n- Keep a register with no review cadence. That is documentation, not risk management.\n- Close a risk because the project that raised it ended.\n","# Enterprise risk\n\n## The register is the artifact\n\nA risk that is not written down with an owner is not managed. Each entry carries:\n\n- **The risk stated as a cause and consequence** — \"if X happens, then Y.\" \"Cybersecurity\" is a\n  category, not a risk. \"If an employee's credentials are phished, an attacker reaches customer\n  records\" is a risk you can do something about.\n- **Likelihood and impact**, on a stated scale, with the reasoning. The reasoning matters more than\n  the score.\n- **Current controls** and an honest view of whether they work.\n- **Residual risk** after those controls — the number that actually matters and the one most often\n  omitted.\n- **A named owner.** A person, not a department.\n- **Treatment and a date.**\n\n## Treatment is a decision with four options\n\n**Mitigate** (reduce it), **transfer** (insure or contract it away), **avoid** (do not do the\nthing), or **accept**. Accepting is legitimate and often correct — but acceptance must be explicit,\nat the right level of authority, and recorded. Risk accepted by silence is risk nobody owns.\n\nAnything above the threshold that only the chief executive can accept goes to them. Never let an\nunacceptable risk be quietly downgraded to fit an existing authority.\n\n## Scoring honestly\n\nTwo failure modes, both common:\n\n- **Everything is high.** The register stops discriminating and gets ignored.\n- **Scores drift downward** as items age without the underlying exposure changing.\n\nRe-assess on a schedule and require evidence for any reduction. A control's existence is not\nevidence it works; a test of the control is.\n\n## Audit readiness\n\nContinuous, not a project. What auditors need: documented policies, evidence they are followed,\nrecords of exceptions and approvals, and a clear line from the framework's requirement to your\ncontrol to the evidence.\n\nCollect evidence as work happens. Assembling a year of it retrospectively is expensive, and gaps\nfound then cannot be fixed retroactively.\n\n## Reporting\n\nLeadership needs the few risks whose residual exposure is above appetite, what is being done, and\nwhat needs a decision. Not the whole register. A risk report that requires reading forty rows to\nfind the three that matter will not be read.\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\nA risk register is a table, and for most organizations a spreadsheet or a database in\nNotion, Airtable, or Confluence is the honest answer. Dedicated platforms — LogicGate,\nAuditBoard, Riskonnect, ServiceNow IRM, and similar — earn their place when the register\nhas to reconcile with audit findings and control testing in one system.\n\nCompliance automation tools cover control evidence, not enterprise risk. Do not let one\nstand in for the other.\n\n## Never\n\n- Score residual risk on controls that are planned rather than operating.\n- Accept a risk without naming who accepted it and when it is reviewed again.\n- Keep a register with no review cadence. That is documentation, not risk management.\n- Close a risk because the project that raised it ended.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fenterprise-risk",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 enterprise-risk",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill enterprise-risk",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill enterprise-risk","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fenterprise-risk\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",908,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fenterprise-risk\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",[],[]]