[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBDVWDMEAEBPQH9F17C7PH":3,"skill-same:01M7FBDVWDMEAEBPQH9F17C7PH":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},"01M7FBDVWDMEAEBPQH9F17C7PH","regulatory-compliance",null,"Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators. Use this to work out what applies to your business, stand up a compliance program, prepare for a regulatory exam or certification, respond to a finding, or assess exposure before entering a new market.","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\u002Fregulatory-compliance\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: regulatory-compliance\ndescription: Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators. Use this to work out what applies to your business, stand up a compliance program, prepare for a regulatory exam or certification, respond to a finding, or assess exposure before entering a new market.\n---\n\n# Regulatory compliance\n\nCompliance failures are rarely defiance. They are almost always an obligation nobody knew applied,\nin a jurisdiction nobody was watching, discovered by someone external.\n\n**This structures the work and names what to ask. Which regulations apply, and what they require,\nare legal determinations that vary by jurisdiction and change — they belong with qualified counsel.\nNothing here substitutes for that.**\n\n## Start with an obligation map, not a framework\n\nThe first question is not \"are we SOC 2 compliant\" but \"what are we actually obliged to do, by\nwhom, and what happens if we do not.\" Build the map from facts about the business:\n\n- **What you sell, and to whom.** Selling to regulated customers pulls their obligations onto you\n  through contract even when the regulation does not reach you directly.\n- **What data you hold.** Personal data, health data, payment data and children's data each carry\n  distinct regimes — see `legal-risk:privacy-and-data-protection`.\n- **Where you operate and where your customers are.** Obligations follow the customer more often\n  than companies expect.\n- **How you are funded and structured.** Public, regulated, or government-adjacent adds regimes.\n\nDistinguish three things that get conflated: **law** you must follow, **certifications** you choose\nto obtain commercially, and **contractual commitments** you signed. Only the first carries state\nenforcement; all three carry consequences.\n\n## Certifications are evidence, not compliance\n\nSOC 2, ISO 27001 and their equivalents demonstrate that controls exist and operate. They do not\nestablish that you meet any legal obligation, and a clean report is not a defense to a regulator.\n\nWhere they earn their cost is commercially — an enterprise prospect makes the certification a\ncondition of the deal, and the certification is what unblocks it. Scope them to what the market\nasks for rather than to everything, since scope drives cost more than any other decision.\n\n## The program is monitoring, not documentation\n\nA compliance program that produces policies and stops is a shelf. What makes it real:\n\n- **An owner per obligation** — a named person, not a department.\n- **Controls that produce evidence as a by-product** of the work, rather than evidence assembled\n  before an audit. See `finance:internal-controls-and-audit` for the control design pattern.\n- **Monitoring that would detect failure** before an external party does, with the frequency matched\n  to how fast the obligation can be breached.\n- **Horizon scanning.** Regulation changes; a map built once is wrong within a year.\n\n## When a regulator arrives\n\nRespond promptly, accurately, and narrowly — answer what was asked. Route everything through counsel\nbefore it goes out, preserve records from the moment you are aware, and never let an informal\nconversation become an undocumented commitment.\n\nFindings get root-caused like any other failure. A remediation that consists of retraining people on\na process that made the failure easy will produce the same finding next cycle.\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\nCompliance automation — Vanta, Drata, Secureframe, Keel GRC, and similar — collects\nevidence continuously and maps one control across several frameworks. It earns its cost on\nthe second audit far more often than the first.\n\nPolicy and attestation lives in those same tools, or in the HRIS, or in Confluence. What\nmatters is that a policy carries a version, an owner, and a record of who acknowledged it.\n\n## Never\n\n- Treat a certification as evidence of legal compliance.\n- Build a compliance program without a named owner per obligation.\n- Assemble control evidence retrospectively for an audit.\n- Answer a regulator without counsel reviewing the response.\n","# Regulatory compliance\n\nCompliance failures are rarely defiance. They are almost always an obligation nobody knew applied,\nin a jurisdiction nobody was watching, discovered by someone external.\n\n**This structures the work and names what to ask. Which regulations apply, and what they require,\nare legal determinations that vary by jurisdiction and change — they belong with qualified counsel.\nNothing here substitutes for that.**\n\n## Start with an obligation map, not a framework\n\nThe first question is not \"are we SOC 2 compliant\" but \"what are we actually obliged to do, by\nwhom, and what happens if we do not.\" Build the map from facts about the business:\n\n- **What you sell, and to whom.** Selling to regulated customers pulls their obligations onto you\n  through contract even when the regulation does not reach you directly.\n- **What data you hold.** Personal data, health data, payment data and children's data each carry\n  distinct regimes — see `legal-risk:privacy-and-data-protection`.\n- **Where you operate and where your customers are.** Obligations follow the customer more often\n  than companies expect.\n- **How you are funded and structured.** Public, regulated, or government-adjacent adds regimes.\n\nDistinguish three things that get conflated: **law** you must follow, **certifications** you choose\nto obtain commercially, and **contractual commitments** you signed. Only the first carries state\nenforcement; all three carry consequences.\n\n## Certifications are evidence, not compliance\n\nSOC 2, ISO 27001 and their equivalents demonstrate that controls exist and operate. They do not\nestablish that you meet any legal obligation, and a clean report is not a defense to a regulator.\n\nWhere they earn their cost is commercially — an enterprise prospect makes the certification a\ncondition of the deal, and the certification is what unblocks it. Scope them to what the market\nasks for rather than to everything, since scope drives cost more than any other decision.\n\n## The program is monitoring, not documentation\n\nA compliance program that produces policies and stops is a shelf. What makes it real:\n\n- **An owner per obligation** — a named person, not a department.\n- **Controls that produce evidence as a by-product** of the work, rather than evidence assembled\n  before an audit. See `finance:internal-controls-and-audit` for the control design pattern.\n- **Monitoring that would detect failure** before an external party does, with the frequency matched\n  to how fast the obligation can be breached.\n- **Horizon scanning.** Regulation changes; a map built once is wrong within a year.\n\n## When a regulator arrives\n\nRespond promptly, accurately, and narrowly — answer what was asked. Route everything through counsel\nbefore it goes out, preserve records from the moment you are aware, and never let an informal\nconversation become an undocumented commitment.\n\nFindings get root-caused like any other failure. A remediation that consists of retraining people on\na process that made the failure easy will produce the same finding next cycle.\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\nCompliance automation — Vanta, Drata, Secureframe, Keel GRC, and similar — collects\nevidence continuously and maps one control across several frameworks. It earns its cost on\nthe second audit far more often than the first.\n\nPolicy and attestation lives in those same tools, or in the HRIS, or in Confluence. What\nmatters is that a policy carries a version, an owner, and a record of who acknowledged it.\n\n## Never\n\n- Treat a certification as evidence of legal compliance.\n- Build a compliance program without a named owner per obligation.\n- Assemble control evidence retrospectively for an audit.\n- Answer a regulator without counsel reviewing the response.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fregulatory-compliance",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 regulatory-compliance",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill regulatory-compliance",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill regulatory-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fregulatory-compliance\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",4165,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fregulatory-compliance\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",[],[]]