CtrlK
BlogDocsLog inGet started
Tessl Logo

stakeholder-summary

Translates a contract review into a summary the business stakeholder will actually read. Not a legal memo — a two-minute answer to "can I sign this and what do I need to know." Use when user says "summarize for the business", "write this up for [stakeholder]", "explain this to procurement", "non-legal summary", or when a review is done and needs to go to someone outside legal.

72

Quality

87%

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

85%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 dense, actionable instruction-only skill with clear sequenced workflows and validation checkpoints. The only real gap is conciseness, where some sections repeat each other and the escalation reconciliation runs long.

Suggestions

Consolidate the overlapping intent of the "Purpose" section and "A note on tone" so the verdict-is-fine-say-so guidance is stated once.

Tighten the "Escalation-fan-out reconciliation" section: the numbered tally steps could be shortened while preserving the N/M reconciliation logic.

Consider whether the matter-context paragraph and destination-check section belong inline or could be trimmed to a one-line pointer, since both largely defer to the plugin CLAUDE.md anyway.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but at ~180 lines it carries some redundancy (the Purpose and "A note on tone" sections overlap) and the escalation-fan-out reconciliation could be tightened.

2 / 3

Actionability

Concrete, copy-paste-ready markdown templates, a legal-finding-to-business-translation table, an explicit "what NOT to include" list, and a tight checklist structure give fully actionable, specific guidance for an instruction-only skill.

3 / 3

Workflow Clarity

A clear sequence (matter context → destination check → side → audience → summary → reconciliation → handoffs) with explicit validation checkpoints: tracker-entry verification before asserting claims and the N-vs-M escalation reconciliation.

3 / 3

Progressive Disclosure

No bundle files exist to verify against; the skill is well-organized into clearly signaled sections with only one-level-deep references to plugin CLAUDE.md and sibling skills, so the self-contained structure scores well.

3 / 3

Total

11

/

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 strong, third-person description with explicit "Use when" triggers and natural user phrasing. Its only weakness is specificity, which describes one action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

Names a concrete domain and action ("Translates a contract review into a summary the business stakeholder will actually read"), but it is a single core action rather than a list of multiple specific actions, so it stops short of the top anchor.

2 / 3

Completeness

Explicitly answers both what it does and when to use it, with an explicit "Use when..." clause covering both verbatim phrases and the situational trigger ("when a review is done and needs to go to someone outside legal").

3 / 3

Trigger Term Quality

Four quoted natural phrases a user would actually say ("summarize for the business", "write this up for [stakeholder]", "explain this to procurement", "non-legal summary") give good coverage of natural trigger terms.

3 / 3

Distinctiveness Conflict Risk

The stakeholder-summary niche is clearly bounded and its triggers (summarize for business / non-legal summary) are distinct from sibling review skills, making wrong-skill activation unlikely.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.