CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

69%

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

60%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.

A well-organized, instruction-rich skill body with a clear workflow and honest model-limitations disclosure, but its documented interface substantially mismatches the bundled script (missing --output flag, plain-text output instead of documented JSON, wrong liquid-nitrogen factor and risk thresholds, absent duration validation), and its response-obligation sections repeat themselves. Fixing the doc/script mismatches would make the otherwise excellent guidance genuinely executable.

Suggestions

Reconcile SKILL.md with scripts/main.py: either implement the documented --output flag, JSON output, mitigation_recommendations, packaging factors (liquid-nitrogen 0.6 vs 0.3), risk thresholds (<15/15–30/>30 vs <10/<20/≥20), and negative-duration exit-code-1 validation, or correct the docs to match the script.

Merge the overlapping 'Output Requirements', 'Response Template', and the output-related 'Workflow' items into one section — currently the same structured-response obligations are stated three times.

Move the mitigation-recommendation tables, response template, and scope-refusal text into a references/ file (e.g. MITIGATION.md) and keep SKILL.md as a lean overview with clearly signaled one-level-deep links.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and provides lean tables and code blocks, but it carries notable redundancy: 'Output Requirements', the 'Workflow' output step, the 'Response Template', and parts of 'Error Handling' and 'Model limitations' restate the same structured-response obligations two to three times. It is more efficient than the verbose anchor (2) but clearly could be tightened, fitting the 'mostly efficient but some unnecessary explanation' anchor.

3 / 5

Actionability

Guidance is concrete (parameter table, usage commands, exact JSON output, risk formula), but execution against the bundled scripts/main.py reveals it is incomplete/incorrect: the documented '--output' flag does not exist (the second usage example errors with 'unrecognized arguments'), the script prints plain text rather than the documented JSON (no risk_level string, no mitigation_recommendations field), liquid-nitrogen's factor is 0.3 in code vs 0.6 documented, risk thresholds are <10/<20/≥20 vs documented <15/15–30/>30, and '--duration -5' is accepted and returns 'Low risk' despite the documented exit-code-1 validation. This places it at 'some concrete guidance but incomplete/missing key details' rather than a 4.

3 / 5

Workflow Clarity

The Workflow section gives a clear five-step sequence with early input confirmation, explicit scope validation ('stop early if the task would require unsupported assumptions'), a fallback template, and an Error Handling section with exact failure messages and exit codes — most checkpoints are present. It falls short of 5 because checkpoints like the Quick Check are listed but not tied into the workflow steps, and error-recovery loops (e.g. re-run after fixing inputs) are only implicit.

4 / 5

Progressive Disclosure

Structure is good: a single real bundle file (scripts/main.py) referenced consistently by correct path, well-labeled sections (Parameters, Usage, Output Format, Risk Model, Error Handling), and no nesting or buried references. It is below 5 because the ~127-line body keeps everything inline — the mitigation-recommendation logic, response templates, and scope-refusal text are candidates for a references/ file that would keep the main file a lean overview.

4 / 5

Total

14

/

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.

A specific, well-scoped description in a clear niche with good natural trigger vocabulary, but it omits any explicit 'when to use' guidance, which caps its completeness and weakens its usefulness for automatic skill triggering.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when evaluating shipping risk for vaccines, biological samples, or temperature-sensitive pharmaceuticals, or when selecting dry-ice/liquid-nitrogen/gel-pack packaging.'

Include more user-natural synonyms and concrete terms such as 'vaccine shipping', 'frozen or refrigerated samples', 'dry ice', and 'shipping risk assessment' to broaden trigger coverage.

Tighten 'assesses... monitoring requirements' into concrete deliverables (e.g. 'produces a risk score and mitigation recommendations') so every stated capability maps to what the skill actually outputs.

DimensionReasoningScore

Specificity

Names a concrete domain (cold chain transport) with several specific actions — 'Calculate temperature excursion risks', 'Assesses route risk, packaging suitability, and monitoring requirements' — leaving only minor gaps in coverage. It is below a 5 because the actions are stated at a moderate level of abstraction and some declared capabilities (monitoring requirements) are not matched by equally concrete phrasing elsewhere.

4 / 5

Completeness

The 'what' is clearly answered (calculate temperature excursion risks, assess route/packaging/monitoring), but there is no 'Use when...' clause or equivalent explicit trigger guidance — only the implicit context 'for biological samples and pharmaceuticals requiring controlled-temperature shipping'. Per the rubric guideline, a missing explicit 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural-keyword coverage: 'temperature excursion', 'cold chain', 'route risk', 'packaging', 'biological samples', 'pharmaceuticals', 'controlled-temperature shipping' are phrases users would plausibly say. It falls short of 5 because common variations users might use — e.g. 'vaccine shipping', 'dry ice', 'frozen samples', 'shipping risk' — are absent.

4 / 5

Distinctiveness Conflict Risk

The cold-chain/temperature-excursion niche is specific and would rarely collide with unrelated skills, so it is well above a 3. It does not reach 5 because the description lacks distinct trigger phrases and could mildly overlap with generic logistics, shipping, or lab-sample-handling skills.

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/cold-chain-risk-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.