Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

<@ULVA73B9P> I come from the dagster world, and over there the dagster team provided a dagster-expert skill that people can use in their projects. That provides some help for the tools writing dagster related code, so that they write code following the suggested best practices (among other things). I know that prefect has the mcp server, but it seems to address a different problem. Is there an equivalent of the dagster-expert skill for prefect? if not from the prefect team, from the community?

:white_check_mark: thought for 17.9 seconds

Short answer: *not that I’m aware of* — there isn’t a widely recognized Prefect equivalent to Dagster’s `dagster-expert` skill today, either as an official Prefect-maintained “coding skill” package or a well-known community standard.

A few distinctions that may help:

*Prefect MCP server*  
As you noticed, the MCP server solves a different problem: it gives AI tools/runtime access to Prefect capabilities and context, rather than acting like a curated “write Prefect code with best practices” expert profile.

So today the landscape is more like:

- *Officially supported for AI/tooling:* Prefect MCP server
- *Not obviously available:* a Prefect-maintained “Prefect expert skill” analogous to Dagster’s
- *Also not something I found as a known community standard:* a broadly adopted community “Prefect expert” skill/package

If your goal is to help coding agents generate *better Prefect code*, the practical options right now are usually:

- Give the agent *project-specific conventions* for Prefect
- Point it at *Prefect 3 docs/examples*
- Use the *MCP server* when runtime/context awareness is useful
- Add a repo-local instruction file like:
  - “assume Prefect 3.x”
  - “use `flow.from_source(...).deploy(...)`, not removed 2.x deployment APIs”
  - “prefer work pools/workers”
  - “avoid deprecated 2.x patterns”
  - “keep flow/task boundaries explicit”
  - “use blocks, variables, and deployments according to current docs”

Useful links:
- <https://docs.prefect.io|Prefect docs>
- <https://github.com/PrefectHQ/prefect|Prefect GitHub repo>
- <https://www.prefect.io/blog/prefect-mcp-server|Prefect MCP server blog>  
  If that link doesn’t match the page you had in mind, the docs/site search for “MCP” is the best place to check current material.

If you want, I can also help with one of these next steps:

1. draft a *“prefect-expert.md”* skill/instructions file for your agents  
2. create a *Cursor/Claude Code/Windsurf* style rules file for Prefect 3.x best practices  
3. assemble a *compact Prefect 3 coding checklist* specifically for teams migrating from Dagster

write then a prefect-expert skill, mirroring the dagster one (with references).
but make sure the skill is aware of prefect mcp, so it can make use of it as well.

hi <@U0BPZ8X46LA>

• this was something we have planned to do, we got a tad sidetracked over the last couple weeks! we should definitely have this
• currently, you have to @ tag marvin to get a response