github-actions-php

Defines GitHub Actions configuration for running PHP/Laravel CI pipeline

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/github-actions-php/SKILL.md

Quality

Content

65%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.

The content is exceptionally concise and well-structured, but it stays at the level of describing the CI pipeline rather than providing executable GitHub Actions YAML or commands, and it omits validation checkpoints for the migration/test steps. Supplying a concrete workflow file and a verification step would lift the two weaker dimensions.

Suggestions

Provide an executable starter GitHub Actions workflow YAML (jobs, services for MySQL, composer install, artisan migrate, test runner) instead of only naming the steps.

Add an explicit validation checkpoint after migrations/tests, e.g. "Verify: `php artisan migrate:status` succeeds and the test suite exits 0 before proceeding."

Specify the PHP version matrix and MySQL service image concretely (e.g., `php:8.3`, `services: mysql: image: mysql:8`) so the guidance is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean and token-efficient: short bulleted scope/non-scope lists and a terse numbered flow with no concept explanations or padding, assuming Claude's competence throughout.	5 / 5
Actionability	It names concrete tasks ("Setup PHP environment", "Install dependencies", "Boot MySQL service", "Run migrations") but gives no executable GitHub Actions YAML, commands, or version specifics — high-level hints missing the specific steps to actually execute.	2 / 5
Workflow Clarity	A clear six-step sequence is present, but the pipeline runs migrations and tests (batch/destructive-adjacent) with no validation checkpoint (e.g., verify migrations applied, confirm tests passed), so per the batch-operation rule workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no external references needed and is well-organized into clearly labeled sections (Purpose, Scope, Non-Scope, Database Requirement, Execution Flow, Principle), meeting the simple-skill exception for a top score.	5 / 5
	Total	15 / 20 Passed

Description

53%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.

The description clearly states what the skill does and targets a reasonably distinct niche, but it lacks any "when to use" trigger guidance and only gestures at a single action. Adding an explicit "Use when..." clause with concrete CI tasks would raise completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up or modifying GitHub Actions CI for a PHP/Laravel project."

Expand the action list from the single "Defines configuration" to concrete tasks (e.g., "runs the test suite, lints code, installs Composer dependencies").

Include natural synonyms users say, such as "CI workflow", "GitHub Actions workflow", and "run Laravel tests".

Dimension	Reasoning	Score
Specificity	Names the domain ("GitHub Actions configuration for running PHP/Laravel CI pipeline") and one concrete action ("Defines ... configuration"), but lists no further specific actions like running tests or deploying, so it sits at domain-plus-one-action rather than comprehensive.	3 / 5
Completeness	Gives a clear "what" (defines GitHub Actions config for a PHP/Laravel CI pipeline) but provides no "when" / "Use when..." clause, so per the judging guideline completeness is capped at 3 for missing explicit trigger guidance.	3 / 5
Trigger Term Quality	Includes natural terms users would say ("GitHub Actions", "PHP", "Laravel", "CI"), but misses common variations and synonyms such as "workflow", "tests", "tests", "pipeline" as a trigger, and any file extensions, leaving keyword coverage partial.	3 / 5
Distinctiveness Conflict Risk	The "GitHub Actions + PHP/Laravel CI pipeline" combination is a fairly distinct niche with clear triggers; it could overlap only marginally with general CI or Laravel-testing skills, fitting "mostly distinct; minor overlap risk."	4 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: Bottelet/DaybydayCRM
Path: .claude/skills/github-actions-php/SKILL.md
Commit: 2199c1e

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