NFC Tools
v1.0.0NFC tag discovery, inspection, and cautious write workflows using libnfc/nfc-utils; trigger when the user asks to read tags, inspect NDEF payloads, write or...
⭐ 0· 195·0 current·0 all-time
bypp@ppopen
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (NFC discovery, inspection, cautious write workflows) match the files and runtime instructions. The skill expects libnfc/nfc-utils CLI tools and an NFC reader, which is appropriate for the stated purpose.
Instruction Scope
SKILL.md gives explicit, scoped runtime steps (discovery, read, write, erase) and enforces explicit textual confirmations before destructive actions. It references supplying key files or a default key bundle and the LIBNFC_DEVICE env var when multiple readers exist — both are reasonable for NFC workflows but mean the agent may ask for or reference local key files or device identifiers during operations.
Install Mechanism
No install spec (instruction-only) and only a small sanity-check script are included; there are no downloads or archive extracts. Installation instructions in README are standard OS package commands for libnfc and udev rules, which are expected.
Credentials
The skill declares no required env vars or credentials. It mentions using LIBNFC_DEVICE as an optional device selector and references key files/default key bundles for MIFARE Classic operations; this is proportional but users should be aware the workflow may touch local key files (and may require elevated privileges for udev/rules installation).
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent presence or system-wide configuration changes. The skill does provide guidance to modify system udev rules during manual installation, which is normal for hardware support.
Assessment
This skill is coherent with its NFC purpose and is instruction-only (low install risk). Before installing/using it: ensure you have trusted libnfc/nfc-utils installed and a supported reader; be prepared to grant or create udev rules (requires sudo) for device access; note that MIFARE Classic workflows may reference or require key files (inspect any key files you supply); the agent may ask you to unmask full UIDs for debugging — only reveal them when necessary. Review the README and SKILL.md so you understand the explicit confirmation gates (CONFIRM NFC WRITE / CONFIRM NFC FORMAT) that prevent accidental destructive writes.Like a lobster shell, security has layers — review code before you run it.
latestvk97d356r00g6mt6dcfhw1ftc7n82nb0t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
