Skip to content
TrustedSkillsbeta
Back to all skills

Laravel Policies And Authorization

Checked
noartem·vlatest·backend

This skill automates Laravel policy creation & authorization setup, streamlining security and simplifying access control management for your applications.

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 noartem/skills --skill laravel-policies-and-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

noartem

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 noartem/laravel-vue-skills at 0002f35143.

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

Commit
0002f35143
Manifest
skills/laravel-policies-and-authorization/SKILL.md
Scanned
1 file, 31 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 enables AI agents to implement and utilize Laravel policies for fine-grained authorization within a Laravel application. It allows developers to define specific access rules for models, controlling which users or roles can perform actions like viewing, creating, updating, or deleting data. This promotes secure and maintainable code by centralizing authorization logic.

When to use it

  • Implementing Role-Based Access Control (RBAC): Define different user roles (e.g., admin, editor, viewer) and restrict access based on these roles.
  • Protecting Sensitive Data: Ensure only authorized users can access specific resources or perform sensitive operations within the application.
  • Enforcing Business Logic for Access: Implement complex authorization rules beyond simple role assignments, such as restricting access to a record based on its ownership.
  • Centralizing Authorization Logic: Move authorization checks out of controller methods and into policies for cleaner code and easier maintenance.

Key capabilities

  • Defining Policies: Create policy classes that encapsulate authorization logic for specific models.
  • Model-Specific Rules: Apply different rules to different models based on user roles or other criteria.
  • Centralized Authorization: Move authorization checks out of controllers into policies.
  • Gate Creation: Define gates using the @can directive in Blade templates and controller methods.

Example prompts

  • "Create a policy for the 'Post' model that allows only administrators to delete posts."
  • "Generate a gate to check if a user can edit this article based on their role."
  • "Show me an example of how to use a policy to authorize access to a specific resource."

Tips & gotchas

  • Requires a working Laravel application. Familiarity with Laravel's Eloquent ORM and basic authorization concepts is helpful for effective utilization.
  • Policies are best used when you need more complex authorization logic than simple role-based checks can provide.