CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

resources

MUST use when managing resources.

Quality

54%

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/resources/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 highly actionable — every example is executable and includes rare, valuable specifics like resolver edge cases and destructive-deploy guards — but it is a monolithic single-file reference that buries a resource-type catalog and sequencing rules (variable-before-resource, hub-sync-before-custom-type) in topic sections. Splitting the catalog and per-language usage examples into reference files and adding a short end-to-end creation flow with a verification step would raise both organization scores. Conciseness would also improve by cutting the repetitive type examples down to a pattern plus two or three exemplars.

Suggestions

Move the Common Resource Types catalog and the Using-Resources-in-Scripts examples into a references file (e.g. references/resource-types.md), keeping SKILL.md as an overview with clearly signaled links.

Add a short numbered creation flow with a validation checkpoint (create variable → write resource file → verify with `wmill resource list` or a preview run before any deploy).

Trim the eight resource-type JSON examples to a representative pattern plus 2–3 exemplars, and tighten the wordy "When No Resource Type Fits" prose into terse bullets.

DimensionReasoningScore

Conciseness

The content is Windmill-specific knowledge Claude does not already have, and no generic concepts are explained, but the eight near-identical resource-type JSON examples (~100 lines) and the wordy "When No Resource Type Fits" prose could be tightened. This matches "mostly efficient but includes some unnecessary explanation or could be tightened" — not a 2 because nothing explains known concepts, not a 4 because the type catalog is substantial repetition.

3 / 5

Actionability

Guidance is fully executable and copy-paste ready: exact JSON structures, the file naming pattern `{path}.resource.json`, concrete CLI commands (`wmill resource list`, `wmill sync push`), explicit wrong-vs-right run-argument examples, and precise edge cases ("nested at most two levels deep... at most 1000 items") covering the common cases. This matches the top anchor exactly.

5 / 5

Workflow Clarity

Sequencing guidance exists (create the variable before the resource, sync the hub before proposing a custom type, deploy "only when the user explicitly asks") but it is scattered across topic sections rather than presented as a flow, and there is no validation checkpoint after creating or deploying a resource (e.g., verifying via `wmill resource list`). This matches "steps listed but validation gaps; sequence present but checkpoints missing or implicit" — not a 4 because the gaps are more than minor.

3 / 5

Progressive Disclosure

The 305-line single file is well-sectioned with headers, but there are no bundle files at all — the ~100-line common-resource-types catalog and the script-usage examples are inline content that belongs in a separate reference file, so SKILL.md is a monolith rather than an overview. This matches "some structure but could be better organized; content that should be separate is inline" — not a 4 because the inlining is substantial, not a minor gap.

3 / 5

Total

14

/

20

Passed

Description

20%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 invoke the skill but never says what the skill does, and "resources" is too generic to serve as a distinguishing trigger. It would both under-inform Claude about its purpose and collide with unrelated skills. Rewriting it to name Windmill resources, list concrete actions (create/deploy resources, define custom types, reference variables), and give natural trigger phrases would fix nearly every dimension.

Suggestions

State what the skill does in third person, e.g. "Creates, deploys, and references Windmill resources (credentials/config for external services), including custom resource types and variable secret references."

Add a "Use when..." clause with natural trigger terms: "Use when the user mentions Windmill resources, credentials for external services, resource types, or $res:/"$var: references."

Include concrete trigger keywords and synonyms (resource, resource type, credential, connection, secret variable) so the skill is distinguishable from generic 'resources' skills.

DimensionReasoningScore

Specificity

The description "MUST use when managing resources." contains no concrete actions and no domain specifics; "resources" is pure abstract language with no stated capability, matching the entirely-vague anchor even more closely than "Processes PDF files" does.

1 / 5

Completeness

Only a "when" is present ("when managing resources") with no "what" whatsoever — the skill's purpose is never stated, exactly parallel to the anchor example "Use when working with documents". It cannot be a 3 because a clear "what" is required.

2 / 5

Trigger Term Quality

The only keywords are the generic "managing" and "resources" — one or two generic terms with no natural phrases or synonyms a user would actually say, matching "Works with files". It is not a 3 because no relevant domain keywords or variations are present.

2 / 5

Distinctiveness Conflict Risk

"Resources" is very broad and would overlap with many unrelated skills (cloud infrastructure, memory, HR, generic file resources), matching "very broad; high overlap risk with many similar skills". It is not a 1 because the term still narrows to a recognizable domain.

2 / 5

Total

7

/

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/resources/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.