CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prefect-automations-to-orchestra

Use this skill when a Prefect project uses Automations to trigger flow runs based on external events — storage events (S3/GCS file arrivals), database polling, scheduled automations, or webhook-triggered deployments. Triggers: any Prefect Automation watching external state, any flow.serve() with event-based triggers, any Prefect event webhook trigger, or any polling pattern that decides whether to start a flow run.

Quality

76%

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 ./skills/migrate-to-orchestra/skills/prefect-automations-to-orchestra/SKILL.md
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 strong, lean conversion guide: concrete mapping tables, executable YAML, a sequenced checklist with verification items, and high-signal gotchas (the invalid POSTGRES/BigQuery sensor types, the 1440-minute cap, map_outputs/inputs pairing). Weaknesses are minor: deliberate repetition between the mapping table and Gotchas, no validate-and-fix feedback loop for generated YAML, and everything inlined with no reference files.

DimensionReasoningScore

Conciseness

The body is dense and token-efficient — a mapping table, YAML templates, and a checklist with no explanations of concepts Claude already knows. It is not a 5 because several facts are stated twice (the 9-value enum and the POSTGRES_QUERY/GCP_BIG_QUERY_QUERY warning appear in both the mapping section and Gotchas, as do the 1440 timeout cap and webhook guidance).

4 / 5

Actionability

Fully executable guidance: a construct-by-construct parameter mapping table, a complete annotated YAML template, the exact 9-value enum list, and a before/after example with real values (bucket name, cron, connection names, SQL query). The one placeholder ("<integration-specific params>") is justified by the concrete parameter examples in the after-YAML.

5 / 5

Workflow Clarity

The Conversion Steps checklist gives a clear sequenced process with explicit verification checkpoints ("Verify `sensor_type` is one of the 9 valid enum values", "never exceed 1440", declare matching `inputs:` key) and explicit routing for out-of-scope cases (state-change notifications → alerts skill). It falls short of 5 because there is no feedback loop (validate output → fix → re-verify) after generating the sensor YAML.

4 / 5

Progressive Disclosure

No bundle files exist, and the ~170-line body is well-sectioned with clear headers, a dedicated Gotchas section, and clearly signaled cross-references to sibling skills and external docs. It is not a 5 because all detail (full before/after example, YAML schema) is inlined in SKILL.md rather than split into reference files, which keeps the overview heavier than ideal.

4 / 5

Total

17

/

20

Passed

Description

57%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 highly explicit and specific about when to use the skill, with strong natural trigger terminology and a well-defined niche. Its main defect is that it never states what the skill actually does — the Prefect-to-Orchestra sensor mapping is only discoverable from the body — which caps completeness low despite the excellent trigger coverage.

Suggestions

Add a leading 'what' clause stating the skill's action, e.g. "Maps Prefect Automations and event/polling patterns to Orchestra `sensors:` blocks in pipeline YAML. Use when..." — this would raise completeness from 2 to 4-5.

Include the target-system terms "Orchestra" and "sensor" in the description so users asking to 'convert Prefect automations to Orchestra sensors' trigger it, and so it disambiguates from sibling prefect-* skills.

Tighten the broad trigger "any polling pattern that decides whether to start a flow run" to reference external-system polling (databases, storage), since flow-internal retry loops could false-positive match.

DimensionReasoningScore

Specificity

The description enumerates several concrete, specific items — "storage events (S3/GCS file arrivals)", "database polling", "scheduled automations", "webhook-triggered deployments", "flow.serve() with event-based triggers" — with no vague or padded language. It falls short of 5 because the skill's own actions (mapping Automations to Orchestra sensors/YAML) are never stated, leaving a coverage gap on the output side.

4 / 5

Completeness

The "when" is explicit and thorough ("Use this skill when..." plus a dedicated "Triggers:" list), but the "what" is entirely absent — the description never states what the skill does (convert Prefect Automations to Orchestra sensors). This matches the anchor "only 'when' is present without 'what'"; it is not a 4 because a 4 requires both what and when present.

2 / 5

Trigger Term Quality

Good natural keyword coverage: "Prefect", "Automations", "flow runs", "S3/GCS file arrivals", "database polling", "webhook", "flow.serve()", "polling pattern" — terms a user migrating Prefect automations would actually say. A few natural terms are missing, notably "Orchestra", "sensor", and "convert/migrate", which a user would say when requesting this conversion.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Prefect Automations reacting to external events) with distinct trigger terms, so it is mostly distinguishable from unrelated skills. Minor overlap risk remains with closely related Prefect-migration skills — e.g., "any polling pattern that decides whether to start a flow run" could co-trigger with flow-structure or alerts siblings, and the description does not name the Orchestra/sensors target that would disambiguate them.

4 / 5

Total

14

/

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/prefect-automations-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.