Agent skill
auditing-permission-ux
Audits notification permission request flows. Use when reviewing or improving permission prompts, settings paths, or denial handling.
Install this agent skill to your Project
npx add-skill https://github.com/clix-so/skills/tree/main/skills/auditing-permission-ux
SKILL.md
Auditing Permission UX
Use this skill to audit how a mobile app requests notification permission and guides users to settings, then produce actionable improvements based on Apple and Android best practices.
What this skill does
- Reviews permission timing, context, and explanation quality
- Checks denial handling and settings recovery paths
- Flags platform-specific risks (iOS vs Android)
- Produces a structured audit report with fixes
Workflow
Permission UX audit progress:
- [ ] 1) Confirm minimum inputs (platforms, flow, current UX)
- [ ] 2) Audit current flow (map prompts, copy, and settings paths)
- [ ] 3) Produce audit report (findings + fixes)
- [ ] 4) Verify improvements (ensure UX changes align with platform rules)
1) Confirm the minimum inputs
Ask only what is needed:
- Platforms: iOS, Android, or both
- Entry points: where the app asks for permission
- Prompt timing: first launch, after action, onboarding step, etc.
- Primer: is there an in-app explanation before the system prompt
- Settings path: how users enable later after denial
- Denial handling: how the app behaves if permission is denied
2) Audit the current flow
Document the current permission flow directly from the app:
- Where the permission prompt appears and what precedes it
- What copy is shown to explain value
- How the app behaves after deny or dismiss
- How users can enable notifications later
3) Produce the audit report
Output a concise report in markdown with:
- Findings: each gap mapped to best practice
- Risk: what the user impact is
- Fix: concrete UX change
- Platform notes: iOS-only or Android-only specifics
Optional: generate a report template:
bash skills/auditing-permission-ux/scripts/generate-permission-ux-audit-report.sh .mobile/permission-ux-audit.md
4) Verify improvements
Confirm:
- Prompt timing is contextual (not forced on first launch)
- Primer explains value clearly and is dismissible
- Denied users can still use the app
- Settings path is discoverable and clear
- Android importance/channel strategy is not misleading
Progressive Disclosure
- Level 1: This
SKILL.md - Level 2:
references/ - Level 3:
examples/(optional) - Level 4:
scripts/(execute; do not load)
References
references/permission-ux-best-practices.md
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
clix-integration
Integrates Clix Mobile SDK into iOS, Android, Flutter, and React Native projects. Provides step-by-step guidance for installation, initialization, and verification. Use when the user asks to install, setup, integrate Clix or when the user types `clix-integration` / "clix integration".
clix-user-management
Implements Clix user identification and user properties (setUserId, removeUserId, setUserProperty/setUserProperties, removeUserProperty/removeUserProperties) with safe schemas, logout best practices, and campaign-ready personalization/audience usage. Use when the user mentions login/logout, userId, user properties, personalization, audience targeting or when the user types `clix-user-management`.
push-notification-designer
Design and implement local push notification campaigns to boost user engagement in mobile apps. Use this skill whenever the user mentions local push notifications, in-app notifications, user engagement campaigns, retention messaging, re-engagement nudges, or wants to add scheduled notifications to their app. Also trigger when the user asks about notification timing strategies, onboarding notification flows, or workout/habit/goal reminder systems. Covers iOS (Swift/UNUserNotificationCenter), Android (Kotlin/WorkManager+NotificationManager), Flutter (flutter_local_notifications), and React Native (notifee/expo-notifications).
clix-api-triggered-campaigns
Helps developers configure API-triggered campaigns in the Clix console and trigger them from backend services with safe auth, payload schemas, dynamic audience filters (trigger.*), and personalization best practices. Use when the user mentions transactional notifications, backend-triggered sends, campaign_id trigger APIs, or "API-triggered campaigns".
push-notification-best-practices
Comprehensive mobile push notification guide for iOS (APNS) and Android (FCM). Use when setting up push notifications, debugging delivery issues, implementing background/foreground handlers, managing push tokens, integrating deep linking, or troubleshooting platform-specific issues.
clix-event-tracking
Implements Clix event tracking (Clix.trackEvent) with consistent naming, safe property schemas, and campaign-ready validation. Use when adding, reviewing, or debugging event tracking; when configuring event-triggered campaigns; or when the user mentions events, tracking, funnels, or properties — or when the user types `clix-event-tracking`.
Didn't find tool you were looking for?