agentsclimarketplace

Policies and authorization

Skill soden46/syarif-laravel-ai-skills/skills/policies-and-authorization

Reusable Laravel AI skills for Codex, Claude Code, and other AI coding assistants

Install
npx -y skills add soden46/syarif-laravel-ai-skills --skill policies-and-authorization

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Laravel guidance to enforce access via Policies and Gates; use authorize() and authorizeResource() to standardize controller protections

SKILL.md

2.0 KB, 349 tokens by cl100k_base, as published. Nobody here has run it

Policies And Authorization

Use this skill when a Laravel task involves policies and authorization.

This skill is adapted to the personal Laravel standards in this repository. It maps the public policies-and-authorization topic from jpcaparas/superpowers-laravel into the local policies-and-authorization catalog without copying third-party skill body text.

Syarif Defaults

  • Follow Laravel conventions before introducing custom abstractions.
  • Prefer project-local patterns when they are explicit and tested.
  • Keep controllers focused on HTTP orchestration.
  • Put validation, authorization, transactions, side effects, and integrations at clear boundaries.
  • Keep client names, credentials, internal URLs, provider secrets, and project-specific business rules out of reusable standards.
  • Verify important behavior with the smallest meaningful tests and quality checks.

Workflow

  1. Detect the Laravel version, PHP version, runner, package manager, and existing project conventions.
  2. Identify the smallest local skill set that overlaps this topic.
  3. Implement or review the change using Laravel-native APIs first.
  4. Add abstractions only when they reduce real complexity or protect a meaningful boundary.
  5. Run targeted tests and available quality checks before handoff.

Checkpoints

  • Authorization and validation boundaries are explicit.
  • Query shape, transactions, queues, cache, files, and external calls are intentional when touched.
  • User-facing behavior has feature, unit, browser, or integration tests at the right level.
  • Logs and errors are useful without exposing secrets or unnecessary personal data.
  • Documentation or proposals avoid importing source-project names or one-off business rules.

Related Skills

  • using-laravel-standards
  • architecture
  • testing
  • security

Gives 0 of the 12 instructions most auth identity skills give in 349 tokens

Counted across 409 of the 410 authors here whose files we hold, read 2026-08-06

  • hash passwords with bcrypt or argon2in 53 of 409, across 43 files
  • use parameterized queriesin 47 of 409, across 39 files
  • load SECRET_KEY from environment variablesin 23 of 409, across 14 files
  • validate all input server-sidein 19 of 409, across 11 files
  • refresh access tokens before expiryin 17 of 409, across 9 files
  • store tokens in httponly cookiesin 17 of 409, across 16 files
  • store refresh tokens securelyin 16 of 409, across 6 files
  • validate webhook signatures before processingin 15 of 409, across 5 files
  • sanitize user inputsin 15 of 409, across 9 files
  • implement rate limiting on auth endpointsin 14 of 409, across 9 files
  • encrypt sensitive data at restin 13 of 409, across 10 files
  • validate uploaded file extensions and sizesin 12 of 409, across 5 files

Said here and by no other author read

  • Follow Laravel conventions before custom abstractions
  • Keep controllers focused on HTTP orchestration
  • Make authorization and validation boundaries explicit
  • Detect the Laravel and PHP versions
  • Detect the runner and package manager
  • Detect existing project conventions

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.