airbyte-cloud-prefect-to-orchestra

Use this skill when the user wants to convert a Prefect task that syncs Airbyte Cloud — AirbyteConnection block, trigger_sync_run_and_wait_for_completion, or AirbyteSyncResult — into an equivalent Orchestra pipeline task targeting Airbyte Cloud. Triggers: any mention of migrating or rewriting Prefect Airbyte tasks to Orchestra; any Prefect flow code importing from prefect_airbyte pointed at Airbyte Cloud.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

90%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 tight, actionable conversion skill with executable examples, a parameter map, and a sequenced checklist. The only meaningful gap is the absence of an explicit validation step on the generated YAML.

Suggestions

Add a final checklist item instructing Claude to validate the generated Orchestra YAML against the documented schema before returning it to the user.

Cross-link the airbyte-server-prefect-to-orchestra skill as a reference path so operators can navigate between the two variants.

Dimension	Reasoning	Score
Conciseness	Lean, table-driven mapping with terse gotchas and no padding; assumes Claude's competence and every aside ('Copy verbatim — UUID string') earns its place.	5 / 5
Actionability	Provides a complete executable before/after pair (Prefect Python + Orchestra YAML), a parameter-mapping table, and a checklist covering sync and reset; copy-paste ready.	5 / 5
Workflow Clarity	The Conversion Steps checklist gives a clear, ordered sequence and the Gotchas flag a validation failure mode, but there is no explicit 'validate the generated YAML' checkpoint before handoff.	4 / 5
Progressive Disclosure	Well-organized sections under ~100 lines with clearly signaled one-level references (external doc links and sibling-skill pointers); no bundle files are present, so structure carries the score.	4 / 5
	Total	18 / 20 Passed

Description

87%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 well-crafted description with an explicit use-when clause, concrete construct names, and natural trigger terms that cleanly distinguish Airbyte Cloud from Airbyte Server. Minor coverage of the reset job type is the only gap.

Suggestions

Mention the reset_cache=True → reset job_type mapping in the description so the reset variant is discoverable alongside sync.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete constructs ('AirbyteConnection block', 'trigger_sync_run_and_wait_for_completion', 'AirbyteSyncResult') and the outcome ('equivalent Orchestra pipeline task'), with only minor coverage gaps (reset not mentioned in the description).	4 / 5
Completeness	Explicit 'Use this skill when...' clause plus a dedicated 'Triggers:' section clearly and concretely answer both what the skill does and when to invoke it.	5 / 5
Trigger Term Quality	Includes natural trigger phrasing ('migrating or rewriting Prefect Airbyte tasks to Orchestra', 'Prefect flow code importing from prefect_airbyte pointed at Airbyte Cloud') with good keyword coverage, though a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	A sharply defined niche (Prefect Airbyte Cloud at api.airbyte.com) that actively steers away from the sibling airbyte-server skill, giving minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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/airbyte-cloud-prefect-to-orchestra/SKILL.md
Commit: 3a29fe4

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.