CtrlK
BlogDocsLog inGet started
Tessl Logo

cold-chain-risk-calculator

Calculate temperature excursion risks for cold chain transport. Assesses route risk, packaging suitability, and monitoring requirements for biological samples and pharmaceuticals requiring controlled-temperature shipping.

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/cold-chain-risk-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 with executable examples and a clear, validated workflow, supported by a real script bundle. Its main weakness is redundancy across the Output Requirements, Response Template, and Features sections that could be consolidated for token efficiency.

Suggestions

Merge the Output Requirements, Response Template, and Workflow step 4 into a single response-structure section to remove redundancy.

Trim or remove the Features list, which restates information already in Output Format and Risk Model.

Move the detailed Error Handling and Input Validation tables into a short reference or keep only the non-obvious cases inline.

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept padding, but the Output Requirements, Response Template, and Workflow step 4 overlap heavily on the same response structure, and the Features section restates the Output Format and Risk Model — content that could be tightened.

3 / 5

Actionability

Fully executable guidance: copy-paste Quick Check commands, concrete Usage examples, a real documented Parameters table, and a complete JSON output sample covering common cases.

5 / 5

Workflow Clarity

A clear 5-step sequence with explicit validation (stop early on out-of-scope, fallback path) and an error-handling section; it is not a 5 because the workflow steps are process guidance rather than concrete operational checkpoints tied to the script.

4 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled, one-level-deep reference to the real scripts/main.py bundle (verified to exist); it is not a 5 because most reference material is inlined in SKILL.md rather than split into separate reference files.

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 clearly distinguishes the skill's niche, but it lacks an explicit 'Use when...' trigger clause, which caps completeness at 3. Adding a concrete trigger sentence would lift the completeness and trigger-term dimensions.

Suggestions

Append an explicit trigger clause such as 'Use when assessing shipping risk for temperature-sensitive biological samples, vaccines, or pharmaceuticals, or when selecting cold-chain packaging.'

Add natural synonyms a user might say (e.g., 'vaccines', 'cold-chain shipping', 'temperature-controlled logistics') to broaden trigger coverage.

Specify what 'monitoring requirements' means concretely to close the specificity gap toward a 5.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'Calculate temperature excursion risks', 'Assesses route risk, packaging suitability, and monitoring requirements' — but monitoring requirements are stated without detail, leaving minor coverage gaps rather than full comprehensiveness.

4 / 5

Completeness

The 'what' is clearly stated (calculate/assess risk, packaging, monitoring), but there is no explicit 'Use when...' trigger clause, and per the rubric a missing trigger clause caps completeness at 3 even though the audience ('biological samples and pharmaceuticals') weakly implies the 'when'.

3 / 5

Trigger Term Quality

Good coverage of natural domain terms users would say ('cold chain transport', 'biological samples', 'pharmaceuticals', 'controlled-temperature shipping'), though it lacks common synonyms or file-extension-style triggers a user might also use.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (cold chain temperature excursion risk) with distinct triggers unlikely to fire for unrelated skills, giving minimal conflict risk.

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.