laravel-verification

Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is tdg-personal/laravel-verification

Quality

Content

100%

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

The content is a tight, executable verification pipeline with explicit gating and validation checkpoints across seven sequenced phases, and it is well-organized as a self-contained skill with no external file dependencies.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: terse gating bullets ('stop immediately if they fail', 'any failure blocks release') and direct commands with no padding explaining what Laravel, Composer, or PHPStan are; every section earns its tokens.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands such as 'vendor/bin/pint --test', 'composer audit', 'php artisan migrate --pretend', and 'XDEBUG_MODE=coverage php artisan test --coverage' rather than pseudocode or vague direction.	3 / 3
Workflow Clarity	A clear 7-phase sequence with explicit validation checkpoints: 'Environment and Composer checks gate everything else; stop immediately if they fail', 'Linting/static analysis should be clean before running full tests', and 'any failure blocks release', plus a feedback-style job side-effect check in Phase 7.	3 / 3
Progressive Disclosure	Self-contained with no bundle files (references/scripts/assets are empty), organized into clear one-level sections (When to Use, How It Works, Phases 1-7, Examples) with no nested references, satisfying the simple self-contained skill allowance.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 is specific and clearly scoped to Laravel, but it lacks an explicit 'Use when...' trigger clause and omits some natural user phrasings (e.g., CI pipeline, PR checks), which caps completeness and trigger-term quality at 2.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use before opening a PR, after major refactors, or pre-deployment for a Laravel project.'

Broaden trigger terms to include phrases users actually say, such as 'CI pipeline', 'PR checks', 'before deploy', and 'Laravel test run'.

Keep the concrete phase list but pair it with the explicit when-guidance so both what and when are answered in the description.

Dimension	Reasoning	Score
Specificity	Quotes concrete actions 'env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness', listing multiple specific capabilities rather than vague language.	3 / 3
Completeness	Clearly answers what the skill does via the enumerated verification phases, but the description has no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Includes relevant terms like 'Laravel', 'tests', 'coverage', 'security scans', and 'linting', but misses common natural variations a user might say such as 'CI pipeline', 'before deploy', or 'PR checks', and lacks explicit 'Use when' phrasing.	2 / 3
Distinctiveness Conflict Risk	Scoped explicitly to 'Laravel projects', a clear niche with distinct triggers that is unlikely to fire for non-Laravel skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/laravel-verification/SKILL.md
Commit: 754b8dd

Reviewed: 2 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.