CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prefect-alerts-to-orchestra

Use this skill when a Prefect project sends notifications: @flow(on_failure=...) or @flow(on_completion=...) hooks, Prefect Automation notification actions (Slack, email, Teams, PagerDuty), SlackWebhook block notifications, or MicrosoftTeamsWebhook block notifications. Covers all six Orchestra alert destination types: SLACK, EMAIL, PAGER_DUTY, MICROSOFT_TEAMS, WEBHOOK, and DATADOG. Read alongside prefect-automations-to-orchestra for complete notification coverage.

Quality

80%

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-alerts-to-orchestra/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 reference whose exact field mappings, enums, and complete before/after example make it immediately usable for Prefect-to-Orchestra alert migration. The main cost is redundancy: the destination-field rules, 5-digit suffix, on_crashed mapping, and message-length limit are each stated three or more times across the table, destination rules, checklist, and Gotchas, and the workflow lacks a final output-validation step.

Suggestions

Deduplicate the rules stated 3-4 times (destination vs connection_id fields, 5-digit connection suffix, on_crashed→FAILED, ~200-char custom_message): state each once in the Parameter Mapping / Destination rules sections and trim the Gotchas bullets that repeat them verbatim.

Add a final validation step to the Conversion Steps checklist, e.g. 'Validate the generated YAML against the Orchestra pipeline schema (see References) before delivering', to close the workflow-clarity gap.

Consider moving the Before/After example or the per-integration destination details into a references/ file linked one level deep, keeping SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

The core content is dense, domain-specific reference material with nothing Claude already knows, but the same rules are repeated three to four times: the SLACK/EMAIL→destination vs connection_id rule appears in "Destination rules", the YAML comments ("required for SLACK and EMAIL only"), and Gotchas ("SLACK and EMAIL require `destination` field; ... require `connection_id`"); the 5-digit suffix rule, the on_crashed→FAILED mapping, and the ~200-char custom_message limit each appear in the table, checklist, and Gotchas. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than 4, because the duplication exceeds minor instances — the Gotchas section largely restates earlier sections.

3 / 5

Actionability

Fully executable and copy-paste ready: an exact field-level YAML schema ("integration: SLACK", "destination: '#channel'", "connection_id: pagerduty_prod_12345"), the complete valid statuses enum ("FAILED, SUCCEEDED, CANCELLED, WARNING, SKIPPED"), and a complete before/after pair — real Python decorators with SlackWebhook.load(...).notify(...) and MicrosoftTeamsWebhook calls mapping to complete Orchestra YAML — covering flow-level, task-level, and three integrations. This matches anchor 5 ('specific examples cover the common cases').

5 / 5

Workflow Clarity

The "Conversion Steps" checklist gives a clear sequence (find flow hooks → find task hooks → find Automations → find .notify() calls → map each → enforce constraints) with checkpoint items such as "Ensure `connection_id` values include the 5-digit Orchestra suffix" and "Ensure all alert names are unique within their scope". It is anchor 4 rather than 5 because there is no final validation step (e.g., validating the generated YAML against the Orchestra pipeline schema); it is not capped at 3 since this is a generation/migration task, not a destructive or batch operation.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, and assets/ are absent), so everything is inline in a single ~180-line file. Sections are well-organized (Overview → Parameter Mapping → YAML Structure → Conversion Steps → Before/After → Gotchas → References) and the external links are clearly signaled, but the file exceeds the under-50-line simple-skill case and the mapping table plus full example bulk could plausibly live in a reference file — anchor 4 ('good structure; most content appropriately placed; minor organization gaps') rather than 5.

4 / 5

Total

16

/

20

Passed

Description

75%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-targeted description with explicit, specific trigger guidance and near-complete keyword coverage for the Prefect-to-Orchestra notification domain. Its main weakness is that the core action — converting Prefect notifications to Orchestra's alerts block — is implied rather than explicitly stated, and @task-level triggers are omitted even though the skill body covers them.

Suggestions

State the action explicitly, e.g. 'Converts Prefect notifications (@flow/@task hooks, Automation notification actions, and block .notify() calls) into Orchestra's alerts block' — this would strengthen both completeness and specificity.

Add @task(on_failure=...) hooks and the standalone term 'alerts' to the trigger list, since users migrating task-level notifications would naturally mention those.

DimensionReasoningScore

Specificity

Lists several specific constructs — "@flow(on_failure=...) or @flow(on_completion=...) hooks, Prefect Automation notification actions (Slack, email, Teams, PagerDuty), SlackWebhook block notifications, or MicrosoftTeamsWebhook block notifications" and "Covers all six Orchestra alert destination types: SLACK, EMAIL, PAGER_DUTY, MICROSOFT_TEAMS, WEBHOOK, and DATADOG". It falls short of anchor 5 because the action the skill performs is never explicitly stated (no verb like 'converts/migrates Prefect notifications to Orchestra alerts'), only implied by the coverage sentence.

4 / 5

Completeness

The 'when' is explicit and detailed ("Use this skill when a Prefect project sends notifications: ...") and a 'what' is present via "Covers all six Orchestra alert destination types", so both exist. It is below anchor 5 because the core action is not explicitly stated — scoring only what is written, 'covers destination types' is a scope claim, not an action; it is above anchor 3 because the when-clause is fully explicit rather than weakly implied.

4 / 5

Trigger Term Quality

Strong natural keyword coverage — "notifications", "on_failure", "on_completion", "Slack", "email", "Teams", "PagerDuty", "SlackWebhook", "MicrosoftTeamsWebhook" are exactly the terms a user with this code would say. Not anchor 5 because a few natural terms are missing: @task(on_failure=...) hooks (which the body handles) and the standalone terms "alerts"/"alerting".

4 / 5

Distinctiveness Conflict Risk

Clear niche (Prefect notification constructs → Orchestra alerts) with distinct, concrete triggers, but "Prefect Automation notification actions (Slack, email, Teams, PagerDuty)" and "Read alongside prefect-automations-to-orchestra for complete notification coverage" create minor overlap with that closely related companion skill — matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills') rather than anchor 5's minimal conflict risk.

4 / 5

Total

16

/

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