CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brief

Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

A well-structured, actionable instruction skill: concrete output templates, per-source scan guidance, and prudent professional notes (privilege, litigation holds, GDPR deadlines). Main improvement areas are trimming minor redundancy and splitting the mode specifications into reference files.

Suggestions

Split each mode specification (daily, topic, incident) into a one-level-deep reference file (e.g., references/daily.md), leaving SKILL.md as a concise overview with mode selection guidance.

Remove the Invocation code block, which duplicates the frontmatter argument-hint and the mode headers, and fold the no-mode fallback into a single sentence.

Add one short worked example of a filled daily brief (with realistic redacted items) to make the output guidance fully concrete.

DimensionReasoningScore

Conciseness

Nearly every token earns its place — scan checklists and output skeletons rather than concept explanations — but the Invocation block duplicates the frontmatter argument-hint and mode headers, and the repeated "(if connected)" per-source lists carry mild redundancy.

4 / 5

Actionability

Concrete, executable instruction guidance: full output-format templates per mode, specific scan targets per source, and precise facts like "72 hours for GDPR" and "flag litigation hold". Falls short of fully copy-paste-ready because no worked example of a filled brief is given and the search strategy stays high-level.

4 / 5

Workflow Clarity

Topic and incident modes have numbered step sequences, and coverage checkpoints exist via "Sources Not Available", "Sources Checked", and "Gaps" sections. The daily mode lacks an explicit step sequence, keeping it below the top anchor; the destructive/batch validation cap does not apply since this is read-only synthesis.

4 / 5

Progressive Disclosure

Well-organized single file with clear per-mode sections and a clearly signaled, one-level-deep reference (CONNECTORS.md). The three ~60-line mode specifications are candidates for one-level reference files, which keeps it below the ideal overview-plus-references structure.

4 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

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: third-person, concrete, with explicit what-and-when structure and scenario-based triggers. Its only weaknesses are slightly incomplete source coverage and a few missing natural synonyms.

DimensionReasoningScore

Specificity

Names the legal-briefing domain and lists several concrete actions ("daily summary, topic research, or incident response", "scan of legal-relevant items across email, calendar, and contracts"), but omits the chat, CLM, CRM, and documents sources the body actually covers — minor gaps in coverage that keep it below the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what ("Generate contextual briefings for legal work — daily summary, topic research, or incident response") and when (three concrete "Use when…" clauses covering daily, research, and incident triggers), matching the top anchor's structure.

5 / 5

Trigger Term Quality

Includes natural user phrasings like "starting your day", "researching a specific legal question", and "data breach, litigation threat, regulatory inquiry", but misses common synonyms such as "morning brief", "legal research", or "compliance" that users might say.

4 / 5

Distinctiveness Conflict Risk

A clear legal-team niche with distinct triggers (data breach, litigation threat, regulatory inquiry), but the generic morning-scan framing ("starting your day… email, calendar") leaves minor overlap risk with a general daily-digest skill.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

anthropics/knowledge-work-plugins

Path

legal/skills/brief/SKILL.md

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.