write-script-php

MUST use when writing PHP scripts.

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./system_prompts/auto-generated/skills/write-script-php/SKILL.md

Quality

Content

67%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 body is a strong, actionable reference: concrete Windmill CLI commands, complete PHP code patterns, and well-sequenced guidance with sensible guards against accidental deploys. Its main weakness is verbosity in the metadata-sync explanation and a couple of placeholder/prose arg formats.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient Windmill-specific guidance Claude would not know, but passages like the metadata-sync rationale and the dependency-bump explanation run long and could be tightened; not a 4 because several sentences over-explain, not a 2 because the content is substantive rather than padded fluff.	3 / 5
Actionability	Concrete commands (wmill script preview/run, generate-metadata, sync push, rehash, --dry-run) and complete copy-paste PHP examples for main(), resource types, and library deps give mostly executable guidance; not a 5 because the preview arg form `-d '<args>'` is a placeholder and per-language arg shapes are described in prose rather than shown.	4 / 5
Workflow Clarity	Clear write→preview→generate-metadata→deploy sequence with explicit guards (only deploy when asked, don't deploy-just-to-test) and validation checkpoints (--dry-run, diff the regenerated lock, rehash); not a 5 because there is no full validate→fix→retry loop spelled out for the deploy step itself.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and one-level-deep, clearly signaled references to AGENTS.wmill.md and the preview skill; no bundle files exist so all content is inline, which is appropriate here, with only minor organization gaps; not a 5 because some metadata-sync detail could live in a referenced file.	4 / 5
	Total	15 / 20 Passed

Description

32%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 a terse trigger-only line: it tells Claude when to use the skill but not what it does. It is narrowly scoped to PHP, but lacks any concrete capability statement or natural keyword variations.

Suggestions

Add a "what" clause stating concrete actions, e.g. "Writes Windmill PHP scripts: defines main(), resource types, and library deps, then previews and syncs metadata."

Expand trigger terms with natural synonyms/extensions such as ".php", "PHP script", or "Windmill PHP" so users phrasing it differently still match.

Keep the explicit "Use when..." trigger but pair it with the capability summary so both what and when are answered.

Dimension	Reasoning	Score
Specificity	The description "writing PHP scripts" names the domain but lists no concrete actions (no preview/run/deploy/metadata actions), matching the "Names the domain but actions are minimal or generic" anchor; not a 1 because a domain is named, not a 3 because zero actions are enumerated.	2 / 5
Completeness	"MUST use when writing PHP scripts" gives a "when" trigger but no "what" — matching the anchor "only 'when' is present without 'what'"; not a 1 because a trigger is present, not a 3 because there is no description of what the skill does.	2 / 5
Trigger Term Quality	"writing PHP scripts" is a phrase a user might say, but it is a single generic term with no synonyms or file extensions (.php), fitting "one or two generic keywords; missing the natural phrases"; not a 3 because common variations are absent.	2 / 5
Distinctiveness Conflict Risk	Scoping to "PHP scripts" carves a clear niche distinct from sibling language skills, with only minor overlap risk against a generic write-script skill; not a 5 because the trigger is bare and could overlap the broader script-writing family.	4 / 5
	Total	10 / 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: windmill-labs/windmill
Path: system_prompts/auto-generated/skills/write-script-php/SKILL.md
Commit: 74af4ed

Reviewed: about 19 hours 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.