CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dei-statement-drafter

Draft Diversity, Equity, and Inclusion statements for academic applications.

Quality

63%

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/dei-statement-drafter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 well structured with a real, clearly-signaled one-level-deep reference and a coherent workflow with explicit validation and fallback checkpoints, but it is undermined by generic template boilerplate, self-referential filler, and duplicated commands. Most critically, it contains almost no actual DEI-statement drafting guidance — the skill's substance — beyond pointing at a script.

Suggestions

Replace the meta-boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Key Features) with actual DEI drafting guidance: templates for faculty/postdoc/grant statements, an example statement, and best practices — or move them to a reference file.

Remove the self-referential filler lines ('See ## Prerequisites above', 'See ## Usage above') and the duplicated py_compile command (it appears in Example Usage, Quick Check, and Audit-Ready Commands).

Move detailed drafting content into references/ (e.g., references/templates.md, references/best-practices.md) and keep SKILL.md as a lean overview with clearly signaled one-level-deep links, improving both conciseness and progressive disclosure.

DimensionReasoningScore

Conciseness

Several sections are padded boilerplate rather than task-specific guidance: 'Key Features' ('Structured execution path designed to keep outputs consistent and reviewable'), self-referential filler ('See ## Prerequisites above', 'See ## Usage above'), the same py_compile command repeated in three sections, and generic template blocks (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that say nothing specific to DEI drafting. This matches 'Noticeably verbose; several unnecessary explanations or padded sections'.

2 / 5

Actionability

There are concrete executable commands ('python -m py_compile scripts/main.py', 'python scripts/main.py --help', a usage example with real flags) and a parameters table matching the actual script, but the core domain guidance is missing: nothing explains how to actually draft a good DEI statement (no template text, examples, or best practices inline — only a --best-practices flag). This matches 'Some concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

The Workflow section gives a clear 5-step sequence with explicit checkpoints: 'stop early if the task would require unsupported assumptions' and a fallback path ('switch to the fallback path and state exactly what blocked full completion'), reinforced by the Error Handling section. It falls short of 5 because the steps are abstract boilerplate rather than concrete, executable per-step actions tied to the script.

4 / 5

Progressive Disclosure

The bundle structure is well used: 'references/audit-reference.md' is a real file, clearly linked from the References section, one level deep, and the script entry point is consistently named. It is not 5 because substantial generic content (risk/security/evaluation checklists) that belongs in a reference file is inlined in SKILL.md instead of being split out.

4 / 5

Total

13

/

20

Passed

Description

57%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 is concise and names a clear, distinctive niche, but it stops at a single action and omits any 'use when' trigger guidance or common synonyms (DEI statement, diversity statement, grant proposals) that would help a user or Claude select it. It sits at the midpoint of the rubric.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions DEI statements, diversity statements, or needs an inclusion statement for faculty, postdoc, or grant applications.'

Include natural synonyms and variations users actually say — 'DEI statement', 'diversity statement', 'job market materials' — to improve trigger term coverage.

Briefly enumerate the concrete outputs (e.g., structured statement, section suggestions, best-practice tips) to raise specificity beyond a single 'Draft' action.

DimensionReasoningScore

Specificity

The description names the domain ('Diversity, Equity, and Inclusion statements for academic applications') and one concrete action ('Draft'), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It does not list multiple concrete actions (e.g., revising, tailoring to faculty/postdoc/grant contexts) that would warrant a 4.

3 / 5

Completeness

The 'what' is clear (draft DEI statements for academic applications) but there is no 'when' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3 ('Has a clear what but when is missing or only weakly implied'). A 4 would require at least a weakly explicit 'Use when...' clause.

3 / 5

Trigger Term Quality

'Diversity, Equity, and Inclusion statements' and 'academic applications' are relevant natural phrases, but common variations users would actually say — 'DEI statement', 'diversity statement', 'job application', 'grant proposal' — are missing, matching 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

Drafting DEI statements for academic applications is a clear niche with distinct triggers and minimal overlap with other skills; nothing generic remains that would cause it to fire for unrelated tasks.

5 / 5

Total

14

/

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/dei-statement-drafter/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.