CC divorce-ct-stephane-boghossian
Claude skill that turns Claude into a Connecticut-specific divorce planner — nine operating modes from pre-flight intake to post-judgment modification, modeled on Untangle.us's feature surface and grounded in C.G.S. Title 46b, Practice Book Chapter 25, and the 2026-08-01 CCSG schedule. Covers eligibility triage (nonadversarial under § 46b-44a vs standard), financial affidavit (JD-FM-6), child support (JD-FM-220 / CCSG-1 / 1A), alimony (§ 46b-82 fourteen factors), parenting plan (with GAL/AMC escalation under JD-FM-224), settlement agreement (JD-FM-172, TCJA-aware), filing packet (marshal 12-day rule, $360 + $50 fees, JD-FM-75 waiver), and post-judgment motion practice. Hard UPL gate: refuses non-CT, domestic violence (refers CTCADV 1-888-774-2900), hidden assets, courtroom advocacy. Heppner-aware: AI prompts are not privileged. First family-law skill in the Lawvable registry.
Claude skill that turns Claude into a Connecticut-specific divorce planner — nine operating modes from pre-flight intake to post-judgment modification…
As a process C 61/100 · Has gaps — weak spots: inputs and preconditions, consistency, execution cost
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 11535 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 61/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 14 mutating operations with no state check
- 40Consistency. Frontmatter name (divorce-ct-stephane-boghossian) differs from the folder (connecticut-divorce-planner-stephane-boghossian)
- 40Execution cost. Instruction body is 11535 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 8 branches
- 85Steps. 299 steps, 2 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 18 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 888: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 57 headings
- +3Step-by-step instructions: 299 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.