CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

raw-app

MUST use when creating raw apps.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./system_prompts/auto-generated/skills/raw-app/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 an exceptionally actionable, well-validated guide to building Windmill raw apps, with copy-paste commands, executable code, guarded destructive operations, and rare insider gotchas (non-TTY wizard hangs, draft-vs-deployed runnables, unmounted-entrypoint blank screens). Its weaknesses are structural: two full guides are concatenated into one ~590-line file with duplicated setup, metadata, and roles content, and no reference files despite explicitly describing a companion guide. Splitting the authoring material into a reference file and deduplicating would raise both conciseness and progressive disclosure.

Suggestions

Split the inlined companion guide (everything from the second "# Windmill Raw Apps" heading onward) into a references/ file (e.g. references/authoring.md) and keep SKILL.md as the CLI-workflow overview that links to it one level deep, as line 8 already implies the structure should be.

Deduplicate the repeated guidance: the "Data setup" questioning rules, the `wmill generate-metadata` workflow, and the `data.roles` semantics each appear in both halves — state each once and cross-reference it.

Isolate version-sensitive specifics (React 19 / React 18 / Svelte 5 defaults, Tailwind CSS v4 directives) in one place so future version churn doesn't scatter edits across the whole document.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and is dense with domain-specific value, but it duplicates material across its two concatenated halves: "Data setup" guidance appears both in "Settle the setup" and again in the second document's "Data setup" section, the `wmill generate-metadata` workflow is explained twice, and the `data.roles` semantics appear in both the CLI and authoring halves. Anchor 3 ("mostly efficient but could be tightened") fits; not 4 because the duplication is wholesale rather than minor.

3 / 5

Actionability

Fully executable throughout: exact commands with flags (`wmill app new --summary ... --framework react19 --datatable main --schema app1`), runnable TypeScript/Python/YAML/SQL examples, a precise bindings table (`backend.<key>(args)`, `backendAsync`, `waitJob`, `getJob`, `streamJob`), and copy-paste entrypoint snippets. This matches anchor 5 ("copy-paste ready code or commands; specific examples cover the common cases").

5 / 5

Workflow Clarity

App creation is explicitly sequenced (Step 1 settle setup → Step 2 run the command → Step 3 offer preview) with an anti-patterns list, the migration workflow ends with the required follow-up ("add them to data.tables"), and validation checkpoints are explicit: run `wmill app lint` after edits, check the regenerated `.lock` diff and report dependency changes, and confirm before `--overwrite`. Destructive operations are guarded, so the missing-validation cap does not apply; this matches anchor 5.

5 / 5

Progressive Disclosure

The body announces "the companion authoring guide" (line 8) — which turns out to be inlined in full as a second "# Windmill Raw Apps" H1 starting at line 250, so two complete documents share one SKILL.md with no references/ bundle at all. Section headers are good, but ~340 lines that clearly belong in a separate reference file are inlined; anchor 3 ("content that should be separate is inline") fits, and it is not 4 because the split is over half the file, not a minor gap.

3 / 5

Total

16

/

20

Passed

Description

35%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 provides a clear trigger but says nothing about what the skill actually does, making it nearly useless for capability discovery. It is short, in third person, and reasonably distinctive thanks to the term "raw apps", but lacks any stated actions, synonyms, or the Windmill context. It resembles the bad example "Use when working with documents" more than any good example.

Suggestions

State what the skill does before the trigger, e.g. "Scaffold and develop Windmill raw apps: create apps via the wmill CLI, configure backend runnables and data tables, and wire React/Svelte frontends to them. Use when creating or editing raw apps, custom Windmill frontends, or app backends."

Add natural trigger variations and the platform name so users and Claude can find it: "Windmill", "raw app", "custom frontend", "app backend runnables", "data tables".

Keep the 'MUST use when' trigger but pair it with a concrete capability list (scaffolding, datatable config, SQL migrations, runnable bindings) so the 'what' is explicit, not inferred.

DimensionReasoningScore

Specificity

The description reads only "MUST use when creating raw apps" — it names no action or capability whatsoever; "creating raw apps" is a trigger, not a described function. This matches anchor 1 ("no concrete actions") rather than 2, which requires naming a domain with at least minimal actions.

1 / 5

Completeness

Only a "when" is present ("when creating raw apps") with no "what" — the skill's actual function is never stated. This matches anchor 2 ("only 'when' is present without 'what'", e.g. "Use when working with documents"); anchor 3 requires a clear 'what', which is absent.

2 / 5

Trigger Term Quality

"creating raw apps" is a phrase a user would plausibly say, but there are no variations or synonyms — no "Windmill", "custom frontend", "React/Svelte app", or "dashboard". Anchor 3 ("some relevant keywords but missing common variations") fits; not 4 because a user asking to build a Windmill frontend or custom app would not hit these terms.

3 / 5

Distinctiveness Conflict Risk

"raw apps" is a fairly distinctive term, giving it a mostly distinct niche with minor overlap risk against closely related app-creation or frontend skills — anchor 4. Not 5, because the niche is never named ("Windmill raw apps" would make it unambiguous) and a generic app-building request could still match.

4 / 5

Total

10

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (598 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

windmill-labs/windmill

Path

system_prompts/auto-generated/skills/raw-app/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.