Skip to content
TrustedSkillsbeta
Back to all skills

Unit Test Security Authorization

Checked
giuseppe-trisciuoglio·vlatest·security·MIT

Helps with testing, security as part of implementing security and authentication workflows.

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 giuseppe-trisciuoglio/developer-kit --skill unit-test-security-authorization -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

giuseppe-trisciuoglio

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 giuseppe-trisciuoglio/developer-kit-claude-code at fe73fb33a0.

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

Commit
fe73fb33a0
Manifest
plugins/developer-kit-java/skills/unit-test-security-authorization/SKILL.md
Scanned
5 files, 1,138 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 write unit tests for security authorization logic. It focuses on verifying that access control decisions are made correctly based on user roles and permissions, ensuring only authorized users can perform specific actions. The generated tests help identify vulnerabilities related to incorrect authorization implementations.

When to use it

  • Developing new features: Automatically generate initial security test suites when building new functionality with access control requirements.
  • Refactoring existing code: Ensure that changes to authorization logic don't introduce regressions or bypasses.
  • Security audits: Quickly create a baseline of tests to evaluate the effectiveness of current authorization implementations.
  • Code reviews: Provide reviewers with automatically generated test cases to verify security authorization logic.

Key capabilities

  • Generates unit tests for authorization code.
  • Focuses on verifying access control decisions.
  • Tests based on user roles and permissions.

Example prompts

  • "Generate unit tests for the check_admin_permission function."
  • "Create a test suite to verify that only users with 'editor' role can publish articles."
  • "Write tests ensuring unauthorized users cannot access the /admin/dashboard endpoint."

Tips & gotchas

This skill is most effective when provided with clear and well-defined authorization logic. It assumes the underlying code structure follows standard practices for security authorization implementations.