CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

65%

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

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 content has a solid skeleton — executable usage examples, a parameter table, concrete output schemas, and explicit input-validation and scope-refusal rules. Its credibility is undermined by documentation-script mismatches (--timezone, warning field, weeks validation), an off-topic survival-analysis note, generic workflow boilerplate, and an orphaned references/guidelines.md that is never linked. Tightening the doc to match the actual script and adding a 'See references/guidelines.md' pointer would resolve the main issues.

Suggestions

Remove the irrelevant 'Note on group parameter' about log-rank tests and Cox regression — it belongs to a survival-analysis skill, not date calculation.

Reconcile documentation with scripts/main.py: either implement --timezone, the future-LMP warning field, and the --weeks ≥ 1 validation, or remove those claims from the Parameters and Validation sections.

Link the existing references/guidelines.md from the body (e.g., a 'Clinical standards: See references/guidelines.md' line) so the reference file is discoverable, and replace the generic 'Workflow' boilerplate with the concrete command sequence.

DimensionReasoningScore

Conciseness

The body is largely efficient with a parameter table, terse usage commands, and compact JSON examples, but it carries real padding: the entirely irrelevant '**Note on group parameter:** ... log-rank test and Cox regression' note (survival-analysis content that has nothing to do with date calculation), and overlapping generic boilerplate in 'Workflow', 'Output Requirements', and 'Response Template' that repeats the same deliverables/assumptions/risks structure three times. This matches the 3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened') — not the 4 anchor, whose over-explanation is only 'minor instances'.

3 / 5

Actionability

Usage commands are copy-paste executable and the parameter table and JSON output examples are concrete, but the documentation does not match the actual bundle script: '--timezone' is documented yet absent from scripts/main.py, and the promised 'warning' field for future LMP dates and '--weeks must be ≥ 1' rejection are not implemented. Documented parameters that fail when used are a substantive gap beyond the 4 anchor's 'minor gaps', placing this at 3 ('some concrete guidance but incomplete ... missing key details').

3 / 5

Workflow Clarity

A usable sequence exists implicitly (Quick Check -> validate inputs -> Usage -> Error Handling -> Fallback template), but the explicit 'Workflow' section is generic procedural boilerplate ('Confirm the user objective...', 'Use the packaged script path or the documented reasoning path') with no concrete commands, and validation checkpoints are scattered rather than sequenced. This matches the 3 anchor ('steps listed but validation gaps; sequence present but checkpoints missing or implicit'); it is not a destructive/batch operation, so the cap-3 rule is not what limits it.

3 / 5

Progressive Disclosure

The body is well-sectioned at a reasonable length and its script reference (scripts/main.py) points to a real file, but the bundle's references/guidelines.md is never mentioned or linked anywhere in the body — a reference file that exists but is not clearly signaled. Per the guideline to score against the actual bundle structure, this lands on the 3 anchor ('references present but not clearly signaled') rather than the 4 anchor's 'references mostly clear'.

3 / 5

Total

12

/

20

Passed

Description

66%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, domain-scoped, and names its output format, with good natural trigger terms for the clinical research context. Its main weakness is the absence of any explicit 'Use when...' trigger clause, which both caps completeness and weakens its invocation guidance. Adding a trigger clause with common synonyms (LMP, due date, visit window) would raise it to the top tier.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user mentions gestational age, LMP, due dates, EDD, or scheduling follow-up visit windows for clinical trials.'

Include common synonyms users would actually say — 'due date', 'LMP', 'pregnancy dating', 'visit window' — to broaden trigger-term coverage.

Mention the calculation types and configurable window sizes to make the capability list more comprehensive.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Calculate medical date windows including gestational age, estimated delivery dates, and follow-up visit scheduling' plus a concrete output format ('Produces structured JSON output') — but stops short of the comprehensive, exhaustive action list of the 5 anchor (e.g., no mention of visit-window generation or date validation). It is clearly above the 3 anchor, which covers only 1-2 concrete actions, so 4 fits best.

4 / 5

Completeness

The 'what' is clearly and specifically stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance — the only situational hint ('for clinical research and trial coordination workflows') describes the audience, not when to invoke the skill. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3, matching the anchor 'Has a clear what but when is missing or only weakly implied'.

3 / 5

Trigger Term Quality

Natural phrases like 'gestational age', 'estimated delivery dates', 'follow-up visit scheduling', 'clinical research', and 'trial coordination' are terms users would plausibly say. However, common synonyms such as 'due date', 'LMP', 'EDD', 'pregnancy dating', and file-format terms are missing, which matches the 4 anchor ('good keyword coverage; a few natural terms missing') rather than the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The clinical/obstetric niche ('gestational age', 'estimated delivery dates', 'clinical research and trial coordination') is mostly distinct from generic date or calendar utilities, with only minor overlap risk with general scheduling/date-math skills. It lacks the razor-sharp 'use when' triggers of the 5 anchor, so 4 ('mostly distinct; minor overlap risk') is the best fit.

4 / 5

Total

15

/

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/Other/date-calculator/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.