CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tableau-dagster-to-orchestra

Use this skill when the user wants to convert a Dagster Tableau integration — TableauCloudWorkspace, TableauServerWorkspace, load_tableau_asset_specs, or build_tableau_materializable_assets_definition — into an equivalent Orchestra pipeline task targeting Tableau Cloud. Triggers: any mention of migrating or rewriting Dagster Tableau assets to Orchestra; Dagster code importing from dagster_tableau.

Quality

90%

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

82%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 a dense, actionable conversion guide with complete before/after examples, an exact parameter mapping, and genuinely non-obvious gotchas. Its main gaps are a missing end-of-workflow validation step and inline content (the full alerts example) that would be better split into a reference file.

Suggestions

Add an explicit validation step at the end of Conversion Steps, e.g. confirm the case-sensitive workbook display name exists in the Tableau project and run the pipeline once to verify the refresh triggers.

Trim the second on-success alert example (one alert block suffices to show the schema) and condense the auth version requirements into a single compact note.

Move the full alerts YAML schema to a reference file (e.g. references/alerts.md) and keep a one-line pointer inline, mirroring the existing deferral to the slack-dagster-to-orchestra skill.

DimensionReasoningScore

Conciseness

Largely efficient — a one-sentence overview, a dense parameter mapping table, and non-obvious gotchas (PAT single in-flight request, Connected App version floors). Minor trimming opportunities remain: the second on-success alert example, duplicated `condition: null`/`tags: []` boilerplate across two YAML blocks, and inline version/date details ("Tableau Cloud (Dec 2025 release+) or Tableau Server 2025.3+") keep it below anchor 5.

4 / 5

Actionability

Fully executable and copy-paste ready: complete before (runnable Python) and after (full pipeline YAML) examples, exact field names in the mapping table, a concrete UI path ("Settings -> Connections -> Tableau Cloud"), and coverage of both common cases (workbook refresh and datasource refresh via TABLEAU_REFRESH_EXTRACT). Matches anchor 5.

5 / 5

Workflow Clarity

Four clearly sequenced steps (find workspace/assets, create/verify connection, replace asset with task, wire dependencies) with "Create/verify the Orchestra connection" as a checkpoint, but there is no explicit post-conversion validation step (e.g., run the pipeline or confirm the case-sensitive workbook display name) — a minor validation gap consistent with anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Well-organized sections with one-level-deep deferral ("See the `slack-dagster-to-orchestra` skill for full schema details" and external doc links), and no broken references since no bundle files exist. However, the full Adding Alerts section with a complete inline YAML example is content that could live in a reference file, and the skill is over 50 lines, so anchor 4 fits better than 5.

4 / 5

Total

17

/

20

Passed

Description

95%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 strong description: it names the exact Dagster Tableau API surface, states the conversion target precisely, and gives explicit, natural trigger phrases covering convert/migrate/rewrite synonyms. The only nit is that the action set is a single conversion verb applied to enumerated objects rather than multiple distinct actions.

DimensionReasoningScore

Specificity

Names four concrete Dagster API symbols ("TableauCloudWorkspace, TableauServerWorkspace, load_tableau_asset_specs, or build_tableau_materializable_assets_definition") and the exact target ("an equivalent Orchestra pipeline task targeting Tableau Cloud"), but describes a single conversion action rather than the multiple distinct actions of the anchor-5 example.

4 / 5

Completeness

Explicitly answers both: what ("convert a Dagster Tableau integration ... into an equivalent Orchestra pipeline task") and when ("Use this skill when the user wants to convert ..." plus a dedicated "Triggers:" clause with concrete trigger phrases). Matches the anchor-5 example structure.

5 / 5

Trigger Term Quality

Covers the natural phrasings users would say — "migrating or rewriting Dagster Tableau assets to Orchestra", "Dagster code importing from dagster_tableau" — plus the synonym "convert", giving comprehensive coverage including the literal import path. Not 4 because no common variation or synonym is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: dagster_tableau symbols and Orchestra as the named target make it unlikely to fire for any other skill; minimal overlap risk.

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-dagster-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.