auditing-permission-ux — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited auditing-permission-ux (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} asks the agent to disclose its hidden system prompt or initial instructions. That is often the first step of a larger attack: knowing the system prompt lets an attacker craft inputs that defeat its constraints by mimicking its own voice.
repeat/reveal/print your system prompt request from the skill.Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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.mdConfirm:
SKILL.mdreferences/examples/ (optional)scripts/ (execute; do not load)references/permission-ux-best-practices.md~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.