CtrlK
BlogDocsLog inGet started
Tessl Logo

resources

MUST use when managing resources.

51

Quality

55%

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

86%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 content is a well-structured, actionable reference with executable examples and a properly guarded destructive command. It is concise without padding and organizes its self-contained material clearly.

DimensionReasoningScore

Conciseness

The body is mostly lean reference material (file format, JSON structures, CLI commands) with no padding about what resources are; minor redundancy across repeated variable-reference examples keeps it just below a 5.

4 / 5

Actionability

Concrete file-pattern conventions, full executable JSON examples, ready-to-run CLI commands (wmill resource list, wmill sync push), and TS/Python code snippets make the guidance copy-paste ready across common cases.

5 / 5

Workflow Clarity

As a reference skill it has clear sections, and the destructive `wmill sync push` command carries an explicit guard ('destructive to remote state, so only run when the user explicitly asks'); minor checkpoint gaps keep it just under a 5.

4 / 5

Progressive Disclosure

No bundle subdirectories exist, so the body is appropriately self-contained with well-organized section headers and a single one-level-deep pointer to AGENTS.wmill.md; navigation is easy.

5 / 5

Total

18

/

20

Passed

Description

25%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 essentially a bare trigger clause with no statement of what the skill does, scoring low across all dimensions. Adding concrete actions (create, edit, deploy, reference credentials) and natural trigger terms would lift every dimension.

Suggestions

State what the skill does, e.g. 'Create, edit, and deploy Windmill resource files ({path}.resource.json) that store credentials and configuration for external services.'

Add natural trigger terms users would say: 'credentials', 'secrets', 'service connections', 'resource types', '.resource.json'.

Keep the explicit 'Use when...' clause but pair it with the 'what' so both halves are present.

DimensionReasoningScore

Specificity

The description names the domain ("resources") but provides no concrete actions — 'MUST use when managing resources' uses only the generic verb 'managing' with no enumerated capabilities.

2 / 5

Completeness

It supplies a 'when' clause ('MUST use when managing resources') but no 'what' — the skill's actual capabilities are never stated, matching the anchor where only 'when' is present without 'what'.

2 / 5

Trigger Term Quality

The sole keyword is 'resources', a generic term; natural phrases a user would actually say (credentials, secrets, connections, service config) are absent.

2 / 5

Distinctiveness Conflict Risk

'resources' is very broad and would overlap with many infrastructure, cloud, and credentials skills, giving it high conflict risk.

2 / 5

Total

8

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
windmill-labs/windmill
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.