CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-php

MUST use when writing PHP scripts.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%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 delivers concrete, executable guidance for writing Windmill PHP scripts, with sensible workflow decision rules and validation checkpoints around metadata regeneration and deployment. Its main weaknesses are repetition of the deploy/metadata caveats across multiple sections, off-scope non-PHP content inlined into a PHP skill, and no progressive disclosure into reference files.

Suggestions

Consolidate the deploy/preview/'not a deploy' caveats into a single section to remove the triple repetition across 'CLI Commands', 'Preview vs run', and 'After writing'.

Move the general Windmill guidance (metadata-sync deep dive, preprocessor scripts, multi-language principles) into reference files or a shared parent skill, keeping only PHP-specific guidance in SKILL.md.

Add one complete end-to-end PHP example that combines the '// require:' dependency block, a resource class, and a main function that actually uses the resource connection.

DimensionReasoningScore

Conciseness

The body is information-dense with no filler explaining concepts Claude already knows, but it could be tightened: the 'not a deploy' caveat and deploy-only-when-asked rule are each repeated across three sections ('CLI Commands', 'Preview vs run', 'After writing'), and non-PHP material (preprocessor scripts 'written in TypeScript or Python', multi-language placeholder syntax like '$1 for PostgreSQL, ? for MySQL') pads a PHP-specific skill. Not 2 because nearly every sentence carries Windmill-specific operational signal; not 4 because the repetition and off-scope sections are more than minor.

3 / 5

Actionability

Concrete commands ('wmill script preview <script_path>', 'wmill generate-metadata --dry-run', 'wmill resource-type list --schema') and copy-paste-ready PHP snippets for the main function, the class_exists resource-type pattern, and '// require:' dependency comments cover the common cases. Not 5 because no combined end-to-end example is shown and resource usage inside main stops at the comment '// $db contains the database connection details' without showing how the connection is actually used.

4 / 5

Workflow Clarity

Clear decision rules sequence the post-writing flow (preview vs run vs sync push chosen by intent) and the post-edit flow (edit → 'wmill generate-metadata' scoped to what changed → diff regenerated .lock files → report version changes), with explicit checkpoints: '--dry-run' to check scope before regenerating and a gated deploy ('Only suggest/run a deploy when the user explicitly asks'). Not 5 because there is no consolidated end-to-end sequence and the PHP authoring sections (Structure, Resource Types, Library Dependencies) are reference-style rather than ordered steps.

4 / 5

Progressive Disclosure

Headers and sub-sections organize the single ~130-line file reasonably well, but everything is inlined with no reference files at all — the deep metadata-sync detail (hash drift, rehash, dry-run, import propagation) and general Windmill material (preprocessors, multi-language principles) could live in separate reference files or a shared skill. Not 2 because the structure is more than minimal and the file is navigable; not 4 because the general-vs-PHP content mixing and absence of any reference split are real organization gaps.

3 / 5

Total

14

/

20

Passed

Description

40%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 bare trigger clause: it states when to use the skill in natural language but says nothing about what the skill does. Its one strength is a clean, specific, low-conflict trigger ('writing PHP scripts'); its weakness is the missing capability statement and near-total absence of keyword variations.

Suggestions

Add a 'what' clause naming the skill's capabilities, e.g. 'Write Windmill PHP scripts: main-function structure, resource-typed parameters, and dependency comments. MUST use when writing PHP scripts for Windmill.'

Include trigger variations users might naturally say — 'PHP', '.php', 'Windmill script', 'automation script' — so the description matches more than one phrasing.

Scope the trigger to Windmill explicitly to reduce misfires on general, non-Windmill PHP coding requests.

DimensionReasoningScore

Specificity

The description names the domain ("writing PHP scripts") but lists no capabilities or actions whatsoever — no 'creates', 'structures', or any verb describing what the skill does. It is above anchor 1 (the domain is concrete, not pure abstraction like 'Helps with documents') but below anchor 3, which requires 1-2 concrete actions.

2 / 5

Completeness

Only the 'when' is present ("MUST use when writing PHP scripts"); there is no statement of what the skill actually does, matching the anchor-2 pattern 'Use when working with documents' ('when' present without 'what'). Not 3, because a clear 'what' is entirely absent; not 1, because the 'when' clause is present and specific rather than both being vague.

2 / 5

Trigger Term Quality

"writing PHP scripts" is exactly the phrase a user would naturally say, but it is the only keyword phrase present — no synonyms or related terms (Windmill, automation, .php) — matching the anchor-3 example 'Works with PDF files' (relevant keyword, missing variations). Not 4, which expects broader keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"PHP scripts" carves a specific niche that is clearly distinguishable from sibling language skills and unlikely to trigger for the wrong skill. Not 5 because the trigger could fire for ordinary (non-Windmill) PHP coding requests — minor overlap with generic PHP assistance; not 3 because PHP is far more specific than 'somewhat specific'.

4 / 5

Total

11

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.