Arkit Visionos Developer

v0.1.0

Build and debug ARKit features for visionOS, including ARKitSession setup, authorization, data providers (world tracking, plane detection, scene reconstructi...

0· 81·0 current·0 all-time
byTom Krikorian@tomkrikorian
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description match the contents: provider-specific guidance, ARKitSession lifecycle, authorization, anchor handling, and RealityKit bridging. Nothing requested (no env vars, binaries, or installs) is out of scope for an authoring/debugging guide.
Instruction Scope
SKILL.md and the reference files contain only implementation guidance and local code examples. Instructions reference adding Info.plist keys and requesting runtime authorizations (expected for camera/hand/world sensing). There are no instructions to read unrelated system files, exfiltrate data, or contact external endpoints.
Install Mechanism
No install spec and no code files to execute — instruction-only skill; therefore no installation risk or downloads are present.
Credentials
The skill declares no required environment variables, credentials, or config paths. The runtime advice to request user authorizations for camera/hand/world sensing is appropriate and proportional to the ARKit functionality described.
Persistence & Privilege
always:false (default) and no install actions writing persistent configuration. The skill does not request persistent or system-wide privileges.
Assessment
This skill is documentation and example code for ARKit on visionOS and appears internally consistent. Consider the following before using it in a project: 1) The examples request runtime camera/hand/world-sensing authorizations — ensure you present clear privacy notices (Info.plist keys) and handle denied states. 2) Some providers require entitlements or enterprise licensing (noted in the docs); verify you have those before enabling them. 3) Because this is instruction-only, no code will be executed by installing the skill, but when copying examples into your app audit any added networking or persistence you introduce and avoid sending raw sensor frames or sensitive anchors off-device unless you have explicit consent and secure transport. 4) If you need higher assurance, review the examples in your development environment and test permission flows on-device.

Like a lobster shell, security has layers — review code before you run it.

latestvk97cxm3ysgz1ntdg372q2jjbd98374h2

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments