CtrlK
BlogDocsLog inGet started
Tessl Logo

laravel-verification

Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness. Use when verifying a Laravel project before merge or deploy — lint, static analysis, tests, coverage, security.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

A well-sequenced, highly actionable verification pipeline with strong gating and validation across phases. The main improvement is removing the redundant Examples block that repeats per-phase commands and adding an explicit error-recovery retry step.

Suggestions

Remove or trim the Examples section, since it duplicates commands already given in each phase, or replace it with a single canonical pipeline reference.

Add an explicit fix-and-revalidate retry loop (e.g., 'if lint/static analysis fails, fix and re-run before proceeding to tests') to strengthen the feedback loop.

Add a final pre-deploy checklist summarizing the pass/fail gates so the workflow ends with a clear go/no-go checkpoint.

DimensionReasoningScore

Conciseness

Mostly lean with command-first phases and short bullets, but the Examples section re-lists commands already shown per phase, adding modest redundancy.

4 / 5

Actionability

Fully executable copy-paste bash commands for every phase, with concrete variants for Sail, Psalm, Horizon, and a CI pipeline; covers the common cases directly.

5 / 5

Workflow Clarity

Clear sequential phases with explicit gating ('stop immediately if they fail', 'any failure blocks release') and validation (migrate --pretend, queue:failed), but no explicit fix-and-revalidate retry loop or final checklist, keeping it just below 5.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear phase headers and no nested references; the duplicated Examples block is a minor organization gap, and no bundle files exist to reference.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

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

A specific, well-triggered description that clearly states both capability and usage context with concrete Laravel verification triggers. Minor keyword synonyms (CI, PR) could broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness' — giving comprehensive coverage of the verification domain.

5 / 5

Completeness

Explicitly answers both 'what' (the verification loop and its phases) and 'when' ('Use when verifying a Laravel project before merge or deploy — lint, static analysis, tests, coverage, security') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural triggers ('verifying a Laravel project before merge or deploy', 'lint', 'static analysis', 'tests', 'coverage', 'security') that users would say; a few common variants like 'CI' or 'PR check' are absent, keeping it just below 5.

4 / 5

Distinctiveness Conflict Risk

Anchored tightly to Laravel with a distinct pre-merge/pre-deploy verification niche, so it is unlikely to trigger for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
Reviewed

Table of Contents

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.