personal-statement
Use when writing medical school personal statements, residency application essays, fellowship statements, or graduate school admissions essays. Crafts compelling narratives highlighting clinical experiences, research achievements, and career motivations for healthcare education applications.
64
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Academic Writing/personal-statement/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger term coverage and completeness, clearly specifying both when to use it and what it does. The explicit 'Use when' clause with multiple specific application types makes it highly selectable. The main weakness is that the capability description could be more specific about concrete actions (drafting, editing, structuring) rather than focusing on narrative qualities.
Suggestions
Add more concrete action verbs describing what the skill does, e.g., 'Drafts, structures, and revises medical school personal statements' rather than just 'crafts compelling narratives.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (medical/healthcare admissions essays) and mentions some actions like 'crafts compelling narratives highlighting clinical experiences, research achievements, and career motivations,' but doesn't list multiple distinct concrete actions (e.g., drafting, editing, structuring, reviewing). The actions are more about what the output contains than what the skill does. | 2 / 3 |
Completeness | The description explicitly answers both 'what' (crafts compelling narratives highlighting clinical experiences, research achievements, and career motivations) and 'when' (starts with 'Use when writing medical school personal statements, residency application essays, fellowship statements, or graduate school admissions essays'). The 'Use when' clause is explicit and detailed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'personal statements,' 'residency application essays,' 'fellowship statements,' 'graduate school admissions essays,' 'clinical experiences,' 'research achievements,' 'healthcare education applications.' These are terms applicants would naturally use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a very clear niche in healthcare/medical education admissions writing. The specific triggers like 'medical school personal statements,' 'residency application,' and 'fellowship statements' are highly distinctive and unlikely to conflict with general writing or non-medical admissions skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill suffers from heavy boilerplate and generic template content that dilutes the genuinely useful domain-specific guidance (character limits table, STAR method, structure percentages, quality checklist, common pitfalls). The workflow sections are entirely generic and not tailored to personal statement writing. The useful medical education content is buried under layers of redundant scaffolding about input validation, error handling, and response templates that Claude already knows.
Suggestions
Remove all generic boilerplate sections (Output Requirements, Error Handling, Input Validation, Response Template, Implementation Details) and the repeated description text in 'When to Use' and 'Key Features' — these add no domain-specific value.
Replace the generic 5-step Workflow with a personal-statement-specific writing workflow: e.g., 1) Gather experiences and motivations, 2) Draft opening hook, 3) Structure body using the 5-section outline, 4) Apply STAR method to each experience, 5) Check against quality checklist, 6) Optimize to character limit.
Consolidate the 'Quick Start', 'Example Usage', and 'Core Capabilities' sections — currently the skill has three different entry points that create confusion about whether this is a CLI tool, a Python library, or a writing guide.
Add a concrete example of a complete personal statement paragraph (input experiences → output narrative) to make the skill truly actionable rather than just describing API calls to potentially non-existent code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with significant redundancy. The 'When to Use' section repeats the description verbatim. 'Key Features' restates the description again. Generic boilerplate sections (Output Requirements, Error Handling, Input Validation, Response Template) add ~40% bloat that Claude already knows how to handle. Implementation Details says 'See Workflow above' then repeats similar content. | 1 / 3 |
Actionability | The Core Capabilities section provides concrete Python API examples with specific parameters (program_type, character_limit, STAR method), the character limits table is useful, and the quality checklist is actionable. However, the code references non-existent modules (PersonalStatementWriter) without confirming they exist, and the generic workflow steps (1-5) are abstract rather than specific to personal statement writing. | 2 / 3 |
Workflow Clarity | The main 'Workflow' section is entirely generic boilerplate ('Confirm the user objective...', 'Validate that the request matches...') with no personal-statement-specific steps. There are no validation checkpoints for the actual writing process. The 'Example run plan' is also generic. The quality checklist partially compensates but isn't integrated into a clear sequential workflow. | 1 / 3 |
Progressive Disclosure | References to external files exist (references/personal-statement-examples.md, scripts/main.py) and the content is sectioned with headers. However, the skill is monolithic with substantial inline boilerplate that should be removed rather than split out, and the reference to 'See ## Workflow above' in Implementation Details is a confusing self-reference. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- aipoch/medical-research-skills
- Commit
8277276
- 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.