CtrlK
BlogDocsLog inGet started
Tessl Logo

date-calculator

Calculate medical date windows including gestational age, estimated delivery dates, and follow-up visit scheduling. Produces structured JSON output for clinical research and trial coordination workflows.

61

Quality

72%

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/Other/date-calculator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable and well-structured with clear workflow and validation guidance, but it carries an irrelevant copy-pasted note about survival-analysis statistics that hurts conciseness and could mislead.

Suggestions

Remove the 'Note on group parameter' paragraph about log-rank tests and Cox regression, which is unrelated to date calculation and appears to be copy-paste drift from another skill.

Either link references/guidelines.md from the body or remove the stub file so the reference structure is consistently signaled.

Add a brief validate->fix->retry loop to the Workflow so a failed run explicitly routes back to validation rather than only to the fallback path.

DimensionReasoningScore

Conciseness

Mostly efficient with a clear parameters table and command examples, but includes an irrelevant 'Note on group parameter' about log-rank tests and Cox regression that has nothing to do with a date calculator and is pure padding/drift.

3 / 5

Actionability

Provides copy-paste ready commands, a full parameter table, concrete usage examples, and concrete JSON output samples covering the common gestational and follow-up cases.

5 / 5

Workflow Clarity

A clear five-step sequence with a Quick Check validation block, explicit input validation rules, and a fallback template; not a 5 because there is no explicit validate-fix-retry loop, though date calculation is not destructive so the cap does not apply.

4 / 5

Progressive Disclosure

Well-organized sections with the executable script referenced by path throughout, but references/guidelines.md exists as a near-empty stub that is never signaled from the body, a minor navigation gap.

4 / 5

Total

16

/

20

Passed

Description

70%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 specific and well-targeted to a clinical research niche, but it omits any explicit 'when to use' trigger guidance, which caps its completeness score.

Suggestions

Add an explicit 'Use when...' clause naming the trigger phrases a user would naturally say (e.g., 'Use when computing gestational age from LMP, estimating delivery dates, or scheduling clinical-trial follow-up windows').

Include common synonyms/shorthand (e.g., 'LMP', 'EDD', 'due date', 'visit windows') to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('gestational age, estimated delivery dates, and follow-up visit scheduling' plus 'structured JSON output'), but stops short of the comprehensive action list needed for a 5.

4 / 5

Completeness

Clearly answers 'what' the skill does, but provides no explicit 'Use when...' trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural domain terms users would say ('gestational age', 'estimated delivery dates', 'follow-up visit scheduling'), but misses common synonyms and shorthand variations a clinician might use.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (medical date windows for clinical research/trial coordination) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

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.

Validation15 / 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
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.