mysql-php-fixer

Update and fix remote MySQL for PHP websites

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/mysql-php-fixer/SKILL.md

Quality

Content

40%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 skill is well-structured and conceptually safe-minded, but it functions as an invocation guide rather than actionable instructions: it lacks executable commands, concrete examples, and a sequenced workflow with validation checkpoints for destructive database operations.

Suggestions

Add concrete, executable examples (e.g. mysql connection-test commands, a sample migration SQL block, a PHP PDO snippet) instead of restating task categories.

Replace the repetitive example-prompt blocks with a single sequenced workflow: verify connection -> backup -> apply change in staging -> validate -> promote to production -> log.

Insert explicit validation checkpoints (e.g. 'run the migration on a staging copy and confirm row counts before production') to satisfy the destructive-operation workflow requirement.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clear bullets and no concept over-explanation, but the five near-identical example-prompt blocks rephrase capabilities already listed, adding padding that could be tightened.	3 / 5
Actionability	The body offers only high-level task categories and example user prompts; it contains no executable SQL, PHP snippets, or shell commands, giving minimal concrete guidance for actually performing the work.	2 / 5
Workflow Clarity	Safety features are listed (backup, staging validation, rollback) but never as a sequenced workflow with checkpoints; for destructive database operations the absence of an explicit validate-then-proceed sequence leaves only a rough, poorly-defined flow.	2 / 5
Progressive Disclosure	The body is self-contained with well-organized section headers and no nested references; minor organization gaps come from repetitive inline example-prompt blocks that could be condensed, but structure is good overall.	4 / 5
	Total	11 / 20 Passed

Description

61%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 is concise and names a clear, fairly distinct niche, but it lacks any explicit 'when to use' trigger guidance and its action verbs are generic. Adding a 'Use when...' clause with concrete trigger phrases would lift completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when fixing MySQL connection errors, applying schema migrations, or tuning database performance on PHP sites.'

Replace generic verbs ('Update and fix') with concrete actions such as 'test connectivity, run migrations, optimize queries, and patch SQL injection risks'.

Include common user synonyms like 'database', 'queries', and 'connection errors' to improve natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Update and fix remote MySQL for PHP websites' names a clear domain plus two actions (update, fix), but those verbs are generic and not comprehensive, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	It gives a clear 'what' ('Update and fix remote MySQL for PHP websites') but no 'Use when...' trigger clause, so per the guideline a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	It surfaces natural terms users would say ('MySQL', 'PHP', 'fix', 'remote MySQL'), giving good keyword coverage, though common variations like 'database' or 'queries' are absent.	4 / 5
Distinctiveness Conflict Risk	The remote-MySQL-for-PHP niche is mostly distinct with only minor overlap risk against general database or MySQL skills, fitting the 'mostly distinct' anchor.	4 / 5
	Total	14 / 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: Mirxa27/arabclue
Path: .opencode/skills/mysql-php-fixer/SKILL.md
Commit: d9c0ab5

Reviewed: 1 day 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.