[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718H9B9MG2JNWWFD97CZEB5":3,"skill-same:01M718H9B9MG2JNWWFD97CZEB5":68},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M718H9B9MG2JNWWFD97CZEB5","exam-forecast",null,"Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says \"what's on the exam\", \"analyze past exams\", \"predict the exam\", or shares past exams.","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\u002Flaw-student\u002Fskills\u002Fexam-forecast\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"exam","exam forecast","forecast","issue","paths","past","name","spot","predict","with","analyze","when","use","policy","mix","for","types","recurring","doctrine","shared","2026-11-10 10:12:30",false,"---\nname: exam-forecast\ndescription: >\n  Analyze past exams from the same professor to surface patterns — subject\n  weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine\n  mix — and forecast likely emphases for the upcoming exam. Use when the user\n  says \"what's on the exam\", \"analyze past exams\", \"predict the exam\", or\n  shares past exams.\nargument-hint: \"[class name, with past exams shared or paths to them]\"\n---\n\n# \u002Fexam-forecast\n\n1. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002FCLAUDE.md` → class, professor, exam format, syllabus.\n2. Apply the workflow below.\n3. Intake past exams (PDF, paste, or paths). Confirm sample size.\n4. Analyze each past exam: format, subject coverage, question style, fact-pattern density, recurring traps.\n5. Cross-exam pattern analysis — what's stable, what varies.\n6. Combine with current syllabus to produce forecast: subject weights, format, hobby horses, study emphasis.\n7. Write `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002Fexam-forecasts\u002F[class]\u002Fforecast-[YYYY-MM-DD].md`. Framed as weighting heuristic, not prediction.\n\n---\n\n## Purpose\n\nEvery professor's exam has fingerprints. The same hypo structures recur. The same traps come back. The same subject ratios repeat. Students who have prior exams study smarter; students who don't, study harder. This skill analyzes the prior exams you have and surfaces the patterns.\n\nNot magic. A forecast, not a prediction. The skill cannot tell you what's on the exam — it can tell you what's been on past exams and what's likely to recur based on syllabus coverage.\n\n## Confidence discipline\n\n- Pattern analysis (what subjects appeared, how many questions per topic, how often policy vs. rule-application) — confident where the exams are clearly in front of me.\n- Inference about likely emphasis on upcoming exam — `[UNCERTAIN]` is the default; these are forecasts, not certainties. Explicitly frame as \"based on the [N] past exams you shared, [topic] appeared in [M]. Your upcoming exam may emphasize it, or the professor may rotate — use this as a weighting for review time, not a prediction.\"\n- If only 1-2 past exams are available, say so explicitly — any pattern inferred from 1 exam is noise.\n- If the professor is new (no past exams available), skill can't forecast. Say so; fall back to syllabus-based \"these are the subjects covered\" only.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002FCLAUDE.md` → current classes, exam formats, syllabus if captured\n- User-provided past exams (PDF, pasted text, paths)\n- Optional: syllabus for the current class (for \"what's been covered to date\")\n\n**If the uploaded past exams have a professor's name, use it to match patterns** (same-professor exams are the highest-signal input). **If not, match on subject and structure.** Don't ask the user to type in the professor's name — use what's in the materials. If the user volunteers it in conversation that's fine; don't prompt for it.\n\n## Workflow\n\n### Step 1: Intake\n\n- Which class are we forecasting for?\n- How many past exams from this professor are available?\n- Are they from the same course, or different courses by the same professor?\n- Are any of them the take-home \u002F open-book \u002F different-format variants, vs. the typical format for your upcoming exam?\n- Syllabus for your current class?\n\nIf fewer than 3 past exams: flag as thin sample. Pattern inference is weaker.\nIf exams are across different courses: some patterns transfer (question style, policy vs. doctrine ratio); subject-specific patterns don't.\n\n### Step 2: Read each past exam\n\nFor each past exam:\n\n- Format (number of questions, length, time limit, open\u002Fclosed book)\n- Subject coverage (which topics tested, in what proportion)\n- Question style (issue-spotter, single-issue deep, policy essay, short-answer MBE-style, mix)\n- Fact pattern density (fact-heavy hypos, sparse facts with doctrinal focus, or policy prompts with no facts)\n- Recurring traps (e.g., professor always hides the jurisdictional issue in an otherwise-clean fact pattern; professor always asks about the exception rather than the rule)\n- Policy vs. doctrine ratio\n- Unusual structures (essays + MBE hybrid, moot court scenario, etc.)\n\n### Step 3: Cross-exam pattern analysis\n\nRoll up what's consistent across exams:\n\n**Stable patterns (appeared in most\u002Fall past exams):**\n- Subject weights (e.g., \"consideration and modification account for 30% of exam points consistently\")\n- Question style (e.g., \"always one long issue-spotter + two short-answer hypos\")\n- Professor hobby horses (e.g., \"always tests third-party beneficiaries even when it's a minor topic in class\")\n\n**Variable patterns (appeared in some but not all):**\n- Policy essays (e.g., \"appeared in 2 of 4 past exams — usually when the semester covered a policy-heavy topic late\")\n- Open-book vs. closed-book differences\n- Take-home vs. in-class differences\n\n**Absent patterns worth noting:**\n- Topics covered in class that have NEVER been tested in past exams — don't skip these, but don't weight them heavily either\n- Topics tested in past exams that aren't in your current syllabus — probably not coming back\n\n### Step 4: Forecast for the upcoming exam\n\n**Header — required, first line of the forecast, both in-chat and in the saved file.** Per plugin config `## Outputs`, every study output carries the verbatim study-notes header. The forecast is a study output. Do not omit, rephrase, or relocate the header. The header is not a disclaimer the student can ask to drop; it is the output's identity and prevents the forecast from being mistaken for a predicted exam or for legal advice:\n\n```\nSTUDY NOTES — NOT LEGAL ADVICE\n```\n\nCombine pattern analysis with current syllabus:\n\n```markdown\nSTUDY NOTES — NOT LEGAL ADVICE\n\n# Exam Forecast — [class \u002F professor] — [date]\n\n**Past exams analyzed:** [N]\n**Sample confidence:** [thin (\u003C3) \u002F moderate (3-5) \u002F strong (6+)]\n**Caveats:** [e.g., \"one of the past exams was an open-book final; your upcoming is closed-book. Pattern transfer is partial.\"]\n\n---\n\n## Subject weighting (historical)\n\n| Topic | Past exam weight (avg) | In current syllabus? | Forecast weight |\n|---|---|---|---|\n| [topic 1] | [%] | [yes\u002Fpartial\u002Fno] | [heavier \u002F stable \u002F lighter] |\n\n## Question-style forecast\n\n- **Format likely:** [X issue-spotters + Y short answers + Z policy, or similar]\n- **Fact-pattern density:** [fact-heavy \u002F sparse \u002F mixed]\n- **Call style:** [one broad call \u002F multiple specific calls \u002F bullet sub-parts]\n\n## Professor hobby horses to watch\n\n- [topic A] — appeared in [M of N] past exams. Weighted 3-5x its syllabus share.\n- [topic B] — [pattern]\n- [trap pattern] — e.g., \"hides jurisdictional issue in otherwise-clean facts\"\n\n## Topics covered this semester but rarely tested\n\n[list — don't skip, but don't over-weight]\n\n## Study emphasis recommendation\n\nBased on past exam patterns AND current syllabus coverage:\n\n**Heavy:** [topics likely to anchor the exam — 40-50% of study time]\n**Moderate:** [supporting topics — 30-40%]\n**Sanity check:** [topics covered but historically under-represented — 10-20%, just in case]\n\n## [UNCERTAIN — framing]\n\nThis forecast is derived from [N] past exams. Professors vary. Professors rotate. Topics that were emphasized in past years can be de-emphasized when the syllabus shifts. Treat this as a weighting heuristic for study time, not a prediction. The exam will include surprises.\n```\n\n### Step 5: Output location\n\nWrite to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002Fexam-forecasts\u002F[class]\u002Fforecast-[YYYY-MM-DD].md`. Versioned — if the student gets another past exam mid-semester, re-run and append.\n\n## Integration\n\n- **outline-builder:** forecast weights feed into outline depth decisions — weight depth on heavy topics\n- **flashcards:** forecast-heavy topics get more cards generated\n- **bar-prep-questions:** irrelevant for bar prep (that has its own forecast model); exam-forecast is for class-specific finals\n- **irac-practice:** use forecast topics as the subject areas for IRAC practice hypos\n\n## Close with the next-steps decision tree\n\nEnd with the next-steps decision tree per CLAUDE.md `## Outputs`. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.\n\n## What this skill does not do\n\n- **Predict specific questions.** Past exams show patterns; they don't show you tomorrow's prompt.\n- **Work without past exams.** If you don't have prior exams from this professor, the skill can't forecast — it falls back to \"here's what the syllabus covers, study that.\"\n- **Replace studying everything on the syllabus.** Forecast is weighting, not elimination. Skipping a topic because it's historically under-represented is how students get burned.\n- **Account for changes you don't know about.** If the professor has shifted focus this year (e.g., emphasized a new case in class lectures), the skill doesn't see that unless you tell it.\n- **Work reliably with 1-2 past exams.** Thin sample. Flag as such.\n","# \u002Fexam-forecast\n\n1. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002FCLAUDE.md` → class, professor, exam format, syllabus.\n2. Apply the workflow below.\n3. Intake past exams (PDF, paste, or paths). Confirm sample size.\n4. Analyze each past exam: format, subject coverage, question style, fact-pattern density, recurring traps.\n5. Cross-exam pattern analysis — what's stable, what varies.\n6. Combine with current syllabus to produce forecast: subject weights, format, hobby horses, study emphasis.\n7. Write `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002Fexam-forecasts\u002F[class]\u002Fforecast-[YYYY-MM-DD].md`. Framed as weighting heuristic, not prediction.\n\n---\n\n## Purpose\n\nEvery professor's exam has fingerprints. The same hypo structures recur. The same traps come back. The same subject ratios repeat. Students who have prior exams study smarter; students who don't, study harder. This skill analyzes the prior exams you have and surfaces the patterns.\n\nNot magic. A forecast, not a prediction. The skill cannot tell you what's on the exam — it can tell you what's been on past exams and what's likely to recur based on syllabus coverage.\n\n## Confidence discipline\n\n- Pattern analysis (what subjects appeared, how many questions per topic, how often policy vs. rule-application) — confident where the exams are clearly in front of me.\n- Inference about likely emphasis on upcoming exam — `[UNCERTAIN]` is the default; these are forecasts, not certainties. Explicitly frame as \"based on the [N] past exams you shared, [topic] appeared in [M]. Your upcoming exam may emphasize it, or the professor may rotate — use this as a weighting for review time, not a prediction.\"\n- If only 1-2 past exams are available, say so explicitly — any pattern inferred from 1 exam is noise.\n- If the professor is new (no past exams available), skill can't forecast. Say so; fall back to syllabus-based \"these are the subjects covered\" only.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002FCLAUDE.md` → current classes, exam formats, syllabus if captured\n- User-provided past exams (PDF, pasted text, paths)\n- Optional: syllabus for the current class (for \"what's been covered to date\")\n\n**If the uploaded past exams have a professor's name, use it to match patterns** (same-professor exams are the highest-signal input). **If not, match on subject and structure.** Don't ask the user to type in the professor's name — use what's in the materials. If the user volunteers it in conversation that's fine; don't prompt for it.\n\n## Workflow\n\n### Step 1: Intake\n\n- Which class are we forecasting for?\n- How many past exams from this professor are available?\n- Are they from the same course, or different courses by the same professor?\n- Are any of them the take-home \u002F open-book \u002F different-format variants, vs. the typical format for your upcoming exam?\n- Syllabus for your current class?\n\nIf fewer than 3 past exams: flag as thin sample. Pattern inference is weaker.\nIf exams are across different courses: some patterns transfer (question style, policy vs. doctrine ratio); subject-specific patterns don't.\n\n### Step 2: Read each past exam\n\nFor each past exam:\n\n- Format (number of questions, length, time limit, open\u002Fclosed book)\n- Subject coverage (which topics tested, in what proportion)\n- Question style (issue-spotter, single-issue deep, policy essay, short-answer MBE-style, mix)\n- Fact pattern density (fact-heavy hypos, sparse facts with doctrinal focus, or policy prompts with no facts)\n- Recurring traps (e.g., professor always hides the jurisdictional issue in an otherwise-clean fact pattern; professor always asks about the exception rather than the rule)\n- Policy vs. doctrine ratio\n- Unusual structures (essays + MBE hybrid, moot court scenario, etc.)\n\n### Step 3: Cross-exam pattern analysis\n\nRoll up what's consistent across exams:\n\n**Stable patterns (appeared in most\u002Fall past exams):**\n- Subject weights (e.g., \"consideration and modification account for 30% of exam points consistently\")\n- Question style (e.g., \"always one long issue-spotter + two short-answer hypos\")\n- Professor hobby horses (e.g., \"always tests third-party beneficiaries even when it's a minor topic in class\")\n\n**Variable patterns (appeared in some but not all):**\n- Policy essays (e.g., \"appeared in 2 of 4 past exams — usually when the semester covered a policy-heavy topic late\")\n- Open-book vs. closed-book differences\n- Take-home vs. in-class differences\n\n**Absent patterns worth noting:**\n- Topics covered in class that have NEVER been tested in past exams — don't skip these, but don't weight them heavily either\n- Topics tested in past exams that aren't in your current syllabus — probably not coming back\n\n### Step 4: Forecast for the upcoming exam\n\n**Header — required, first line of the forecast, both in-chat and in the saved file.** Per plugin config `## Outputs`, every study output carries the verbatim study-notes header. The forecast is a study output. Do not omit, rephrase, or relocate the header. The header is not a disclaimer the student can ask to drop; it is the output's identity and prevents the forecast from being mistaken for a predicted exam or for legal advice:\n\n```\nSTUDY NOTES — NOT LEGAL ADVICE\n```\n\nCombine pattern analysis with current syllabus:\n\n```markdown\nSTUDY NOTES — NOT LEGAL ADVICE\n\n# Exam Forecast — [class \u002F professor] — [date]\n\n**Past exams analyzed:** [N]\n**Sample confidence:** [thin (\u003C3) \u002F moderate (3-5) \u002F strong (6+)]\n**Caveats:** [e.g., \"one of the past exams was an open-book final; your upcoming is closed-book. Pattern transfer is partial.\"]\n\n---\n\n## Subject weighting (historical)\n\n| Topic | Past exam weight (avg) | In current syllabus? | Forecast weight |\n|---|---|---|---|\n| [topic 1] | [%] | [yes\u002Fpartial\u002Fno] | [heavier \u002F stable \u002F lighter] |\n\n## Question-style forecast\n\n- **Format likely:** [X issue-spotters + Y short answers + Z policy, or similar]\n- **Fact-pattern density:** [fact-heavy \u002F sparse \u002F mixed]\n- **Call style:** [one broad call \u002F multiple specific calls \u002F bullet sub-parts]\n\n## Professor hobby horses to watch\n\n- [topic A] — appeared in [M of N] past exams. Weighted 3-5x its syllabus share.\n- [topic B] — [pattern]\n- [trap pattern] — e.g., \"hides jurisdictional issue in otherwise-clean facts\"\n\n## Topics covered this semester but rarely tested\n\n[list — don't skip, but don't over-weight]\n\n## Study emphasis recommendation\n\nBased on past exam patterns AND current syllabus coverage:\n\n**Heavy:** [topics likely to anchor the exam — 40-50% of study time]\n**Moderate:** [supporting topics — 30-40%]\n**Sanity check:** [topics covered but historically under-represented — 10-20%, just in case]\n\n## [UNCERTAIN — framing]\n\nThis forecast is derived from [N] past exams. Professors vary. Professors rotate. Topics that were emphasized in past years can be de-emphasized when the syllabus shifts. Treat this as a weighting heuristic for study time, not a prediction. The exam will include surprises.\n```\n\n### Step 5: Output location\n\nWrite to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002Fexam-forecasts\u002F[class]\u002Fforecast-[YYYY-MM-DD].md`. Versioned — if the student gets another past exam mid-semester, re-run and append.\n\n## Integration\n\n- **outline-builder:** forecast weights feed into outline depth decisions — weight depth on heavy topics\n- **flashcards:** forecast-heavy topics get more cards generated\n- **bar-prep-questions:** irrelevant for bar prep (that has its own forecast model); exam-forecast is for class-specific finals\n- **irac-practice:** use forecast topics as the subject areas for IRAC practice hypos\n\n## Close with the next-steps decision tree\n\nEnd with the next-steps decision tree per CLAUDE.md `## Outputs`. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.\n\n## What this skill does not do\n\n- **Predict specific questions.** Past exams show patterns; they don't show you tomorrow's prompt.\n- **Work without past exams.** If you don't have prior exams from this professor, the skill can't forecast — it falls back to \"here's what the syllabus covers, study that.\"\n- **Replace studying everything on the syllabus.** Forecast is weighting, not elimination. Skipping a topic because it's historically under-represented is how students get burned.\n- **Account for changes you don't know about.** If the professor has shifted focus this year (e.g., emphasized a new case in class lectures), the skill doesn't see that unless you tell it.\n- **Work reliably with 1-2 past exams.** Thin sample. Flag as such.\n",{"name":5,"description":44,"argument-hint":45},"Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says \"what's on the exam\", \"analyze past exams\", \"predict the exam\", or shares past exams.\n","[class name, with past exams shared or paths to them]","main","4a6c651889c97cc9140580363c73e0eb17379c2b","law-student\u002Fskills\u002Fexam-forecast",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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add anthropics\u002Fclaude-for-legal --skill exam-forecast",{"tool":60,"command":61},"bunx","bunx skills add anthropics\u002Fclaude-for-legal --skill exam-forecast",{"tool":63,"command":64},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-for-legal --skill exam-forecast","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Flaw-student\u002Fskills\u002Fexam-forecast\u002FSKILL.md",true,[],[69,98,119,137,159,172],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":80,"publishedAt":39},"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",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[81,82,83,84,85,86,87,88,34,89,90,91,31,92,30,93,94,95,96,97],"reg","watcher","reg feed watcher","running","feeds","filtered","diff","development","classification","new","now","scheduled","check","last","update","report","regulatory",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":39},"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",[],[32,105,87,34,106,107,108,31,109,30,110,111,112,113,114,115,116,117,97,118],"policy redraft","up","fix","produce","documents","drafting","gaps","review","draft","id","gap","mark","first","direct",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":39},"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",[],[87,32,126,127,30,128,129,81,130,82,131,132,133,134,31,135,115,136,25,97],"policy diff","which","you","analysis","text","change","paste","library","material","gap analysis","what the",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":39},"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",[],[144,145,127,146,147,148,90,31,30,128,149,150,151,152,153,154,155,156,157,158],"workspace","matter workspace","switch","manage","workspaces","keep","across","create","engagement","close","active","clients","list","it","context",{"skillNo":160,"name":111,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":39},"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,114,115,165,153,166,167,168,169,31,170,30,171],"risk","tracker","remediation","status","open","accept","user",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":183,"publishedAt":39},"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",[178],{"categoryNo":179,"categoryName":180,"taxonomyType":181,"taxonomyTypeDesc":182},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[115,184,38,185,87,32,186,169,187,188,189,190,111,28,191,192,193,166,167,194],"gap surfacer","tracks","send","confirmation","aging","false","comments","work","slack","via","surfaces"]