CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tableau-prefect-to-orchestra

Use this skill when the user wants to convert a Prefect @task that refreshes a Tableau workbook or extract — using tableau-server-client (TSC) library, RefreshWorkbookRequest, or ScheduleItem — into an equivalent Orchestra pipeline task targeting Tableau Cloud. Triggers: any mention of migrating Tableau refresh Prefect tasks to Orchestra; Prefect flow code importing tableau_server_client and calling rest_api.workbooks.refresh.

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

A highly actionable, well-structured conversion guide whose mapping table, complete YAML templates, and gotchas give Claude everything needed to execute. Its main weaknesses are a missing validation checkpoint before the destructive deletion of the Prefect code, and minor redundancy (duplicated alert pointer, overlapping YAML examples, version-dated details).

Suggestions

Add a verification step before deletion in Conversion Steps: e.g., "Trigger the Orchestra task once and confirm the refresh starts/completes successfully; only then delete the Prefect @task and TSC imports."

Remove the duplicated "See prefect-alerts-to-orchestra for all notification patterns" line — keep either the References entry or the Adding Alerts section, not both.

Trim the standalone Orchestra YAML Structure examples (the Before/After section already contains a complete task YAML) or drop the after-example and keep only the template, and move version-specific details (Dec 2025 release, Tableau Server 2025.3+) into a dedicated compatibility note.

DimensionReasoningScore

Conciseness

The parameter-mapping table and Gotchas are dense and every bullet earns its place, but "See `prefect-alerts-to-orchestra` for all notification patterns." appears twice (References and Adding Alerts), the two standalone YAML blocks partially duplicate the Before/After example, and version-dated details ("Dec 2025 release+", "Tableau Server 2025.3+") sit outside any old-patterns/deprecated section. Efficient overall with minor trimmable redundancy, so above anchor 3 but below the lean anchor 5.

4 / 5

Actionability

Fully executable guidance: copy-paste-ready YAML for both the workbook and datasource cases, exact Orchestra field names, a precise conversion rule ("retry_delay is integer MINUTES (not seconds); convert Prefect's retry_delay_seconds by dividing by 60, cap at 120"), and a complete runnable Python before-example. The common cases are covered concretely, matching the anchor-5 standard.

5 / 5

Workflow Clarity

The Conversion Steps checklist is clearly sequenced, but it ends with the destructive step "Delete the Prefect `@task` function and any TSC imports no longer needed" with no verification checkpoint (e.g., confirm the Orchestra task triggers a successful refresh before deleting the source code). Per the rubric, a workflow involving destructive changes without validation is capped at 3, taking precedence over the otherwise clear sequence.

3 / 5

Progressive Disclosure

Well-organized sections (Overview, Parameter Mapping, YAML Structure, Conversion Steps, Before/After, Gotchas) with clearly signaled one-level-deep references (two documentation URLs and one sibling skill), no nesting. Minor gaps keep it below anchor 5: the two-line "Adding Alerts" stub duplicates the References line, and the 120+ line body is entirely inline with no split despite being over the simple-skill size.

4 / 5

Total

16

/

20

Passed

Description

92%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.

A highly specific, well-triggered description that explicitly states both what the skill does and when to use it, with concrete code-level triggers. Its only weakness is slightly less than exhaustive synonym coverage in the trigger terms, and it names constructs (RefreshWorkbookRequest, ScheduleItem) that the body never actually addresses.

DimensionReasoningScore

Specificity

"convert a Prefect @task that refreshes a Tableau workbook or extract ... into an equivalent Orchestra pipeline task targeting Tableau Cloud" names the exact source constructs (tableau-server-client, RefreshWorkbookRequest, TSC) and the exact target, comprehensively covering the skill's niche with no vague language. It exceeds anchor 4 because the conversion capability is fully characterized rather than listed with gaps.

5 / 5

Completeness

Both questions are explicitly answered: the what ("convert a Prefect @task that refreshes a Tableau workbook or extract ... into an equivalent Orchestra pipeline task") and the when ("Use this skill when the user wants to..." plus a dedicated "Triggers:" clause with concrete phrases). This matches the anchor-5 example pattern of what + explicit when with concrete triggers.

5 / 5

Trigger Term Quality

"Triggers: any mention of migrating Tableau refresh Prefect tasks to Orchestra; Prefect flow code importing tableau_server_client and calling rest_api.workbooks.refresh" gives good natural-term coverage (migrating, refresh, Prefect, Orchestra) plus a code-level trigger. It falls short of anchor 5 because a few natural variations users might say (e.g. "datasource", "port/move to Orchestra") are not covered.

4 / 5

Distinctiveness Conflict Risk

The Prefect-TSC-to-Orchestra Tableau refresh niche is extremely specific ("tableau-server-client", "rest_api.workbooks.refresh", "Orchestra pipeline task"), with distinct triggers and minimal overlap risk against any sibling skill. It is clearly a distinct niche rather than merely "mostly distinct" as at anchor 4.

5 / 5

Total

19

/

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

orchestra-hq/orchestra-skills

Path

skills/migrate-to-orchestra/skills/tableau-prefect-to-orchestra/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.