v0.1.0

Arkit Visionos Developer

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 7:44 AM.

Analysis

This instruction-only skill gives coherent ARKit visionOS development guidance, with privacy-sensitive sensor permissions disclosed as part of the stated purpose.

GuidanceThis looks reasonable to install as ARKit development guidance. Before applying its examples, review any generated app code that requests camera, hand-tracking, world-sensing, room, scene reconstruction, or shared spatial data access, and keep those permissions limited to the feature’s real needs.

Findings (1)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityLowConfidenceHighStatusNote

SKILL.md

Add `NSWorldSensingUsageDescription`, `NSHandsTrackingUsageDescription`, and `NSMainCameraUsageDescription` to `Info.plist` as needed... Request authorization for provider-required data types before running the session.

The skill guides developers to request app-level permissions for ARKit sensor access, including world sensing, hand tracking, and camera access. This is expected for ARKit development and is clearly disclosed, but it is privacy-sensitive authority.

User impactIf you use the generated code, your app may ask users for access to camera, hand-tracking, and spatial-environment data.

RecommendationOnly enable the ARKit providers your feature actually needs, write clear permission prompts, handle denied permissions gracefully, and review generated code before shipping.