CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

equipment-maintenance-log

Track lab equipment calibration dates and send maintenance reminders for pipettes, balances, centrifuges, and other instruments. Validates date formats and supports update/delete operations.

Quality

74%

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/equipment-maintenance-log/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 is highly actionable — executable commands, a full parameter table, exact error messages, and a report format that matches the bundled script — but the body is padded with generic governance boilerplate and redundant restatements that waste context. Trimming those sections would make an otherwise strong reference lean and focused.

Suggestions

Delete the generic boilerplate sections ("Stress-Case Rules", "Output Requirements", "Response Template", and the abstract "Workflow") or replace the Workflow with the actual operational sequence: quick check → run command → handle documented errors.

State date validation once (e.g. in Error Handling) and remove the duplicated Quick Check line from "Audit-Ready Commands".

Consider moving the full compliance-report JSON schema into a references/ file and keeping only a short example inline.

DimensionReasoningScore

Conciseness

Several padded sections add no skill-specific value: "Stress-Case Rules", "Output Requirements", the generic "Response Template", and an abstract "Workflow" ("Confirm the user objective, required inputs, and non-negotiable constraints"). Date validation is stated three times (Parameters note, Input Validation, Error Handling) and the "Quick Check" command is duplicated verbatim inside "Audit-Ready Commands". This matches anchor 2 (noticeably verbose, several padded sections) rather than 3, whose "some unnecessary explanation" understates the volume of boilerplate; it is not 1 because the core reference material (Parameters, Usage, Output, report format) is efficient.

2 / 5

Actionability

Every operation has a copy-paste-ready command with realistic arguments (e.g. `python scripts/main.py --add "Pipette P100" --calibration-date 2024-01-15 --interval 12`), a complete parameter table, exact error messages, and a concrete JSON report schema that matches the bundled script's actual arguments (verified against scripts/main.py). Anchor 5 fits; specific examples cover all the common cases.

5 / 5

Workflow Clarity

The operational path is clear with most checkpoints present: a Quick Check (`python -m py_compile scripts/main.py`), input-time date validation, and explicit error recovery ("report 'Equipment not found' and list available names", fallback path on script failure). The destructive --delete operation has documented validation, so no cap applies. Not 5 because the "Workflow" section is generic boilerplate rather than the concrete validate→fix→retry sequence for the actual commands; not 3 because real checkpoints are explicit and complete.

4 / 5

Progressive Disclosure

The bundle is a single script referenced by its correct path (`scripts/main.py`) and documented in Parameters and Usage, with no nesting and no buried references. Content is appropriately inline for a skill this size, with clear section headers. Anchor 4 rather than 5 because the boilerplate sections dilute the otherwise clean organization and some reference material (e.g. the full report schema) could live in a separate file.

4 / 5

Total

15

/

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.

A specific, third-person description with concrete actions and natural trigger terms for a well-defined lab-equipment niche. Its main weakness is the absence of an explicit "Use when..." clause, and it undersells the list/report capabilities the skill actually provides.

Suggestions

Add an explicit trigger clause, e.g. "Use when tracking lab equipment calibration schedules, checking for overdue maintenance, or preparing compliance reports."

Mention the listing and JSON compliance-report generation operations so the description's coverage matches the skill's full capability set.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Track lab equipment calibration dates", "send maintenance reminders", "Validates date formats", "supports update/delete operations" — plus named instruments (pipettes, balances, centrifuges). It sits at anchor 4 rather than 5 because the body documents list and compliance-report operations that the description omits, a minor coverage gap.

4 / 5

Completeness

The "what" is clearly answered (track calibration dates, send reminders, validate dates, update/delete), but there is no "Use when..." clause or equivalent explicit trigger guidance; the rubric explicitly caps completeness at 3 in that case. It is not 2 because the "what" is concrete and specific rather than vague.

3 / 5

Trigger Term Quality

Natural keywords users would say are present: "calibration", "maintenance reminders", "lab equipment", and specific instrument names. Not 5 because common synonyms such as "instrument servicing" or "calibration schedule" are missing, keeping coverage good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — lab instrument calibration tracking for pipettes, balances, centrifuges — with distinct triggers and minimal overlap risk with other skills. Anchor 5 fits; anchor 4's "minor overlap risk" understates how specific the lab-equipment domain is.

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.

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/equipment-maintenance-log/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.