CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recommendation-letter-assistant

Helps faculty and mentors draft standardized recommendation letters for.

Quality

56%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/recommendation-letter-assistant/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is dominated by generic administrative boilerplate and circular cross-references rather than task-specific letter-drafting guidance, hurting token efficiency and actionability. Real assets exist in the bundle (scripts/main.py with concrete templates, references/guidelines.md with AAMC/ERAS guidance) but the body fails to surface them specifically. Consolidating the three overlapping workflow sections and linking the real reference file would substantially improve the skill.

Suggestions

Cut the boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) and the circular "See `## X` above" lines; keep only guidance that changes how Claude drafts the letter.

Replace the generic "`references/` contains supporting rules" mention with an explicit link, e.g. "See [references/guidelines.md](references/guidelines.md) for AAMC/ERAS and specialty-specific LOR requirements".

Merge Workflow, Example run plan, and Implementation Details into one sequenced section with a concrete validation checkpoint (e.g., run `python scripts/main.py demo` and verify the output matches the documented JSON schema before generating the user's letter).

Remove time-sensitive details (dated example path, Next Review Date) or move them out of the main body, since they penalize conciseness and will go stale.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with several padded sections: circular self-references ("See `## Features` above for related details", "See `## Prerequisites` above"), generic boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status), and time-sensitive filler ("Next Review Date: 2026-03-06", dated example path "20260318/scientific-skills/..."). This matches the 'noticeably verbose; several unnecessary explanations or padded sections' anchor rather than a 3, because the padding is systematic across multiple sections rather than a few stray instances.

2 / 5

Actionability

There is some concrete guidance — executable commands (`python -m py_compile scripts/main.py`, `python scripts/main.py demo`), an Input Parameters table, and an Output Format JSON schema — but the core letter-drafting guidance remains abstract ("Competency-based content suggestions", "Strength/weakness framing" with no examples), and the Example Usage hardcodes a dated directory path. This fits the 'some concrete guidance but incomplete; missing key details' anchor; it is not a 4 because a reader still cannot execute the actual letter-generation task end-to-end from the body alone.

3 / 5

Workflow Clarity

The Workflow section lists a five-step sequence with stop-early and fallback logic, and Error Handling adds per-failure paths, but checkpoints are implicit rather than concrete (no validate-then-proceed step tied to an actual command or output check), and the sequence is duplicated across three overlapping sections (Workflow, Example run plan, Implementation Details), which creates ambiguity. This matches the 'steps listed but validation gaps; checkpoints missing or implicit' anchor rather than a 4.

3 / 5

Progressive Disclosure

The bundle provides references/guidelines.md and scripts/main.py, but the body only gestures generically ("Reference guidance: `references/` contains supporting rules, prompts, or checklists") without naming or linking the actual reference file, and generic administrative content that belongs in a separate file is inlined in SKILL.md. This fits the 'references present but not clearly signaled' anchor; it is not a 4 because the actual useful detail (AAMC/ERAS guidelines in references/guidelines.md) is never pointed to explicitly.

3 / 5

Total

11

/

20

Passed

Description

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

The description communicates a recognizable domain but is grammatically truncated ("...recommendation letters for.") and entirely lacks a 'Use when' trigger clause, capping completeness. Trigger coverage omits the natural synonyms (LOR, letter of recommendation, reference letter) users would most likely say. Fixing the sentence and adding an explicit trigger clause would move it toward the good examples.

Suggestions

Complete the truncated sentence, e.g. "Helps faculty and mentors draft standardized letters of recommendation for residency, fellowship, and faculty positions. Use when the user asks to write, revise, or structure a letter of recommendation (LOR) or reference letter."

Add natural trigger synonyms such as "letter of recommendation", "LOR", "reference letter", and "residency application" so the skill triggers on the phrasings users actually say.

Name 1-2 more concrete capabilities (e.g., competency-based framing, MSPE/Dean's Letter alignment) to raise specificity beyond a single action.

DimensionReasoningScore

Specificity

"Helps faculty and mentors draft standardized recommendation letters for" names the domain and one concrete action (drafting standardized letters), matching the 'names domain and 1-2 concrete actions' anchor, but it is not comprehensive and the sentence is truncated mid-phrase ("for."), leaving the object of the letter unspecified. It is not a 4 because no additional specific actions or capabilities are listed.

3 / 5

Completeness

The description has a clear 'what' (draft standardized recommendation letters) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

"recommendation letters", "faculty", and "mentors" are relevant natural keywords, but common variations users would actually say are missing: "letter of recommendation", "LOR", "reference letter", "residency", or "MSPE". This matches the 'some relevant keywords but missing common variations or synonyms' anchor; it is above a 2 because the present terms are domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

"recommendation letters" for "faculty and mentors" carves out a fairly distinct academic-writing niche with minor overlap risk against general academic-writing or cover-letter skills. It is not a 5 because the truncated description gives no concrete trigger phrases that would fully separate it from adjacent writing-assistant skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/recommendation-letter-assistant/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.