Configuring Horizon
coollabsio/coolify
A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.
Build and work with Spatie Laravel Permission features, including roles, permissions, middleware, policies, teams, and Blade directives.
$ npx skills add yungifez/skuul --skill laravel-permission-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yungifez/skuul laravel-permission-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/yungifez/skuul.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.grok/skills/laravel-permission-development .claude/skills/laravel-permission-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "laravel-permission-development" agent skill from https://github.com/yungifez/skuul/tree/main/.grok/skills/laravel-permission-development into .claude/skills/laravel-permission-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "laravel-permission-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/yungifez/skuul/tree/main/.grok/skills/laravel-permission-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add yungifez/skuul --skill laravel-permission-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yungifez/skuul laravel-permission-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yungifez/skuul.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.grok/skills/laravel-permission-development .agents/skills/laravel-permission-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "laravel-permission-development" agent skill from https://github.com/yungifez/skuul/tree/main/.grok/skills/laravel-permission-development into .agents/skills/laravel-permission-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "laravel-permission-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yungifez/skuul --skill laravel-permission-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yungifez/skuul laravel-permission-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yungifez/skuul.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.grok/skills/laravel-permission-development .cursor/skills/laravel-permission-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "laravel-permission-development" agent skill from https://github.com/yungifez/skuul/tree/main/.grok/skills/laravel-permission-development into .cursor/skills/laravel-permission-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "laravel-permission-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/yungifez/skuul.git --path .grok/skills/laravel-permission-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yungifez/skuul --skill laravel-permission-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yungifez/skuul laravel-permission-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yungifez/skuul.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.grok/skills/laravel-permission-development .gemini/skills/laravel-permission-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "laravel-permission-development" agent skill from https://github.com/yungifez/skuul/tree/main/.grok/skills/laravel-permission-development into .gemini/skills/laravel-permission-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "laravel-permission-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install yungifez/skuul laravel-permission-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add yungifez/skuul --skill laravel-permission-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yungifez/skuul.git skills-src && mkdir -p .github/skills && cp -r skills-src/.grok/skills/laravel-permission-development .github/skills/laravel-permission-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "laravel-permission-development" agent skill from https://github.com/yungifez/skuul/tree/main/.grok/skills/laravel-permission-development into .github/skills/laravel-permission-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "laravel-permission-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yungifez/skuul --skill laravel-permission-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yungifez/skuul laravel-permission-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yungifez/skuul.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.grok/skills/laravel-permission-development .opencode/skills/laravel-permission-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "laravel-permission-development" agent skill from https://github.com/yungifez/skuul/tree/main/.grok/skills/laravel-permission-development into .opencode/skills/laravel-permission-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "laravel-permission-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
laravel-permission-developmentBuild and work with Spatie Laravel Permission features, including roles, permissions, middleware, policies, teams, and Blade directives.
Laravel Permission Development is an agent skill from yungifez/skuul. Build and work with Spatie Laravel Permission features, including roles, permissions, middleware, policies, teams, and Blade directives.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Backend development. It works with Laravel and PHP. The repository describes itself as: A multi school management system. The licence is MIT.
Read from SKILL.md and the folder at commit 8de86ba. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are php and blade).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Laravel Permission Development loads about 1.9k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 242 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from yungifez/skuul at commit 8de86ba, republished under its MIT licence (© yungifez). 242 words, ~1,863 tokens.
.claude/skills/laravel-permission-development/SKILL.md (or your agent's skills folder).Use this skill when working with authorization, roles, permissions, access control, middleware guards, or Blade permission directives using spatie/laravel-permission.
$user->can('permission-name') for all authorization checks (supports Super Admin via Gate).HasRoles trait (which includes HasPermissions) is added to User models.Add the HasRoles trait to your User model:
use Spatie\Permission\Traits\HasRoles;
class User extends Authenticatable
{
use HasRoles;
}use Spatie\Permission\Models\Role;
use Spatie\Permission\Models\Permission;
$role = Role::create(['name' => 'writer']);
$permission = Permission::create(['name' => 'edit articles']);
// findOrCreate is idempotent (safe for seeders)
$role = Role::findOrCreate('writer', 'web');
$permission = Permission::findOrCreate('edit articles', 'web');// Assign roles to users
$user->assignRole('writer');
$user->assignRole('writer', 'admin');
$user->assignRole(['writer', 'admin']);
$user->syncRoles(['writer', 'admin']); // replaces all
$user->removeRole('writer');
// Assign permissions to roles (preferred)
$role->givePermissionTo('edit articles');
$role->givePermissionTo(['edit articles', 'delete articles']);
$role->syncPermissions(['edit articles', 'delete articles']);
$role->revokePermissionTo('edit articles');
// Reverse assignment
$permission->assignRole('writer');
$permission->syncRoles(['writer', 'editor']);
$permission->removeRole('writer');// Permission checks (preferred - supports Super Admin via Gate)
$user->can('edit articles');
$user->canAny(['edit articles', 'delete articles']);
// Direct package methods (bypass Gate, no Super Admin support)
$user->hasPermissionTo('edit articles');
$user->hasAnyPermission(['edit articles', 'publish articles']);
$user->hasAllPermissions(['edit articles', 'publish articles']);
$user->hasDirectPermission('edit articles');
// Role checks
$user->hasRole('writer');
$user->hasAnyRole(['writer', 'editor']);
$user->hasAllRoles(['writer', 'editor']);
$user->hasExactRoles(['writer', 'editor']);
// Get assigned roles and permissions
$user->getRoleNames(); // Collection of role name strings
$user->getPermissionNames(); // Collection of permission name strings
$user->getDirectPermissions(); // Direct permissions only
$user->getPermissionsViaRoles(); // Inherited via roles
$user->getAllPermissions(); // Both direct and inherited$users = User::role('writer')->get();
$users = User::withoutRole('writer')->get();
$users = User::permission('edit articles')->get();
$users = User::withoutPermission('edit articles')->get();Register middleware aliases in bootstrap/app.php:
->withMiddleware(function (Middleware $middleware) {
$middleware->alias([
'role' => \Spatie\Permission\Middleware\RoleMiddleware::class,
'permission' => \Spatie\Permission\Middleware\PermissionMiddleware::class,
'role_or_permission' => \Spatie\Permission\Middleware\RoleOrPermissionMiddleware::class,
]);
})Use in routes (pipe | for OR logic):
Route::middleware(['permission:edit articles'])->group(function () { ... });
Route::middleware(['role:manager|writer'])->group(function () { ... });
Route::middleware(['role_or_permission:manager|edit articles'])->group(function () { ... });
// With specific guard
Route::middleware(['role:manager,api'])->group(function () { ... });For single permissions, Laravel's built-in can middleware also works:
Route::middleware(['can:edit articles'])->group(function () { ... });Prefer @can (permission-based) over @role (role-based):
@can('edit articles')
{{-- User can edit articles (supports Super Admin) --}}
@endcan
@canany(['edit articles', 'delete articles'])
{{-- User can do at least one --}}
@endcanany
@role('admin')
{{-- Only use for super-admin type checks --}}
@endrole
@hasanyrole('writer|admin')
{{-- Has writer or admin --}}
@endhasanyroleUse Gate::before in AppServiceProvider::boot():
use Illuminate\Support\Facades\Gate;
public function boot(): void
{
Gate::before(function ($user, $ability) {
return $user->hasRole('Super Admin') ? true : null;
});
}This makes $user->can() and @can always return true for Super Admins. Must return null (not false) to allow normal checks for other users.
Use $user->can() inside policy methods to check permissions:
class PostPolicy
{
public function update(User $user, Post $post): bool
{
if ($user->can('edit all posts')) {
return true;
}
return $user->can('edit own posts') && $user->id === $post->user_id;
}
}enum RolesEnum: string
{
case WRITER = 'writer';
case EDITOR = 'editor';
}
enum PermissionsEnum: string
{
case EDIT_POSTS = 'edit posts';
case DELETE_POSTS = 'delete posts';
}
// Most methods accept enums directly
Permission::findOrCreate(PermissionsEnum::EDIT_POSTS, 'web');
$user->assignRole(RolesEnum::WRITER);
$user->hasRole(RolesEnum::WRITER);
$role->givePermissionTo(PermissionsEnum::EDIT_POSTS);
$user->hasPermissionTo(PermissionsEnum::EDIT_POSTS);Always flush the permission cache when seeding:
class RolesAndPermissionsSeeder extends Seeder
{
public function run(): void
{
// Reset cache
app()[\Spatie\Permission\PermissionRegistrar::class]->forgetCachedPermissions();
// Create permissions
Permission::findOrCreate('edit articles', 'web');
Permission::findOrCreate('delete articles', 'web');
// Create roles and assign permissions
Role::findOrCreate('writer', 'web')
->givePermissionTo(['edit articles']);
Role::findOrCreate('admin', 'web')
->givePermissionTo(Permission::all());
}
}Enable in config/permission.php before running migrations:
'teams' => true,Set the active team in middleware:
setPermissionsTeamId($teamId);When switching teams, unset cached relations:
$user->unsetRelation('roles')->unsetRelation('permissions');Enable in config/permission.php:
'events_enabled' => true,Available events: RoleAttachedEvent, RoleDetachedEvent, PermissionAttachedEvent, PermissionDetachedEvent in the Spatie\Permission\Events namespace.
app()[\Spatie\Permission\PermissionRegistrar::class]->forgetCachedPermissions()Permission::insert() for speed, but flush the cache afterward.© yungifez, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .grok/skills/laravel-permission-development of yungifez/skuul.
Open the folder on GitHubat commit 8de86ba
Laravel Permission Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Laravel Permission Development this skillyungifez/skuul | 409 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Configuring Horizoncoollabsio/coolify | 63k | 4 repos | ~898 | Automated safety check: Pass | MIT | |
| Fortify Developmentcoollabsio/coolify | 63k | 4 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Laravel Best Practicesanonaddy/anonaddy | 4.9k | 13 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Geoflowyaojingang/GEOFlow | 3.8k | — | ~722 | Automated safety check: Pass | AGPL-3.0 | |
| Livewire Developmentcoollabsio/coolify | 63k | — | ~964 | Automated safety check: Pass | MIT |
coollabsio/coolify
A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
anonaddy/anonaddy
Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code.
yaojingang/GEOFlow
Operate/develop GEOFlow CLI/Laravel/admin/API, topics/专题 and topic tasks, theme libraries/replication, sites/leads/Agent, channel sync and legacy yao-geoflow-cli/design/template migration.
coollabsio/coolify
A skill your agent uses for any task or question involving Livewire.
Jeffallan/claude-skills
Builds Laravel 10+ applications with Eloquent models, Sanctum authentication, Horizon queues, API resources and Livewire components, tested with Pest or PHPUnit.
yungifez/skuul
A skill your agent uses for any task or question involving Livewire.
yungifez/skuul
Deploys and manages Laravel applications on Laravel Cloud using the cloud CLI.
Categories
Build and work with Spatie Laravel Permission features, including roles, permissions, middleware, policies, teams, and Blade directives. Laravel Permission Development is an agent skill from yungifez/skuul. Build and work with Spatie Laravel Permission features, including roles, permissions, middleware, policies, teams, and Blade directives.
Laravel Permission Development fits situations like: tasks that involve Backend development.
Run `npx skills add yungifez/skuul --skill laravel-permission-development -a claude-code`. Or copy the skill folder (.grok/skills/laravel-permission-development in yungifez/skuul) into .claude/skills/laravel-permission-development in your project. Claude Code loads it when a task matches its description.
Run `npx skills add yungifez/skuul --skill laravel-permission-development -a codex`. Or copy the skill folder (.grok/skills/laravel-permission-development in yungifez/skuul) into .agents/skills/laravel-permission-development in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yungifez/skuul --skill laravel-permission-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/laravel-permission-development, .gemini/skills/laravel-permission-development, .github/skills/laravel-permission-development and .opencode/skills/laravel-permission-development in your project.
SKILL.md names no scripts, command-line tools or credentials: Laravel Permission Development is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Laravel Permission Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Laravel Permission Development: Configuring Horizon (coollabsio/coolify, 63k stars), Fortify Development (coollabsio/coolify, 63k stars), Laravel Best Practices (anonaddy/anonaddy, 4.9k stars) and Geoflow (yaojingang/GEOFlow, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
yungifez (a GitHub user) maintains it in yungifez/skuul, which has 409 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 5, 2026.
Source: yungifez/skuul on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.