CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-bigquery

MUST use when writing BigQuery queries.

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-bigquery/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 genuinely useful, platform-specific Windmill/BigQuery guidance with concrete commands and executable SQL examples, and the preview/deploy workflow is clearly gated. Its main weaknesses are inlined general-guide content that belongs in a shared reference, repeated deploy warnings, off-scope multi-language details, and dangling references to sections that are not part of this skill.

Suggestions

Move the general "Windmill Script Writing Guide" (preprocessor scripts, resource types, return values, `main` naming) into a shared reference file (e.g. references/windmill-guide.md) and link to it, keeping this SKILL.md focused on BigQuery specifics.

Fix the dangling "the language section" references (lines 55, 60, 73) — those sections do not exist in this file; either inline the BigQuery-relevant details or link to a real file in the bundle.

Trim the repeated deploy-only-on-explicit-request warnings (stated at lines 15, 26-27, and 45) to a single authoritative statement, and drop the PostgreSQL/MySQL/Snowflake/MSSQL/Bash/PowerShell placeholder-syntax list (line 43), which is out of scope for a BigQuery skill.

DimensionReasoningScore

Conciseness

Most content is non-obvious Windmill platform knowledge Claude cannot be assumed to know, but it could be tightened: the deploy-only-on-explicit-request rule is repeated three times ("Only suggest/run a deploy when the user explicitly asks to deploy/publish/push", "Only use `sync push` when: The user explicitly asks to deploy", "do it only when the user explicitly asks to deploy/publish/push"), sentences are long and multi-clause, and the placeholder-syntax list for PostgreSQL, MySQL, Snowflake, MSSQL, Bash and PowerShell is irrelevant to a BigQuery skill. This fits anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than 2, since there is little generic padding.

3 / 5

Actionability

Guidance is mostly executable: concrete commands (`wmill script preview <script_path>`, `wmill generate-metadata --dry-run`, `wmill generate-metadata rehash`) and copy-paste SQL examples for @name parameters, S3Object consumption with JSON_EXTRACT_ARRAY, and the `-- s3 prefix=... format=parquet` directive. It falls short of anchor 5 because some guidance defers to sections that do not exist in this file — "the language section below shows how that language declares parameters" and "the language section gives its type" — leaving those steps underspecified.

4 / 5

Workflow Clarity

The write → preview → generate-metadata → deploy-only-on-request sequence is clear, with explicit decision gates ("If the user says 'run the script'... use `script preview`", "Only use `sync push` when...") and a checking step (`--dry-run` to inspect stale items before regenerating). Preview-before-deploy acts as a validation checkpoint for the state-mutating deploy. It is not anchor 5 because there is no explicit error-recovery loop (what to do when a preview fails) or validation of the produced script's results.

4 / 5

Progressive Disclosure

No bundle files (references/, scripts/, assets/) exist, and the ~115-line body inlines the entire general "Windmill Script Writing Guide" (preprocessors, resource types, return values, main naming) — content that belongs in a shared reference file for a per-language skill like this. Navigation also dangles: references to "the language section" and to `AGENTS.wmill.md`'s "Deploying" section point to material not present in this skill's bundle. This matches anchor 3 ('some structure but could be better organized; content that should be separate is inline').

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 tells Claude when to activate but not what the skill does. The named domain is specific (BigQuery), but the absence of any capability statement leaves the description uninformative and prone to overlap with generic BigQuery/SQL helpers.

Suggestions

State what the skill does, e.g. "Writes BigQuery scripts for Windmill: declares @name parameters, accepts S3Object inputs, streams large results to S3. Use when writing or running BigQuery queries or Windmill BigQuery scripts."

Add natural trigger synonyms users would actually say — "BigQuery SQL", "BigQuery script", "query BigQuery" — so the skill fires on phrasing variations beyond the exact word "BigQuery queries".

DimensionReasoningScore

Specificity

The description is only "MUST use when writing BigQuery queries" — it names a concrete domain (BigQuery queries) but states no capability or action whatsoever; there is no verb describing what the skill does. This matches anchor 2 ('Names the domain but actions are minimal or generic') better than anchor 1, since it is not vague or abstract — a specific domain is named.

2 / 5

Completeness

The description has an explicit 'when' ("MUST use when writing BigQuery queries") but no 'what' — the skill's actual function (writing Windmill BigQuery scripts, declaring @name parameters, streaming results) is never stated. Anchor 2 explicitly covers 'only when is present without what'; this is not anchor 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

"BigQuery queries" is a natural phrase a user would say, but the description misses common variations and synonyms such as "BigQuery SQL", "Standard SQL", "query", or "dataset". This fits anchor 3 ('Some relevant keywords but missing common variations or synonyms') and falls short of anchor 4's broader keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"BigQuery" is a clear, specific niche with distinct triggers and minimal conflict risk with unrelated skills. It stops short of anchor 5 because a generic SQL or BigQuery-helper skill could still claim the same trigger — nothing in the description differentiates this skill's Windmill-script purpose from those.

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