Back to catalog
Human reviewedDevelopment

Skill dossier

laravel-specialist

Source declaration

Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers, implementing Sanctum auth flows, building Livewire components, optimising Eloquent queries, or writing Pest/PHPUnit tests for Laravel features.

The author's original description, preserved in English. It describes intent, not verified performance.

Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers, implementing Sanctum auth flows, building Livewire components, optimising Eloquent queries, or writing Pest/PHPUnit tests for Laravel features.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

A Laravel 10+ Skill covering Eloquent models, API resources, queued jobs and Pest/PHPUnit tests, with artisan commands as checkpoints at each stage.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Creates Eloquent models with relationships, scopes and casts.
  • Builds controllers, API resources and queued jobs with failure handling.
  • Runs migrate:status, route:list and queue:work checkpoints.
  • Writes feature and unit tests and checks style with Pint.

Limitations & scope

  • Targets Laravel 10+ and PHP 8.2+.
  • Livewire, queues and testing details are in separate reference files.
  • The stated 85 percent coverage target is not verified against any project here.

Relevant for

  • Laravel backend developers
  • Teams building REST APIs with queues
  • Developers adopting Pest testing

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
56.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/laravel-specialist/references/eloquent.mdReference7.3 KB
skills/laravel-specialist/references/livewire.mdReference10.9 KB
skills/laravel-specialist/references/queues.mdReference9.2 KB
skills/laravel-specialist/references/routing.mdReference8.4 KB
skills/laravel-specialist/references/testing.mdReference12 KB
skills/laravel-specialist/SKILL.mdInstruction8.3 KB

SKILL.md frontmatter

{
  "name": "laravel-specialist",
  "description": "Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers, implementing Sanctum auth flows, building Livewire components, optimising Eloquent queries, or writing Pest/PHPUnit tests for Laravel features.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "backend",
    "triggers": "Laravel, Eloquent, PHP framework, Laravel API, Artisan, Blade templates, Laravel queues, Livewire, Laravel testing, Sanctum, Horizon",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "fullstack-guardian, test-master, devops-engineer, security-reviewer"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyse requirements

    Identify models, relationships, APIs and queue needs.

  2. 02
    Action

    Implement models

    Create Eloquent models and verify with make:model and migrate:status.

  3. 03
    Decision

    Gate on checkpoints

    Confirm routes, job processing and tests pass before treating a step as complete.

  4. 04
    Output

    Deliver tested code

    Run the coverage and Pint checks listed in the validation table before a PR.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

488 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Note

File modification is described or implemented

482 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 482 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

6 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Run migrations and queue commands against a development database, not production, and review any raw queries the agent writes.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/laravel-specialist # .claude/skills/laravel-specialist
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/laravel-specialist/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Ask Claude Code to add a Post model with a migration and confirm it proposes migrate:status and a test run as checks.

Prerequisites

  • Targets Laravel 10+ and PHP 8.2+.
  • Livewire, queues and testing details are in separate reference files.
  • The stated 85 percent coverage target is not verified against any project here.

Example prompts

Representative task

Using the laravel-specialist skill, add a Post model with soft deletes, a PostResource, a queued PublishPost job with retries, and Pest feature tests for the publish endpoint.

Inspect before use

Read the laravel-specialist skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/laravel-specialist/SKILL.md and its reference files. Explain its workflow, any commands it tells the agent to run, and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Provides code templates for model, migration, resource, job and test.
  • Ties each stage to a verifying command.

Considerations

  • Running migrations and queue workers touches the database.
  • Strict rules such as final classes may not fit existing codebases.
Research conclusion

A practical, checkpoint-driven guide for conventional Laravel feature work.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/laravel-specialist
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.