From nfc-ops
Use when you need to diagnose a tag's hardware properties, lock state, memory layout, and capacity — before attempting a write or to troubleshoot a failed operation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nfc-ops:inspect-tagThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Deep inspection of an NFC tag's hardware properties, memory layout, lock state, and capacity. Useful for diagnosing why writes fail or whether a tag is locked/read-only.
Deep inspection of an NFC tag's hardware properties, memory layout, lock state, and capacity. Useful for diagnosing why writes fail or whether a tag is locked/read-only.
nfc-list is available.nfc-list to detect the tag. Capture UID and initial type classification. Fail if no tag is detected.nfc-mfultralight info or equivalent to read:
nfc-mfclassic info or mfoc -O dump.bin to read:
mfoc can brute-force known keys).mfoc to brute-force MIFARE Classic keys, inform the user that this may take 30–60 seconds. Only attempt if the user explicitly asks or if a write failed due to authentication.password-protect if the user owns the tag.npx claudepluginhub danielrosehill/claude-code-plugins --plugin nfc-opsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.