write-script-php

MUST use when writing PHP scripts.

Quality

63%

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

77%

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

The content is highly actionable with executable code and commands, and the workflow is clearly sequenced with validation checkpoints for destructive steps. Its main weaknesses are mild repetition of deploy caveats and a monolithic structure that mixes language-agnostic Windmill workflow with PHP specifics.

Suggestions

De-duplicate the "deploy only on explicit request" and "generate-metadata is not a deploy" guidance into one canonical statement referenced where needed, to recover token budget.

Consider splitting the Windmill CLI workflow from the PHP language rules (e.g. a references/PHP.md) so SKILL.md stays a concise overview with one-level-deep references.

Tighten the metadata-sync paragraph, which explains import propagation and version bumps at length; the dry-run/diff guidance already carries the key points.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, Windmill-specific guidance Claude would not already know, but the deploy caveat ("only when the user explicitly asks to deploy/publish/push") and "generate-metadata is not a deploy" note are restated across several sections and could be tightened.	2 / 3
Actionability	It provides fully executable PHP code blocks for main(), resource types with class_exists guards, and library-dependency comments, plus concrete copy-paste wmill commands ("wmill script preview <path>", "wmill generate-metadata --dry-run", "wmill generate-metadata rehash").	3 / 3
Workflow Clarity	Decision rules are explicit ("Only use script run when...", "Only use sync push when..."), and risky operations have validation checkpoints: dry-run to list stale items, diffing regenerated lock files to catch version bumps, and gating deploys on an explicit user request.	3 / 3
Progressive Disclosure	Section headers are clear, but the single file mixes two distinct concerns (the Windmill CLI workflow for any script language and PHP-specific structure/dependency rules) that could be split, and there are no one-level-deep bundle references to offload either block.	2 / 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 is terse and uses third-person imperative voice, but it tells Claude when to fire without explaining what the skill actually does or offering trigger-term variations. It sits firmly at the mid level across all dimensions.

Suggestions

Add a "what" clause stating the skill's purpose, e.g. "Structures Windmill PHP scripts with a main() function, resource types, and library dependencies. Use when writing or editing PHP scripts for Windmill."

Broaden trigger terms to include natural variations users say ("PHP script", "Windmill script", "main function", "resource type") so the skill is more discoverable.

Include the Windmill-specific context in the description to distinguish it from generic PHP skills and reduce conflict risk.

Dimension	Reasoning	Score
Specificity	The phrase "writing PHP scripts" names the domain and a single action, but gives no list of concrete capabilities (e.g. create, edit, structure, declare dependencies) beyond the verb "writing".	2 / 3
Completeness	It has an explicit "when" trigger ("MUST use when writing PHP scripts") but the "what does this do" half is only implied by the trigger itself; it never states the skill's purpose.	2 / 3
Trigger Term Quality	"writing PHP scripts" is a natural phrase a user might say, but the description offers no common variations such as "PHP", "script", "Windmill script", or "main function" to broaden trigger coverage.	2 / 3
Distinctiveness Conflict Risk	"writing PHP scripts" is a somewhat specific niche but, read alone, could still overlap with generic PHP-coding or other scripting skills, since it omits the Windmill context that would set it apart.	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: windmill-labs/windmill
Path: system_prompts/auto-generated/skills/write-script-php/SKILL.md
Commit: 33d2845

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