backend-php

PHP Developer Agent. Laravel 기반 백엔드 개발을 담당합니다. Eloquent ORM, Artisan, Queue, Sanctum 전문.

Install with Tessl CLI

npx tessl i github:shaul1991/shaul-agents-plugin --skill backend-php

What are skills?

Review — 48%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 9 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear technical domain (Laravel/PHP) and lists specific framework components, which helps with identification. However, it lacks concrete action verbs describing what the skill actually does and completely omits trigger guidance ('Use when...'), making it difficult for Claude to know when to select this skill over others.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Laravel, PHP backend, Eloquent models, database migrations, API authentication with Sanctum, or queue jobs'

Replace the technology list with concrete actions: 'Creates Laravel migrations, builds Eloquent models, configures Sanctum authentication, implements queue jobs' instead of just listing 'Eloquent ORM, Artisan, Queue, Sanctum'

Add common user-facing terms like 'PHP backend', 'REST API', 'database queries', 'authentication' alongside the framework-specific terminology

Dimension	Reasoning	Score
Specificity	Names the domain (Laravel backend development) and lists specific technologies (Eloquent ORM, Artisan, Queue, Sanctum), but doesn't describe concrete actions like 'create migrations', 'build APIs', or 'configure authentication'.	2 / 3
Completeness	Describes what it specializes in (Laravel backend development with specific tools) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant technical terms (Laravel, Eloquent ORM, Artisan, Queue, Sanctum, PHP) that developers would use, but missing common variations like 'backend API', 'database queries', 'authentication', 'job processing', or file extensions like '.php'.	2 / 3
Distinctiveness Conflict Risk	Laravel-specific terms provide some distinction from generic PHP or other framework skills, but 'PHP Developer Agent' and 'backend development' are broad enough to potentially conflict with other PHP or backend-related skills.	2 / 3
	Total	7 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive Laravel development guide with excellent actionable code examples covering controllers, services, repositories, Eloquent models, and testing patterns. However, it's overly long for a SKILL.md file, includes some redundant explanations of concepts Claude knows, and lacks validation checkpoints in workflows. The content would benefit from being split into a concise overview with links to detailed reference files.

Suggestions

Add validation checkpoints to the '새 기능 개발' workflow (e.g., 'Run php artisan test after each step', 'Verify migration with migrate:status')

Split detailed code examples (Eloquent patterns, testing examples, security) into separate reference files and link from main SKILL.md

Remove or condense the '전문 영역' bullet lists - Claude already knows what Eloquent ORM and Blade are

Add error recovery guidance for common failure scenarios (failed migrations, queue job failures)

Dimension	Reasoning	Score
Conciseness	The skill contains useful information but is verbose in places. The '역할' and '전문 영역' sections list concepts Claude already knows, and the extensive code examples could be more condensed. However, the code patterns themselves are valuable and not overly explained.	2 / 3
Actionability	Provides fully executable, copy-paste ready code examples throughout - from controllers to repositories, migrations to tests. The Artisan commands section and workflow steps are concrete and immediately usable.	3 / 3
Workflow Clarity	The '새 기능 개발' section provides a clear sequence of steps, but lacks validation checkpoints. For database migrations and deployments, there are no explicit verification steps or rollback guidance for when things go wrong.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but the document is monolithic at ~350 lines. The Eloquent patterns, testing examples, and security sections could be split into separate reference files with links from the main skill.	2 / 3
	Total	9 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (509 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	9 / 11 Passed

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.