Skip to content
TrustedSkillsbeta
Back to all skills

Auditing Permission Ux

Checked
clix-so·vlatest·security

Analyzes user interface permission flows to identify UX friction points and compliance risks, optimizing clarity and trust.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add clix-so/skills --skill auditing-permission-ux -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

clix-so

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned clix-so/skills at 71afaf5dd2.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
71afaf5dd2
Manifest
skills/auditing-permission-ux/SKILL.md
Scanned
4 files, 163 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to audit user permission settings and identify potential UX issues related to those permissions. It can analyze existing permission flows, highlight confusing or overly complex steps, and suggest improvements based on best practices for usability and clarity. The goal is to ensure users understand and control their privacy and security settings effectively.

When to use it

  • Redesigning a Permissions System: Before launching a new permissions system, use this skill to proactively identify potential UX pitfalls.
  • Troubleshooting User Confusion: If users are frequently contacting support about permission-related issues, leverage the skill to diagnose and resolve underlying usability problems.
  • Compliance Audits: As part of compliance efforts (e.g., GDPR), audit existing permissions flows for clarity and user control.
  • Improving Feature Adoption: Permissions often gate access to valuable features; ensure these are easily understood and managed.

Key capabilities

  • Permission flow analysis
  • UX issue identification
  • Best practice suggestions
  • Clarity assessment

Example prompts

  • "Analyze the user permission flow for accessing location data and identify any potential UX issues."
  • "Suggest improvements to make our privacy settings more understandable for non-technical users."
  • “Audit this existing permissions system: [paste system description]”

Tips & gotchas

The effectiveness of this skill depends on providing clear and detailed descriptions of the permission flows being audited. It's most helpful when given context about the target user base and their technical proficiency.