CtrlK
BlogDocsLog inGet started
Tessl Logo

process-letter

Draft process letters and bid instructions for sell-side M&A processes. Covers initial indication of interest (IOI) instructions, final bid procedures, and management meeting logistics. Triggers on "process letter", "bid instructions", "IOI letter", "bid procedures", "final round letter", or "management meeting invite".

76

Quality

93%

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

87%

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

The body is a concise, well-structured drafting guide with concrete per-letter-type checklists, but its workflow validation is informal — client/legal review is mentioned yet not framed as an explicit checkpoint with a revision loop.

Suggestions

Add an explicit validation gate, e.g. a 'Step 6: Review & Approve' step framing legal/client review as a validate→fix→proceed loop before sending.

Include a short sample process letter template (header + one IOI section) so the output guidance is closer to copy-paste ready.

Note the process-tracker logging step (who received each letter and when) as a concrete closing action rather than only a passive reminder.

DimensionReasoningScore

Conciseness

Lean bullet-style sections with no padding or explanation of M&A concepts Claude already knows; every line earns its place.

3 / 3

Actionability

An instruction-only skill giving concrete section-by-section guidance (e.g., IOI Requirements lists valuation range, consideration form, financing sources), which meets the actionable bar without needing code.

3 / 3

Workflow Clarity

A clear 5-step sequence is present, but validation checkpoints are soft and implicit ('Client should review and approve before sending') rather than an explicit validate→fix→proceed gate, with no feedback loop for revisions.

2 / 3

Progressive Disclosure

A single, compact (~76 line), well-organized file with clearly labeled sections and no nested references; given its size and single purpose, keeping content inline is appropriate.

3 / 3

Total

11

/

12

Passed

Description

100%

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 that states concrete capabilities and supplies an explicit, well-chosen set of trigger phrases covering both what the skill does and when to invoke it. It is concise, distinctive, and free of vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Draft process letters and bid instructions,' 'Covers initial indication of interest (IOI) instructions, final bid procedures, and management meeting logistics' — rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' ('Draft process letters and bid instructions for sell-side M&A processes') and 'when' (a dedicated 'Triggers on...' clause), matching the anchor that requires both.

3 / 3

Trigger Term Quality

Provides strong natural-term coverage: 'Triggers on "process letter", "bid instructions", "IOI letter", "bid procedures", "final round letter", or "management meeting invite"' — terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (sell-side M&A process letters) with distinct, domain-specific triggers 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
anthropics/financial-services
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.