plain-english-translation

Translates every clause of a contract from legalese into clear, plain English with flags for deliberately confusing or misleading language

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/legal-plain/SKILL.md

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.

The body is highly actionable and clearly sequenced with a complete output template, making it easy to follow. It loses points for restating the description and concepts Claude already knows, and for keeping all content in one monolithic file rather than offloading the large template to a reference.

Suggestions

Trim the opening "You are an AI Legal Translator..." paragraph, which duplicates the frontmatter description, and replace the pre-filled glossary rows with a single "add only terms that appear in this contract" instruction.

Move the large output template (lines 69–159) into a references file (e.g. references/output-template.md) and link to it, keeping SKILL.md as a concise overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and instructional, but the opening paragraph ("You are an AI Legal Translator... You help non-lawyers...") restates the description, and the pre-filled glossary rows (Indemnify, Liquidated damages, etc.) explain legal concepts Claude already knows.	2 / 3
Actionability	The skill provides a concrete step-by-step process, five precisely defined flag types, and a complete copy-paste markdown output template with a specific filename pattern, giving fully actionable guidance.	3 / 3
Workflow Clarity	Five steps are clearly sequenced (read → translate sections → add callouts → summary → write output) with an explicit "include every section, even boilerplate" check; the task is non-destructive so no validation feedback loop is required.	3 / 3
Progressive Disclosure	Content is well-sectioned but monolithic: the entire ~90-line output template is inline in a single file with no references, and the large template could reasonably be split into a separate reference file.	2 / 3
	Total	10 / 12 Passed

Description

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

The description is specific and distinctive, naming concrete translation and flagging actions in a clear niche. Its main weakness is the missing explicit "Use when..." trigger guidance and only partial coverage of natural trigger terms.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when a user asks to understand a contract, wants legalese translated to plain English, or needs confusing clauses flagged."

Broaden trigger terms to include natural variations like "agreement", "terms of service", "fine print", and "legal jargon".

Dimension	Reasoning	Score
Specificity	"Translates every clause of a contract from legalese into clear, plain English" and "flags for deliberately confusing or misleading language" name multiple distinct, concrete actions, matching the anchor that lists several specific actions.	3 / 3
Completeness	The description clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	"contract", "legalese", and "plain English" are natural terms a user might say, but common variations like "agreement", "terms", "fine print", or "legal jargon" are missing, so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	"Translates...contract from legalese into...plain English with flags for deliberately confusing or misleading language" carves out a clear niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: zubair-trabzada/ai-legal-claude
Path: skills/legal-plain/SKILL.md
Commit: 19ece98

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.