github-actions-php

Defines GitHub Actions configuration for running PHP/Laravel CI pipeline

Quality

61%

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

72%

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

The content is commendably concise and well-organized for a simple definition-style skill, but its guidance stays at a high level without executable specifics or validation checkpoints for the database-related steps it prescribes.

Suggestions

Add concrete, executable guidance (e.g., a minimal workflow YAML snippet or specific commands) so the CI structure is copy-paste ready rather than only enumerated.

Insert validation/feedback checkpoints into the Execution Flow (e.g., verify MySQL is reachable before migrations, confirm migrations succeeded before running tests).

Fix the typo on the Database Requirement line ("MySQL =MariaDB") so the constraint is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — "Defines CI workflow structure only" and "This skill defines 'how CI runs', not 'what is correct'" — with no padding or explanations of concepts Claude already knows, matching the score-3 anchor.	3 / 3
Actionability	It names concrete components ("PHP version matrix", "Composer install steps") and a sequenced flow, but provides no executable commands, YAML snippets, or copy-paste-ready specifics, leaving guidance incomplete as in the score-2 anchor.	2 / 3
Workflow Clarity	The "Execution Flow" lists a clear 1–6 sequence, but there are no validation checkpoints or error-recovery feedback loops for database/migration operations, which caps workflow clarity at 2 per the scoring notes.	2 / 3
Progressive Disclosure	This is a simple skill under 50 lines with no external references, and it is organized into clear, well-separated sections (Purpose, Scope, Non-Scope, Database Requirement, Execution Flow, Principle), matching the score-3 guidance for simple skills.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 identifies the niche and a core action but stops short of listing multiple concrete capabilities or providing explicit trigger guidance, leaving it solidly at the midpoint of the rubric.

Suggestions

Add a "Use when..." clause naming natural trigger terms (e.g., GitHub Actions workflow, CI pipeline, Laravel tests) to raise completeness and trigger-term quality.

List a few specific concrete actions (e.g., define PHP version matrix, set up MySQL service, run migrations and tests) instead of one broad action to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete action category ("Defines GitHub Actions configuration for running PHP/Laravel CI pipeline"), but it is a single broad action rather than a list of multiple specific concrete actions like the score-3 anchor.	2 / 3
Completeness	The description states what the skill does but lacks any "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Relevant natural terms appear ("GitHub Actions", "PHP", "Laravel", "CI pipeline"), but common variations a user might say (e.g., "workflow", "continuous integration", "tests") are missing, matching the score-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The platform+stack niche (GitHub Actions + PHP/Laravel) is somewhat specific, but the absence of explicit trigger phrasing leaves overlap risk with generic CI/PHP skills, matching the score-2 anchor.	2 / 3
	Total	8 / 12 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: fb83b36

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