[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718DGVY1XG3025K6SMN2VYC":3,"skill-same:01M718DGVY1XG3025K6SMN2VYC":67},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M718DGVY1XG3025K6SMN2VYC","customize",null,"Guided customization of your employment practice profile — change one thing without re-running the whole cold-start interview. Adjust jurisdictional footprint, risk posture, escalation contacts, hiring review rules, termination review rules, handbook positions, investigation preferences, or matter workspace paths. Use when the user says \"change my [thing]\", \"add a jurisdiction\", \"update my profile\", \"edit my config\", or \"customize\".","anthropics\u002Fclaude-for-legal","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7189QY7HXHMC9BW4MFHPZ6H",10006,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Femployment-legal\u002Fskills\u002Fcustomize\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"adjust","name","change","contacts","review","you","when","Rules","use","preferences","cold-start","employment","re","section","risk","cold","escalation","interview","running","2026-11-10 10:12:30",false,"---\nname: customize\ndescription: >\n  Guided customization of your employment practice profile — change one thing\n  without re-running the whole cold-start interview. Adjust jurisdictional\n  footprint, risk posture, escalation contacts, hiring review rules,\n  termination review rules, handbook positions, investigation preferences,\n  or matter workspace paths. Use when the user says \"change my [thing]\",\n  \"add a jurisdiction\", \"update my profile\", \"edit my config\", or \"customize\".\nargument-hint: \"[section name, or describe what you want to change]\"\n---\n\n# \u002Fcustomize\n\n## When this runs\n\nThe user typed `\u002Femployment-legal:customize`. They want to change something\nin their practice profile — a jurisdiction, a risk posture, an escalation\ncontact, a handbook position — without re-running the whole cold-start\ninterview and without hand-editing YAML.\n\n## What to do\n\n1. **Read the config.** Read\n   `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Femployment-legal\u002FCLAUDE.md`\n   (and `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcompany-profile.md` one\n   level up). If the plugin config does not exist or still contains\n   `[PLACEHOLDER]` values, say:\n\n   > You haven't run setup yet. Run `\u002Femployment-legal:cold-start-interview`\n   > first — customize is for adjusting a profile you already have.\n\n2. **Show the customizable map.** List what's in the profile, grouped, with a\n   one-line summary of the current value:\n\n   - **Company \u002F who you are** — name, industry, practice setting, jurisdictions\n     *(shared across all 12 plugins — changes flow through\n     `company-profile.md`)*\n   - **Jurisdictional footprint** — states (and countries) where employees\n     work, single-state vs. multi-state, and any upcoming expansion. This\n     drives state-specific supplement logic.\n   - **Risk posture** — conservative \u002F middle \u002F aggressive, what each means\n     for flagging termination risk, restrictive covenant enforceability, and\n     leave accommodation\n   - **People** — HR partners, people team lead, outside counsel, escalation\n     chain, investigation sponsor\n   - **Hiring review** — offer letter template, restrictive covenants\n     posture, background check vendor, standard at-will language\n   - **Termination review** — severance framework, release language, final\n     pay timing rules per state, high-risk flags\n   - **Handbook** — handbook file path, state supplements approach, review\n     cadence\n   - **Investigation preferences** — privileged labeling, interview protocol,\n     audience-specific summary templates\n   - **Workflow** — matter workspaces, leave tracker cadence, expansion\n     project paths\n   - **Integrations** — HRIS \u002F Slack \u002F document storage status, fallbacks\n\n3. **Ask what they want to change.**\n\n   > What would you like to adjust? Pick a section, or describe the change in\n   > your own words.\n\n4. **Make the change.** Show the current value, ask for the new value, explain\n   what changes downstream, confirm, write it to the config.\n\n   Examples:\n   - *Adding Washington to the jurisdictional footprint:* \"`\u002Fwage-hour-qa`\n     and `\u002Ftermination-review` will start applying WA rules. `\u002Fhandbook-\n     updates` will prompt for a WA supplement. `\u002Fhiring-review` will now\n     flag non-compete attempts in WA (unenforceable).\"\n   - *Severance framework 2 weeks\u002Fyear → 4 weeks\u002Fyear:* \"`\u002Ftermination-\n     review` will use the new baseline in severance calculations.\"\n   - *Risk posture middle → conservative:* \"I'll flag more terminations for\n     escalation, recommend more protective release language, and be stricter\n     on restrictive covenants.\"\n\n5. **For shared-profile changes** (company name, industry, jurisdictions,\n   practice setting, stage): write to\n   `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcompany-profile.md` and note:\n\n   > This change affects all 12 plugins — any plugin that reads your\n   > jurisdiction footprint now sees [new value].\n\n6. **Close.**\n\n   > Done. Your next output will reflect the change. Anything else? You can\n   > run `\u002Femployment-legal:customize` anytime.\n\n## Guardrails\n\n- **Never delete a section.** If the user wants to \"remove\" a jurisdiction,\n  offer to mark it `[Not currently staffed — retain rules for re-entry]` and\n  explain that going to `[Not configured]` will drop state-specific\n  flagging.\n- **Flag internal inconsistency.** If the change would make the profile\n  inconsistent (e.g., CA in the footprint + aggressive non-compete posture;\n  or risk posture aggressive + \"every termination goes to outside counsel\"),\n  flag the tension.\n- **Flag guardrail degradation.** The pre-flight citation check, source\n  attribution tags, and `[verify]` tags on cited statutes are load-bearing —\n  do not remove. The `[review]` flag is load-bearing — explain the trade-off\n  before adjusting.\n- **One change at a time.** Don't re-ask the whole interview.\n","# \u002Fcustomize\n\n## When this runs\n\nThe user typed `\u002Femployment-legal:customize`. They want to change something\nin their practice profile — a jurisdiction, a risk posture, an escalation\ncontact, a handbook position — without re-running the whole cold-start\ninterview and without hand-editing YAML.\n\n## What to do\n\n1. **Read the config.** Read\n   `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Femployment-legal\u002FCLAUDE.md`\n   (and `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcompany-profile.md` one\n   level up). If the plugin config does not exist or still contains\n   `[PLACEHOLDER]` values, say:\n\n   > You haven't run setup yet. Run `\u002Femployment-legal:cold-start-interview`\n   > first — customize is for adjusting a profile you already have.\n\n2. **Show the customizable map.** List what's in the profile, grouped, with a\n   one-line summary of the current value:\n\n   - **Company \u002F who you are** — name, industry, practice setting, jurisdictions\n     *(shared across all 12 plugins — changes flow through\n     `company-profile.md`)*\n   - **Jurisdictional footprint** — states (and countries) where employees\n     work, single-state vs. multi-state, and any upcoming expansion. This\n     drives state-specific supplement logic.\n   - **Risk posture** — conservative \u002F middle \u002F aggressive, what each means\n     for flagging termination risk, restrictive covenant enforceability, and\n     leave accommodation\n   - **People** — HR partners, people team lead, outside counsel, escalation\n     chain, investigation sponsor\n   - **Hiring review** — offer letter template, restrictive covenants\n     posture, background check vendor, standard at-will language\n   - **Termination review** — severance framework, release language, final\n     pay timing rules per state, high-risk flags\n   - **Handbook** — handbook file path, state supplements approach, review\n     cadence\n   - **Investigation preferences** — privileged labeling, interview protocol,\n     audience-specific summary templates\n   - **Workflow** — matter workspaces, leave tracker cadence, expansion\n     project paths\n   - **Integrations** — HRIS \u002F Slack \u002F document storage status, fallbacks\n\n3. **Ask what they want to change.**\n\n   > What would you like to adjust? Pick a section, or describe the change in\n   > your own words.\n\n4. **Make the change.** Show the current value, ask for the new value, explain\n   what changes downstream, confirm, write it to the config.\n\n   Examples:\n   - *Adding Washington to the jurisdictional footprint:* \"`\u002Fwage-hour-qa`\n     and `\u002Ftermination-review` will start applying WA rules. `\u002Fhandbook-\n     updates` will prompt for a WA supplement. `\u002Fhiring-review` will now\n     flag non-compete attempts in WA (unenforceable).\"\n   - *Severance framework 2 weeks\u002Fyear → 4 weeks\u002Fyear:* \"`\u002Ftermination-\n     review` will use the new baseline in severance calculations.\"\n   - *Risk posture middle → conservative:* \"I'll flag more terminations for\n     escalation, recommend more protective release language, and be stricter\n     on restrictive covenants.\"\n\n5. **For shared-profile changes** (company name, industry, jurisdictions,\n   practice setting, stage): write to\n   `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcompany-profile.md` and note:\n\n   > This change affects all 12 plugins — any plugin that reads your\n   > jurisdiction footprint now sees [new value].\n\n6. **Close.**\n\n   > Done. Your next output will reflect the change. Anything else? You can\n   > run `\u002Femployment-legal:customize` anytime.\n\n## Guardrails\n\n- **Never delete a section.** If the user wants to \"remove\" a jurisdiction,\n  offer to mark it `[Not currently staffed — retain rules for re-entry]` and\n  explain that going to `[Not configured]` will drop state-specific\n  flagging.\n- **Flag internal inconsistency.** If the change would make the profile\n  inconsistent (e.g., CA in the footprint + aggressive non-compete posture;\n  or risk posture aggressive + \"every termination goes to outside counsel\"),\n  flag the tension.\n- **Flag guardrail degradation.** The pre-flight citation check, source\n  attribution tags, and `[verify]` tags on cited statutes are load-bearing —\n  do not remove. The `[review]` flag is load-bearing — explain the trade-off\n  before adjusting.\n- **One change at a time.** Don't re-ask the whole interview.\n",{"name":5,"description":43,"argument-hint":44},"Guided customization of your employment practice profile — change one thing without re-running the whole cold-start interview. Adjust jurisdictional footprint, risk posture, escalation contacts, hiring review rules, termination review rules, handbook positions, investigation preferences, or matter workspace paths. Use when the user says \"change my [thing]\", \"add a jurisdiction\", \"update my profile\", \"edit my config\", or \"customize\".\n","[section name, or describe what you want to change]","main","4a6c651889c97cc9140580363c73e0eb17379c2b","employment-legal\u002Fskills\u002Fcustomize",1968,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-14 23:30:58",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add anthropics\u002Fclaude-for-legal --skill customize",{"tool":59,"command":60},"bunx","bunx skills add anthropics\u002Fclaude-for-legal --skill customize",{"tool":62,"command":63},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-for-legal --skill customize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Femployment-legal\u002Fskills\u002Fcustomize\u002FSKILL.md",true,[],[68,97,118,134,156,168],{"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":79,"publishedAt":38},"01M718SG9G2R92ECCD0HYK2R5E","reg-feed-watcher","Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says \"check the feeds\", \"what's new\", \"regulatory update\", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Freg-feed-watcher\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[80,81,82,37,83,84,85,86,87,88,89,90,27,91,25,92,93,94,95,96],"reg","watcher","reg feed watcher","feeds","filtered","diff","development","for","classification","new","now","scheduled","check","last","update","report","regulatory",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":38},"01M718SCRTBN55DMTVSPG67A7N","policy-redraft","Produce a proposed marked-up policy redraft that closes a gap found by \u002Fregulatory-legal:gaps or \u002Fregulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says \"redraft the policy\", \"draft the policy fix\", \"mark up the policy\", or when gap-surfacer hands off a gap for drafting.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fpolicy-redraft\u002FSKILL.md",[],[104,105,85,87,106,107,108,27,109,25,110,111,23,112,113,114,115,116,96,117],"policy","policy redraft","up","fix","produce","documents","drafting","gaps","draft","id","gap","mark","first","direct",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":38},"01M718S8RV0C4NMVKG078CBFXP","policy-diff","Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says \"diff this reg against our policies\", \"which policy does this affect\", or \"gap analysis\", or when reg-feed-watcher hands off a material item.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fpolicy-diff\u002FSKILL.md",[],[85,104,125,126,25,24,127,80,128,81,21,129,130,131,27,132,114,133,20,96],"policy diff","which","analysis","text","paste","library","material","gap analysis","what the",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":38},"01M718S6521Y0FT4T24VCFKVG5","matter-workspace","Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fmatter-workspace\u002FSKILL.md",[],[141,142,126,143,144,145,89,27,25,24,146,147,148,149,150,151,152,153,154,155],"workspace","matter workspace","switch","manage","workspaces","keep","across","create","engagement","close","active","clients","list","it","context",{"skillNo":157,"name":111,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":38},"01M718S3FPEJNQGCMQ1AR8M4HE","Open gaps tracker — what's flagged and not yet closed. Use when the user asks \"what gaps are open\", \"gap tracker\", \"remediation status\", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fgaps\u002FSKILL.md",[],[111,113,114,33,150,162,163,164,165,27,166,25,167],"tracker","remediation","status","open","accept","user",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":179,"publishedAt":38},"01M718S06WSZ9Y24JKYM0VVPPE","gap-surfacer","Reference: shared gap- and comment-tracker framework backing \u002Fregulatory-legal:gaps and \u002Fregulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fgap-surfacer\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[114,180,181,182,85,104,183,165,184,185,186,187,111,188,189,190,191,162,163,192],"gap surfacer","shared","tracks","send","confirmation","aging","false","comments","with","work","slack","via","surfaces"]