Skip to content
Back to skills

Apple Hig Id Verifier

ASecurity

Use when designing or reviewing in-person iPhone mobile-ID verification, age-threshold requests, Display Only versus Data Transfer, or verifier outcomes.

  • 7 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 26, 2026
ai-agentsgo

Security analysis

A100/100

Scanned October 26, 2026

npx -y skills add AyushRajSinghParihar/apple-human-interface-skills --skill apple-hig-id-verifier --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Apple Hig Id Verifier?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Apple Hig Id Verifier
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ayushrajsinghparihar-apple-hig-id-verifier/badge)](https://www.skillsdirectory.com/skills/ayushrajsinghparihar-apple-hig-id-verifier)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: apple-hig-id-verifier
description: Use when designing or reviewing in-person iPhone mobile-ID verification, age-threshold requests, Display Only versus Data Transfer, or verifier outcomes.
---

# Verify only the identity fact the task requires

Read [ID Verifier](../../references/id-verifier.md). Inspect the in-person verification purpose, necessary attributes, storage/processing need, requester role, and requested design/review/adaptation. This source describes iOS 17+ iPhone reading of compatible mobile IDs; other platforms are excluded. Preserve the existing stack and verify current entitlement/eligibility requirements before implementation.

Choose the minimum fact that answers the task. If an age threshold is enough, request that result rather than date of birth or current age. Distinguish Display Only, where data/photo appear solely in system UI for visual checking, from Data Transfer, which requires a legal verification need to store/process information and an additional entitlement. Do not design app-side processing around information it never receives.

Start verification through a clear age/identity action rather than NFC/QR-specific artwork or an Apple logo. For eligible organizations, show the verified business identity supplied through appropriate registration. In Display Only, provide the requester a clear outcome action for the visual decision, such as portrait match/nonmatch; keep that human observation separate from any claimed automated identity verdict.

**Before → decision → after:** A venue requests a full birth date, labels the action with an NFC glyph, and assumes Display Only returns the portrait to app storage. Decision: entry needs only an age-threshold result and a visual match. After, “Verify age” launches the appropriate minimal system request, the operator records the supported match/nonmatch outcome, and no nonexistent photo-transfer path is promised.

Deliver a purpose-to-attribute/request-mode/outcome contract and corrected flow or implementation. Fail if unnecessary personal details are requested, Display Only data is treated as app-owned, or the action hides its identity-verification purpose. Static review cannot verify certificates, entitlement issuance, actual ID interoperability, or legal necessity; identify those evidence boundaries explicitly.

Use [Privacy](../../../apple-hig-foundations/.topics/apple-hig-privacy/SKILL.md) for minimization and [NFC](../apple-hig-nfc/SKILL.md) only for a separate tag-reading task, not as a substitute verification model.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.