菜单
Audits notification permission request flows. Use when reviewing or improving permission prompts, settings paths, or denial handling.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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).
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.
Audits deep link contracts and routing behavior. Use when validating supported routes, required parameters, and cold or warm start handling.
Helps authors create new Clix agent skills by first researching the latest Clix SDK + docs via the Clix MCP Server, then generating a complete skill folder (SKILL.md, references, scripts, examples) aligned with the conventions in this repository. Use when the user asks to create/author a new Clix skill, extend the skills library, or when the user types `clix-skill-creator`.
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`.
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".
| name | auditing-permission-ux |
| display-name | Auditing Permission UX |
| short-description | Permission UX audit |
| description | Audits notification permission request flows. Use when reviewing or improving permission prompts, settings paths, or denial handling. |
| user-invocable | true |
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.
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)
Ask only what is needed:
Document the current permission flow directly from the app:
Output a concise report in markdown with:
Optional: generate a report template:
bash skills/auditing-permission-ux/scripts/generate-permission-ux-audit-report.sh .mobile/permission-ux-audit.md
Confirm:
SKILL.mdreferences/examples/ (optional)scripts/ (execute; do not load)references/permission-ux-best-practices.md