[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79MWJN7ASTGK8VGG807TYWB":3,"skill-same:01M79MWJN7ASTGK8VGG807TYWB":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M79MWJN7ASTGK8VGG807TYWB","legal-risk",null,"Legal exposure review for a product or business plan. OmniSkill Legal crew — sweeps the standard exposure categories before building, ranks by likelihood and impact, and proposes mitigations.","IPedrax\u002FOmniSkill","IPedrax","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64429409?v=4","01M79MSCRSKESGTTRZMGK54KW0","01M79MSCSDY16CNNHW0VRGZFHF",9,"MIT","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Flegal-risk\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: legal-risk\ndescription: Legal exposure review for a product or business plan. OmniSkill Legal crew — sweeps the standard exposure categories before building, ranks by likelihood and impact, and proposes mitigations.\ndisable-model-invocation: true\n---\n\n# Legal Risk\n\n> Flags legal exposure · OmniSkill Legal crew\n\n**This is analysis, not legal advice.** No attorney-client relationship exists. Material findings need a qualified attorney.\n\nRun this **before building**, not after. Exposure found at design time is a design change; the same exposure found at launch is a rewrite, and sometimes a recall.\n\n## Sweep these categories\n\n**Data and privacy**\nWhat personal data is collected, why, where it is stored, who it is shared with, how long it is kept. Cross-border transfer. Children's data (a hard line — under 13 triggers COPPA in the US, and similar rules elsewhere). Biometrics carry their own statutes with statutory damages. Route specifics to `\u002Fomniskill:compliance`.\n\n**Intellectual property**\nFreedom to operate: does this infringe anything known? Ownership of what is built — contractor agreements without written assignment leave IP with the contractor. Open-source licence obligations, especially copyleft in distributed software. Trademark clearance before committing to a name. Training data provenance for any model.\n\n**Consumer protection**\nAdvertising claims must be substantiated before publication. Dark patterns in signup or cancellation flows are actively enforced. Auto-renewal disclosure and easy cancellation are statutory in many jurisdictions. Pricing transparency, including all mandatory fees.\n\n**Contracts and commitments**\nTerms of service and privacy policy actually fit for the product. Liability caps and disclaimers that survive. SLAs the business can meet. Existing agreements that constrain this plan — exclusivity, non-competes, MFN clauses.\n\n**Employment**\nWorker classification (contractor versus employee) is a frequent and expensive error. Non-competes are unenforceable or restricted in a growing number of jurisdictions. Equity and compensation compliance.\n\n**Sector-specific**\nFinancial services, health, insurance, legal, education, and children's products each carry licensing and disclosure regimes. Identify early whether the product touches a regulated activity — retrofitting a licence is rarely possible.\n\n**Platform and distribution**\nApp-store rules, API terms of service, and scraping restrictions. Building a business on a platform whose terms forbid it is an existential risk, not a legal footnote.\n\n## Rank the findings\n\nScore likelihood × impact:\n\n| Rating | Meaning | Response |\n|---|---|---|\n| **Critical** | Likely, and existential | Do not proceed without counsel |\n| **High** | Probable and material | Mitigate before launch |\n| **Medium** | Possible, manageable | Plan a mitigation |\n| **Low** | Unlikely or immaterial | Note and monitor |\n\nConcentrate on what is both likely *and* material. A register where everything is critical gets ignored, and then the genuinely critical item is ignored with it.\n\n## Output\n\nFor each finding: what the exposure is, what triggers it, the realistic consequence, likelihood and impact, and a concrete mitigation with an owner.\n\nMitigations must be actionable. \"Consult counsel\" is not a mitigation — \"add explicit consent before collecting location data, and confirm the wording with counsel\" is.\n\nOpen with the three things that would actually stop the launch.\n\n## Judgement\n\nDistinguish legal risk from business risk. Most decisions carry some legal exposure, and the answer is rarely \"do not do it\" — it is \"do it this way instead\". The value here is in finding the version that works, not in listing reasons to stop.\n\n## Checks before delivering\n\n- Every category swept, including ones that turned out not to apply.\n- Jurisdictions named explicitly — answers differ by country and by US state.\n- Each finding has a concrete, owned mitigation.\n- The three launch-blocking items lead the document.\n- The not-legal-advice scope note is present.\n","# Legal Risk\n\n> Flags legal exposure · OmniSkill Legal crew\n\n**This is analysis, not legal advice.** No attorney-client relationship exists. Material findings need a qualified attorney.\n\nRun this **before building**, not after. Exposure found at design time is a design change; the same exposure found at launch is a rewrite, and sometimes a recall.\n\n## Sweep these categories\n\n**Data and privacy**\nWhat personal data is collected, why, where it is stored, who it is shared with, how long it is kept. Cross-border transfer. Children's data (a hard line — under 13 triggers COPPA in the US, and similar rules elsewhere). Biometrics carry their own statutes with statutory damages. Route specifics to `\u002Fomniskill:compliance`.\n\n**Intellectual property**\nFreedom to operate: does this infringe anything known? Ownership of what is built — contractor agreements without written assignment leave IP with the contractor. Open-source licence obligations, especially copyleft in distributed software. Trademark clearance before committing to a name. Training data provenance for any model.\n\n**Consumer protection**\nAdvertising claims must be substantiated before publication. Dark patterns in signup or cancellation flows are actively enforced. Auto-renewal disclosure and easy cancellation are statutory in many jurisdictions. Pricing transparency, including all mandatory fees.\n\n**Contracts and commitments**\nTerms of service and privacy policy actually fit for the product. Liability caps and disclaimers that survive. SLAs the business can meet. Existing agreements that constrain this plan — exclusivity, non-competes, MFN clauses.\n\n**Employment**\nWorker classification (contractor versus employee) is a frequent and expensive error. Non-competes are unenforceable or restricted in a growing number of jurisdictions. Equity and compensation compliance.\n\n**Sector-specific**\nFinancial services, health, insurance, legal, education, and children's products each carry licensing and disclosure regimes. Identify early whether the product touches a regulated activity — retrofitting a licence is rarely possible.\n\n**Platform and distribution**\nApp-store rules, API terms of service, and scraping restrictions. Building a business on a platform whose terms forbid it is an existential risk, not a legal footnote.\n\n## Rank the findings\n\nScore likelihood × impact:\n\n| Rating | Meaning | Response |\n|---|---|---|\n| **Critical** | Likely, and existential | Do not proceed without counsel |\n| **High** | Probable and material | Mitigate before launch |\n| **Medium** | Possible, manageable | Plan a mitigation |\n| **Low** | Unlikely or immaterial | Note and monitor |\n\nConcentrate on what is both likely *and* material. A register where everything is critical gets ignored, and then the genuinely critical item is ignored with it.\n\n## Output\n\nFor each finding: what the exposure is, what triggers it, the realistic consequence, likelihood and impact, and a concrete mitigation with an owner.\n\nMitigations must be actionable. \"Consult counsel\" is not a mitigation — \"add explicit consent before collecting location data, and confirm the wording with counsel\" is.\n\nOpen with the three things that would actually stop the launch.\n\n## Judgement\n\nDistinguish legal risk from business risk. Most decisions carry some legal exposure, and the answer is rarely \"do not do it\" — it is \"do it this way instead\". The value here is in finding the version that works, not in listing reasons to stop.\n\n## Checks before delivering\n\n- Every category swept, including ones that turned out not to apply.\n- Jurisdictions named explicitly — answers differ by country and by US state.\n- Each finding has a concrete, owned mitigation.\n- The three launch-blocking items lead the document.\n- The not-legal-advice scope note is present.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","cc238b48e3c4fe0061cad0b0475142fbff5b183d","skills\u002Flegal-risk",0,"https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill","https:\u002F\u002Fgithub.com\u002FIPedrax","2026-10-14 10:26:53",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":23},[33,36,39],{"tool":34,"command":35},"npx","npx skills add IPedrax\u002FOmniSkill --skill legal-risk",{"tool":37,"command":38},"bunx","bunx skills add IPedrax\u002FOmniSkill --skill legal-risk",{"tool":40,"command":41},"pnpm","pnpm dlx skills add IPedrax\u002FOmniSkill --skill legal-risk","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Flegal-risk\u002FSKILL.md",[],[45,52,59,66,73,79],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M79N058MCJZPHNFYZCPJG3ZZ","xlsx","Excel with live formulas. OmniSkill Operations crew — adapter for the xlsx skill, which installs separately.","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fxlsx\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M79N01GR5C5EK22CKGG38VYH","webapp-testing","Browser-test a web app. OmniSkill Developers crew — drives a real browser to verify user flows, catches console and network errors, and writes tests that do not flake.","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M79MZZSJHFKJRE46BNEHCYZ3","web-artifacts","shadcn HTML artifacts. OmniSkill Design crew — bundled copy of the Web Artifacts skill.","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M79MZXFMCV0QSQ2WN316JKGZ","video","Script and produce video. OmniSkill Social crew — structures short-form and long-form video around retention, with shot lists, captions, and platform-specific delivery.","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M79MZV8SR0N02YX539Z5PS5E","vgpu","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fvgpu\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M79MZS7JG9X0T4T5TGA4MMJS","uisfx","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fuisfx\u002FSKILL.md",[],[]]