CtrlK
BlogDocsLog inGet started
Tessl Logo

matter-update

Append a dated event to a matter's history file and refresh the log row — captures new developments, status changes, risk re-assessments, deadline shifts, and settlement authority changes. Use when the user wants to log an update on a matter, note a development, or record a status change against the portfolio.

79

Quality

100%

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

100%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.

The body delivers a tight, fully-actionable workflow with strong validation gates and feedback loops, organized into clearly labeled sections. It is self-contained and appropriately scoped for a single-purpose legal-matter update skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what a matter, history file, or yaml log is — and each section earns its tokens with specific guidance rather than padding.

3 / 3

Actionability

Concrete file paths, exact log field lists, ready-to-deliver prompt text, and a copy-paste markdown template for the history entry make the guidance fully executable rather than descriptive.

3 / 3

Workflow Clarity

A clear sequence (load context → conflicts gate → input → update → write → confirm) carries multiple explicit validation checkpoints (unbypassable conflicts gate, settlement-acceptance gate, explicit materiality prompt, show-diff-before-write confirm).

3 / 3

Progressive Disclosure

No bundle files exist, so the self-contained body is judged on its own organization; sections are well-labeled and navigable, which the rubric permits to score 3 for a focused single-purpose skill without external references.

3 / 3

Total

12

/

12

Passed

Description

100%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 strong description: it names concrete actions, provides explicit 'Use when' trigger guidance with natural phrasing, and occupies a clearly distinct legal-matter niche. It answers what and when without verbosity or over-claim.

DimensionReasoningScore

Specificity

Concrete actions are stated ('Append a dated event to a matter's history file and refresh the log row') alongside enumerated capture types (developments, status changes, risk re-assessments, deadline shifts, settlement authority changes), matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

It explicitly answers both 'what' (append dated event, refresh log row, capture enumerated change types) and 'when' via an explicit 'Use when...' clause, satisfying the full both-anchors requirement.

3 / 3

Trigger Term Quality

'Use when the user wants to log an update on a matter, note a development, or record a status change against the portfolio' uses natural phrasing a user would actually say, with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The matter/legal-portfolio update niche has distinct triggers tied to logging matter updates, making it unlikely to fire for unrelated skills; voice is consistently third person.

3 / 3

Total

12

/

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.