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.
Install / Use
npx skills add aipoch/medical-research-skills --skill equipment-maintenance-logInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Customer SupportSupported Platforms
Our assessment of equipment-maintenance-log
equipment-maintenance-log scores 89/100 on our quality scale, 166th of 319 Customer Support skills we index.
Its SKILL.md is 5.6 KB long, well organised into 21 sections with 4 code examples: a solid amount of guidance for an agent.
With 1,916 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so equipment-maintenance-log is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
equipment-maintenance-log compared with similar skills
All 4 of these similar skills score higher than equipment-maintenance-log; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| equipment-maintenance-log (this skill)by aipoch | 89 | 1.9k | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
| crawl4aiby unclecode | 100 | 87.4k | 3d ago | MCP Server |
Frequently asked questions
- How do I install equipment-maintenance-log?
- Run
npx skills add aipoch/medical-research-skills --skill equipment-maintenance-log. The install tabs above show the steps for each supported agent. - Which AI agents does equipment-maintenance-log work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is equipment-maintenance-log safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is equipment-maintenance-log still maintained?
- The repository was last updated about 2 months ago, so equipment-maintenance-log is actively maintained.
Skill content
View source on GitHubname: equipment-maintenance-log description: Track lab equipment calibration dates and send maintenance reminders for pipettes, balances, centrifuges, and other instruments. Validates date formats and supports update/delete operations. license: MIT author: AIPOCH
Equipment Maintenance Log
Track calibration dates for pipettes, balances, centrifuges and send maintenance reminders.
Quick Check
python -m py_compile scripts/main.py
Audit-Ready Commands
python -m py_compile scripts/main.py
python scripts/main.py --help
python scripts/main.py --add "Pipette P100" --calibration-date 2024-01-15 --interval 12
When to Use
- Track lab equipment calibration schedules
- Check for overdue or upcoming maintenance
- Generate maintenance reminder reports
- Maintain compliance records for audits
Workflow
- Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work.
- Validate that the request matches the documented scope and stop early if the task would require unsupported assumptions.
- Use the packaged script path or the documented reasoning path with only the inputs that are actually available.
- Return a structured result that separates assumptions, deliverables, risks, and unresolved items.
- If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion.
Parameters
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| --add | string | * | Equipment name to add |
| --calibration-date | string | * | Last calibration date (YYYY-MM-DD format required) |
| --interval | int | * | Calibration interval in months |
| --location | string | No | Equipment location |
| --update | string | ** | Equipment name to update calibration date |
| --delete | string | ** | Equipment name to remove from log |
| --check | flag | ** | Check for upcoming maintenance |
| --list | flag | ** | List all equipment |
| --report | flag | ** | Generate compliance report (JSON) |
* Required when adding or updating equipment ** Alternative operations (mutually exclusive with --add)
Date validation:
--calibration-datemust be in YYYY-MM-DD format. Invalid dates (e.g., 2024-13-45) are rejected at input time with a clear error message. The script validates the date before storing it.
Usage
# Add equipment
python scripts/main.py --add "Pipette P100" --calibration-date 2024-01-15 --interval 12
# Add with location
python scripts/main.py --add "Balance XS205" --calibration-date 2024-03-01 --interval 6 --location "Lab 3B"
# Check maintenance status
python scripts/main.py --check
# List all equipment
python scripts/main.py --list
# Update calibration date after servicing
python scripts/main.py --update "Pipette P100" --calibration-date 2025-01-15
# Remove decommissioned equipment
python scripts/main.py --delete "Balance XS205"
# Generate compliance report
python scripts/main.py --report
Output
- Maintenance schedule with next due dates
- Overdue alerts (past calibration date)
- Upcoming reminders (30/60/90 days)
- Compliance report (JSON) with equipment name, location, last calibration date, interval, next due date, and status
Compliance Report Format
{
"generated": "2025-01-15",
"equipment": [
{
"name": "Pipette P100",
"location": "Lab 3B",
"last_calibration": "2024-01-15",
"interval_months": 12,
"next_due": "2025-01-15",
"status": "DUE"
}
],
"summary": {
"total": 1,
"overdue": 0,
"due_30_days": 1,
"compliant": 0
}
}
Stress-Case Rules
For complex multi-constraint requests, always include these blocks:
- Assumptions
- Hard Constraints
- Maintenance Check Path
- Compliance Risks
- Unresolved Items
Input Validation
This skill accepts requests involving lab equipment calibration tracking, maintenance scheduling, and reminder generation.
If the user's request does not involve equipment maintenance logging — for example, asking to order supplies, write SOPs, or manage personnel schedules — do not proceed with the workflow. Instead respond:
"equipment-maintenance-log is designed to track lab equipment calibration dates and maintenance schedules. Your request appears to be outside this scope. Please provide equipment name and calibration details, or use a more appropriate tool for your task."
Output Requirements
Every final response must include:
- Objective or requested deliverable
- Inputs used and assumptions introduced
- Workflow or decision path
- Core result, recommendation, or artifact
- Constraints, risks, caveats, or validation needs
- Unresolved items and next-step checks
Error Handling
- If
--addis used without--calibration-dateor--interval, report exactly which fields are missing before proceeding. - If
--calibration-dateis not in YYYY-MM-DD format, reject with: "Invalid date format. Use YYYY-MM-DD (e.g., 2024-01-15)." - If
--updateor--deletereferences an equipment name not in the log, report "Equipment not found" and list available names. - If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.
- If
scripts/main.pyfails, report the failure point, summarize what still can be completed safely, and provide a manual fallback. - Do not fabricate files, citations, data, search results, or execution outcomes.
Response Template
- Objective
- Inputs Received
- Assumptions
- Workflow
- Deliverable
- Risks and Limits
- Next Checks
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
crawl4ai
87.4kOfficial Crawl4AI Cloud: a hosted web scraping, extraction, and search API for AI agents. Free API key, 1,000 credits a month, no card. Fully open source: this repo is the Apache-2.0 crawler that powers it, and you can self-host it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
