Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rshankras/permission-priming
Generates pre-permission priming screens that explain benefits before showing iOS system permission dialogs.
Passed 16 of 22 test cases with the skill, and 16 of 22 without it.
2 fixed14 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
If an iOS project follows a standard layout with a top-level Sources directory, where should the generated permission framework files be placed?
| Checked | Without skill | With skill |
|---|---|---|
| Places files inside Sources/Permissions/ | Missed | Passed |
The instructions your model reads when the skill loads.
Generate pre-permission priming screens — shown before iOS system permission dialogs to explain WHY the app needs access. Dramatically increases permission grant rates vs. cold-prompting users with the system alert.
Use this skill when the user:
Search for existing permission handling:
Glob: **/*Permission*.swift, **/*Authorization*.swift
Grep: "requestAuthorization" or "AVCaptureDevice" or "UNUserNotificationCenter" or "CLLocationManager" or "PHPhotoLibrary"
If existing permission code found:
Search for required usage description keys:
Grep: "NSCameraUsageDescription" or "NSMicrophoneUsageDescription" or "NSLocationWhenInUseUsageDescription" or "NSPhotoLibraryUsageDescription" or "NSContactsUsageDescription" or "NSHealthShareUsageDescription"
If missing keys found for requested permissions:
test cases passed, vs 16 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.