CtrlK
BlogDocsLog inGet started
Tessl Logo

draft-long-form-memo

Writes a formal objective legal research memo (Questions Presented, Brief Answers, Facts, IRAC Discussion, Conclusion) as a .docx. Use to "draft a research memo on whether…" Predicts, never advocates.

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, lean instruction skill: it sequences a multi-step research workflow with explicit validation gates, hands Claude concrete tool fields and a rendering snippet, and offloads craft details to real, clearly signaled one-level-deep references. It does not re-explain concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is dense and point-first — it assumes Claude knows what IRAC, a memo, and citation are and never pads with such concepts; every line is task-specific imperative guidance, so it sits at the lean/efficient anchor rather than the 'could be tightened' one.

3 / 3

Actionability

It gives concrete, executable guidance: named Midpage tools with exact filter params (jurisdictionType, circuits/courts/states, publishStatus), specific result fields (doesNotAddress, supportedPropositions, deeplinkURL, centrality, scope, opinionSection), and a copy-paste rendering snippet using D.builders("memo", { lineSpacing: 480 }).

3 / 3

Workflow Clarity

The research method is a clearly sequenced pipeline (Frame → Search → Triage → Branch → analyzeOpinion gate) with explicit validation checkpoints — "Check doesNotAddress first — if your point is listed, the case doesn't stand for it" — and a saturation stopping condition, matching the anchor for clear sequence with explicit validation steps.

3 / 3

Progressive Disclosure

The body is an overview that signals three one-level-deep reference files at the top (litigation-writing.md, citations.md, legal-docx.md), all of which exist on disk, while keeping the core method inline — clear navigation with content appropriately split.

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 tight, third-person description that covers what, when, and how-it-differs with concrete section names and a natural trigger phrase. It avoids fluff and over-claims entirely.

DimensionReasoningScore

Specificity

It names multiple concrete actions and structural parts — "Questions Presented, Brief Answers, Facts, IRAC Discussion, Conclusion" plus the ".docx" output format — matching the anchor that lists several specific concrete actions rather than a vague domain label.

3 / 3

Completeness

It states both what it does (writes a formal objective legal research memo as .docx with named sections) and when to use it ("Use to 'draft a research memo on whether…'") with an explicit trigger, so it is not capped at 2 for a missing trigger clause.

3 / 3

Trigger Term Quality

The quoted phrase "draft a research memo on whether…" is exactly how a user would phrase the request, giving good natural-term coverage rather than jargon or generic wording.

3 / 3

Distinctiveness Conflict Risk

The narrow legal-research-memo niche, named IRAC structure, and the disambiguating "Predicts, never advocates" carve a clear space unlikely to collide with other 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.