Skip to content
TrustedSkillsbeta
Back to all skills

File Permission Test

Checked
matteocervelli·vlatest·security·MIT

Checks if an AI agent has read/write permissions to a specified file path.

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 matteocervelli/llms --skill file-permission-test --full-depth -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

matteocervelli

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 matteocervelli/llms at 1e1f2089eb.

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

Commit
1e1f2089eb
Manifest
.archive/claude-v1/skills/file-permission-test/SKILL.md
Scanned
1 file, 55 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 an AI agent to test if a given user has permission to access a specified file. It determines whether the user can read, write, or execute the file based on the operating system's permissions settings. The agent can then report these findings and adjust actions accordingly.

When to use it

  • Automated Security Audits: Regularly check file permissions across a server to identify potential vulnerabilities.
  • User Access Control: Verify if a user has the necessary rights before allowing them to modify or execute a script.
  • Troubleshooting Permission Errors: Diagnose why a user is unable to access or manipulate a specific file.
  • Scripted Deployment: Ensure correct permissions are set on deployed files and directories.

Key capabilities

  • File permission checking (read, write, execute)
  • Operating system compatibility
  • User identification for permission assessment

Example prompts

  • "Can user 'john' read the file '/var/log/syslog'?"
  • "Does the current user have execute permissions on /opt/my_script.sh?"
  • "Check if anyone can write to the configuration file at /etc/app.conf."

Tips & gotchas

The skill requires appropriate operating system access for accurate permission checks. Results are dependent on the underlying OS's permission model and may require elevated privileges in some cases.