CtrlK
BlogDocsLog inGet started
Tessl Logo

case-brief

Brief a case in your preferred format. In drill-me mode, makes the student state the holding first. Use when the user says "brief [case]", "what's the holding in", "case brief", or pastes a case.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instruction skill with an actionable template and clear validation checkpoints, but it is verbose: the central 'don't write the brief for the student' rule is repeated across four sections, and all content is inlined rather than progressively disclosed.

Suggestions

Consolidate the repeated 'don't brief it for me' message into one authoritative section; the other sections can reference it instead of restating it.

Extract the default brief template into a reference file (e.g. references/template.md) and link to it, improving progressive disclosure and trimming the main body.

Trim aphoristic padding (e.g. "A brief you didn't write is a brief you won't remember") where the concrete rules already convey the same point.

DimensionReasoningScore

Conciseness

It avoids explaining concepts Claude already knows, but the same core rule (don't brief it for them) is restated across Confidence discipline, the 'don't brief it for me' rule, Mode fork, and 'What this skill does not do', and aphorisms like "A brief you didn't write is a brief you won't remember" add padding that could be tightened.

2 / 3

Actionability

Concrete, copy-paste-ready brief template plus specific follow-up questions ("What were the key facts the court actually relied on?", "Why did the court reject the dissent's framing?") and explicit per-mode behavior give fully executable guidance.

3 / 3

Workflow Clarity

The drill-me holding check ("If they can't state it, make them read it again") and the [UNCERTAIN]/[VERIFY] flagging act as explicit validation checkpoints within a sequenced load-context → mode-fork → scaffold → review flow.

3 / 3

Progressive Disclosure

Sections are clearly headed and there are no 2+ level nested references, but the full template and detailed mode rules are inline in a single 80+ line file rather than split into a one-level-deep reference, and no bundle files are used.

2 / 3

Total

10

/

12

Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, well-constructed description that clearly answers both what the skill does and when to use it, with natural trigger terms and a distinct niche. The only soft spot is capability specificity, which lists a couple of actions rather than a comprehensive set.

DimensionReasoningScore

Specificity

"Brief a case in your preferred format" and "makes the student state the holding first" name the domain and two actions, but the action list is not comprehensive, matching the anchor that names domain and some actions.

2 / 3

Completeness

It states what the skill does ("Brief a case in your preferred format") and provides an explicit 'Use when...' clause covering several triggers, answering both what and when.

3 / 3

Trigger Term Quality

"Use when the user says 'brief [case]', 'what's the holding in', 'case brief', or pastes a case" gives strong coverage of the natural phrases a user would actually say when they need this skill.

3 / 3

Distinctiveness Conflict Risk

The legal case-briefing niche and triggers like "brief [case]" and "what's the holding in" are distinct and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
anthropics/claude-for-legal
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.