semester-handoff

End-of-semester case handoff memos — the mirror of /ramp. Produces per-case transition memos and a cohort summary so the departing cohort hands work to the incoming cohort cleanly. Reads deadlines, client-comms, and case history. Use when the professor or departing students need to wrap up the semester, build transition memos, or offboard a graduating/withdrawing student.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%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, actionable skill body with a clear sequenced workflow and an explicit review gate for consequential case transitions. The only weakness is token efficiency — a motivational Purpose narrative and some repetition between the quick-start summary and the detailed Workflow could be tightened.

Suggestions

Tighten the Purpose section: drop the narrative color ("Two weeks are wasted re-learning… calls go unanswered… questions already answered get asked again") and keep one sentence on why handoff memos matter, since the rest is motivational rather than action-guiding.

Reduce duplication between the top quick-start list (steps 1–7) and the detailed Workflow section — either collapse the quick-start list into a one-line summary or fold its detail into the Workflow so the same steps aren't stated twice.

Trim the audience/load-context prose where it restates information already implied by the workflow inputs, leaving only what Claude needs to execute.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient templates and a clear 5-step workflow, but the Purpose narrative ("Two weeks are wasted re-learning the case… calls go unanswered… questions already answered get asked again") is motivational color, and the top quick-start list repeats the detailed Workflow. Not 3 because some tokens don't earn their place; not 1 because there is no over-explanation of concepts Claude already knows.	2 / 3
Actionability	Provides fully concrete, copy-paste-ready memo and cohort-summary templates with exact section headers, tables, and placeholder fields, plus specific file paths and integration points — actionable guidance for an instruction-only skill.	3 / 3
Workflow Clarity	Five clearly sequenced steps with an explicit validation gate in Step 4 ("Case-closing memos always get professor sign-off before the case is marked closed") and a feedback loop (professor approves, edits, or returns), plus an input-validation checkpoint in Step 1 ("Ask for it. Don't guess."). Not 2 because validation checkpoints are present for this consequential/batch operation.	3 / 3
Progressive Disclosure	No bundle files exist, so the single-file skill is scored on organization: clear sections (Purpose, Audience, Load context, Workflow, Integration, What this skill does not do) with easy navigation, and the inline templates are the core deliverable rather than awkwardly-dumped reference material.	3 / 3
	Total	11 / 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, third-person description that names concrete actions, gives an explicit "Use when" trigger clause, and carves out a distinct niche. Voice is correctly third person throughout, so no specificity penalty applies.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Produces per-case transition memos and a cohort summary", "Reads deadlines, client-comms, and case history", "offboard a graduating/withdrawing student" — matching the highest anchor; not 2 because the actions are comprehensive rather than partial.	3 / 3
Completeness	Explicitly answers both what ("Produces per-case transition memos and a cohort summary") and when (an explicit "Use when the professor or departing students need to wrap up the semester…" clause with multiple triggers).	3 / 3
Trigger Term Quality	Natural terms the audience would actually say — "wrap up the semester", "build transition memos", "offboard a graduating/withdrawing student", "end-of-semester case handoff memos" — giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche — legal-clinic end-of-semester handoff, explicitly "the mirror of /ramp" — with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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: anthropics/claude-for-legal
Path: legal-clinic/skills/semester-handoff/SKILL.md
Commit: 4a6c651

Reviewed: 6 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.