dei-statement-drafter
Draft Diversity, Equity, and Inclusion statements for academic applications.
38
23%
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/dei-statement-drafter/SKILL.mdQuality
Discovery
40%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 identifies a clear and distinctive niche—drafting DEI statements for academic applications—but is too terse. It lacks a 'Use when...' clause, misses common trigger term variations (e.g., 'DEI statement,' 'diversity statement,' 'faculty application'), and only names a single action rather than listing the range of capabilities the skill offers.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks for help writing a diversity statement, DEI essay, or inclusion narrative for academic job, fellowship, or graduate school applications.'
Include common trigger term variations such as 'DEI statement,' 'diversity statement,' 'inclusion statement,' 'faculty application,' 'postdoc application,' and 'grad school.'
Expand the list of concrete actions beyond 'draft,' e.g., 'Draft, revise, and tailor Diversity, Equity, and Inclusion statements for academic job, fellowship, and graduate school applications.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DEI statements for academic applications) and one action (draft), but does not list multiple specific concrete actions like editing, reviewing, tailoring to specific institutions, or formatting. | 2 / 3 |
Completeness | Describes what the skill does (drafts DEI statements) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Diversity, Equity, and Inclusion statements' and 'academic applications,' but misses common variations users might say such as 'DEI statement,' 'diversity statement,' 'faculty application,' 'grad school application,' or 'job application essay.' | 2 / 3 |
Distinctiveness Conflict Risk | The combination of DEI statements specifically for academic applications is a clear, narrow niche that is unlikely to conflict with other skills. The domain is quite distinct. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is almost entirely generic boilerplate with very little DEI-statement-specific content. It reads like a template that was filled in with the skill name but never given actual domain expertise or concrete examples. The few DEI-relevant sections (Statement Components, Parameters) are superficial bullet lists without actionable guidance on how to actually draft a quality DEI statement.
Suggestions
Replace the generic boilerplate with concrete DEI statement writing guidance: include at least one full example input (experiences) and corresponding output (drafted statement) showing the expected quality and structure.
Add specific, actionable writing patterns for each statement component (personal background, experiences, future plans) with concrete examples of strong vs weak content.
Remove or drastically compress the generic sections (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Response Template) that consume tokens without adding DEI-specific value.
Fix the circular cross-references ('See ## Prerequisites above' appearing before Prerequisites) and consolidate the workflow into a single clear sequence with DEI-specific validation steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with boilerplate sections that add no value for Claude. Sections like 'Risk Assessment', 'Security Checklist', 'Lifecycle Status', 'Evaluation Criteria', and 'Response Template' are generic filler. Multiple sections reference each other circularly ('See ## Prerequisites above', 'See ## Usage above'). The actual DEI-specific content is minimal compared to the overall length. | 1 / 3 |
Actionability | Despite referencing scripts/main.py extensively, there is no actual executable code or concrete DEI statement drafting guidance. The skill never shows how to actually write a DEI statement - no examples of input experiences, no example output statements, no concrete writing patterns. The 'Statement Components' section is just a bullet list of vague categories with no actionable detail. | 1 / 3 |
Workflow Clarity | The workflow section is entirely generic ('Confirm the user objective', 'Validate that the request matches the documented scope') with no DEI-specific steps. There are no validation checkpoints specific to the task. The 'Example run plan' is also generic boilerplate. No feedback loop exists for reviewing or improving the drafted statement. | 1 / 3 |
Progressive Disclosure | There is a reference to references/audit-reference.md and the references/ directory, which shows some attempt at progressive disclosure. However, the main file itself is bloated with content that should either be removed or split out, and the sections are poorly organized with circular cross-references. | 2 / 3 |
Total | 5 / 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
0b96148
- 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.