adifcheck@0.1.0
VERIFIED· install onlyPublisher claims: "Check a ham-radio ADIF log's contents — the values LoTW and eQSL actually reject — before upload. Use when asked to validate an .adi or .adx log, find why QSOs were rejected by LoTW or eQSL, or check a log before uploading — for example "check my log before I upload to LoTW", "why did eQSL reject these QSOs", or "validate this ADIF file". Checks modes, submodes and their pairings, band versus frequency, dates and times, satellite fields and state/county codes against the ADIF 3.1.8 specification's own tables, plus the documented LoTW and eQSL acceptance rules. Not for Darwin Core / GBIF occurrence files (that is dwccheck) or iCalendar (.ics) files (that is icslint)." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-20 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
No findings across 106 lines in 2 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.