CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nih-biosketch-builder

Generate NIH Biosketch documents compliant with the 2022 OMB-approved.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/nih-biosketch-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 skill has a genuinely strong core: accurate 2022 NIH format requirements, a complete input JSON schema, and runnable CLI commands including PubMed auto-import. But it is wrapped in substantial generic boilerplate, contradictory dependency statements, broken 'See above' cross-references, and inconsistent script paths that dilute token efficiency and leave the real generation workflow without output validation.

Suggestions

Cut the boilerplate meta-sections ('Key Features', 'Implementation Details', 'Output Requirements', 'Response Template', 'Lifecycle Status', 'Functions', 'Evaluation Criteria') and the duplicate '## References' section, keeping only domain-specific guidance.

Fix correctness defects: resolve the 'python-docx, requests' vs 'No additional Python packages required' contradiction, correct the 'See ## Usage/## Workflow above' cross-references (both sections appear later), replace the literal 'cd "20260318/..."' path, and unify the two conflicting script path styles.

Add a real output-validation step to the workflow, e.g. verify the generated DOCX meets the stated limits (<= 5 pages, Arial/Helvetica/Palatino/Georgia at >= 11pt, >= 0.5 inch margins) before returning the deliverable.

DimensionReasoningScore

Conciseness

The body carries several padded boilerplate sections that add no domain knowledge: 'Key Features', 'Implementation Details', 'Output Requirements', 'Response Template', 'Lifecycle Status', and 'Functions' (which just restates the description). It also contains two duplicate '## References' sections and a direct contradiction ('Dependencies: python-docx, requests' vs 'Prerequisites: No additional Python packages required'), matching the 'noticeably verbose; several unnecessary explanations or padded sections' anchor. The genuinely useful material (format requirements, input JSON, CLI usage) keeps it above a 1.

2 / 5

Actionability

There are real executable commands ('python -m py_compile scripts/main.py', 'python scripts/main.py --help', '--input data.json --output biosketch.docx') and a complete JSON input example, but there are also concrete gaps: the 'Example Usage' path 'cd "20260318/scientific-skills/Academic Writing/nih-biosketch-builder"' is a non-portable literal, two different script path styles conflict ('scripts/main.py' vs 'skills/nih-biosketch-builder/scripts/main.py'), the PubMed import block contains an empty ```text fence, and 'Example Usage' says 'See ## Usage above' while the Usage section actually appears later in the document. These missing details place it at 'some concrete guidance but incomplete' rather than the mostly-executable level of 4.

3 / 5

Workflow Clarity

The 'Workflow' and 'Example Usage' sections list a sequence and there is one validation checkpoint ('python -m py_compile scripts/main.py' before deeper execution), but the steps are generic meta-process ('Confirm the user objective... Return a structured result...') rather than the actual generation flow, and no checkpoint validates the deliverable itself (page count <= 5, font >= 11pt, DOCX integrity). This matches 'steps listed but validation gaps; checkpoints missing or implicit', above the rough-sequence level of 2 because py_compile and input-confirmation steps do exist.

3 / 5

Progressive Disclosure

The bundle structure is real and one level deep: '[references/audit-reference.md](references/audit-reference.md)' is a clearly signaled, working link and 'scripts/main.py' exists and is referenced. However, audit-reference.md largely duplicates commands already in SKILL.md, risk assessment / security checklist / evaluation criteria content that belongs in a reference is inlined, and the duplicate '## References' sections impair navigation. This fits 'some structure but could be better organized' rather than the well-split level of 4.

3 / 5

Total

11

/

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 distinctive and names a concrete domain, but it is a single bare 'what' statement: the trailing phrase is grammatically truncated, there is no 'Use when...' trigger clause, and natural synonyms like 'grant application' or 'SciENcv' are absent. It is serviceable but below the quality of the reference good examples.

Suggestions

Add an explicit trigger clause, e.g. 'Use when preparing NIH grant applications, biosketches, or SciENcv-style CV documents.'

Complete the truncated phrase and mention the output format and PubMed import capability, e.g. 'Generate NIH Biosketch documents (DOCX) compliant with the 2022 OMB-approved format for NIH grant applications, including auto-import of publications via PMID.'

Include natural trigger terms users would actually say: 'NIH grant', 'grant application', 'biosketch', 'SciENcv', 'personal statement'.

DimensionReasoningScore

Specificity

"Generate NIH Biosketch documents" names the domain and one concrete action, matching the 'names domain and 1-2 concrete actions' anchor. The phrase "compliant with the 2022 OMB-approved" is truncated (missing a noun such as 'version' or 'format'), and capabilities the skill actually has (PubMed auto-import, DOCX output) are absent, so it is not comprehensive enough for a 4.

3 / 5

Completeness

The description clearly answers 'what' (generate NIH Biosketch documents) but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. The 'what' is clear, so it does not fall to the vague-what level of 2; the missing 'when' prevents a 4.

3 / 5

Trigger Term Quality

"NIH Biosketch" and "2022 OMB-approved" are relevant and reasonably natural keywords, but common variations users would say are missing: "grant application", "NIH grant", "SciENcv", "personal statement". This matches the 'some relevant keywords but missing common variations or synonyms' anchor, not the sparse single-keyword level of a 2.

3 / 5

Distinctiveness Conflict Risk

"NIH Biosketch" is a clear niche with distinct, domain-specific triggers; virtually no other skill category would be wrongly triggered by this phrasing. This matches the 'clear niche with distinct triggers; minimal conflict risk' anchor.

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/nih-biosketch-builder/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.