diff --git a/examples/slackbot/.claude/skills/prefect-behavior-triage/SKILL.md b/examples/slackbot/.claude/skills/prefect-behavior-triage/SKILL.md new file mode 100644 index 000000000..d7b75a700 --- /dev/null +++ b/examples/slackbot/.claude/skills/prefect-behavior-triage/SKILL.md @@ -0,0 +1,40 @@ +--- +name: prefect-behavior-triage +description: Use when a Prefect question hinges on whether observed behavior is expected, a documentation gap, or a real bug. Inspect docs and source first, then build and run a minimal reproduction only when needed. +--- + +# Prefect Behavior Triage + +Use this skill when a user reports surprising Prefect behavior or asks whether something is a bug. + +## Workflow + +1. Read the relevant docs and implementation before making claims. +2. If docs and source code already answer the question, do not reproduce unnecessarily. +3. If runtime behavior still matters, create the smallest possible reproduction and run it. +4. Compare four things explicitly: + - what the user observed + - what the docs say + - what the source code does + - what the reproduction actually did +5. End with a clear classification: + - expected behavior + - docs unclear or outdated + - likely bug + - still inconclusive + +## Reproduction Rules + +- Prefer tiny standalone scripts over modifying existing project files. +- Write repros under `.research_cache/repros/` and reuse them if they already fit. +- Keep the repro focused on one claim or edge case. +- Use `uv run python