CtrlK
BlogDocsLog inGet started
Tessl Logo

litigation-update-post

Writes public-facing litigation updates — blog posts, client alerts, LinkedIn/X posts — on a federal case or legal development. Use to "write a blog post about…," "draft a client alert on…"

80

Quality

100%

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

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.

A well-structured skill body: a clear multi-step method with verification boundaries, concrete tool usage, format-specific anatomies, and a clean reference structure where every cited file exists. It adds only domain-specific guidance Claude would not already know.

DimensionReasoningScore

Conciseness

The ~80-line body is dense with domain-specific, non-obvious guidance (procedural-timing framing, the rule that web research never verifies law, Midpage tool-usage constraints) and avoids explaining concepts Claude already knows; length is justified by a genuinely complex process rather than padding.

3 / 3

Actionability

Gives concrete, executable guidance throughout — named tools and fields (analyzeOpinion, supportedPropositions, deeplinkURL, doesNotAddress), specific word-count targets per format, and verbatim disclaimer/byline text — making the instructions copy-paste ready despite being instruction-only.

3 / 3

Workflow Clarity

An 8-step Method is clearly sequenced with an explicit steering check-in (step 5) and layered verification rules (analyzeOpinion is what permits a citation; check doesNotAddress before citing; never invent dates), satisfying the explicit-checkpoint anchor.

3 / 3

Progressive Disclosure

The body is an overview that signals one-level-deep references at the right moments (litigation-writing.md, citations.md, court-rules.md, legal-docx.md), all of which exist as real bundle files, with detail appropriately split out rather than inlined.

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: third-person, concrete, with both a clear capability statement and explicit quoted trigger phrases for when to invoke it. It names multiple output formats and a precise subject area, minimizing conflict risk.

DimensionReasoningScore

Specificity

Names the concrete action ("Writes public-facing litigation updates") and enumerates three specific output formats — blog posts, client alerts, LinkedIn/X posts — on a federal case or legal development, matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Clearly answers both what (writes litigation updates across three formats on a federal case or legal development) and when (explicit "Use to…" trigger clause with quoted phrasings), matching the anchor requiring both what and when with explicit triggers.

3 / 3

Trigger Term Quality

Includes verbatim natural user phrasings ("write a blog post about…", "draft a client alert on…") plus LinkedIn/X, giving good coverage of terms users actually say; the slight grammatical awkwardness of "Use to" keeps it at rather than above the top anchor.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — public-facing, firm-bylined litigation-update writing tied to federal cases/legal developments with distinct triggers — making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
openai/plugins
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.