Skip to content
TrustedSkillsbeta
Back to all skills

Permission Analyzer

Checked
arjenschwarz·vlatest·security

This tool analyzes text to determine if a request implies permission, helping users understand potential consent issues and improve communication clarity.

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 arjenschwarz/agentic-coding --skill permission-analyzer -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

arjenschwarz

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 arjenschwarz/agentic-coding at 3a876e8068.

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

Commit
3a876e8068
Manifest
claude/skills/permission-analyzer/SKILL.md
Scanned
2 files, 253 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

The permission-analyzer skill assesses the permissions requested by an application or piece of code. It can identify potential security risks associated with excessive or unnecessary permissions, and suggest more restrictive alternatives. This helps ensure applications operate with minimal privilege, reducing the attack surface.

When to use it

  • Reviewing mobile app permissions: Before deploying a mobile application, analyze its requested permissions to ensure they are justified and necessary for functionality.
  • Auditing API access rights: Evaluate the permissions granted to third-party applications accessing your APIs to identify potential vulnerabilities.
  • Analyzing code snippets: When integrating new code libraries or components, use this skill to understand and validate their permission requirements.
  • Security assessments: Incorporate permission analysis into regular security audits of software systems.

Key capabilities

  • Permission request identification
  • Risk assessment based on permissions
  • Suggestion of alternative, more restrictive permissions

Example prompts

  • "Analyze the requested permissions for this AndroidManifest.xml file."
  • "What are the potential risks associated with granting 'READ_CONTACTS' permission?"
  • "Suggest a less permissive alternative to 'WRITE_EXTERNAL_STORAGE'."

Tips & gotchas

The skill requires access to the application’s permission request manifest or code snippet for analysis. The accuracy of the risk assessment depends on the context and potential use cases of the requested permissions.