Skip to main content
A skill teaches a workflow: when to look up information, which tool to use, what to confirm and what to do next. The tools perform the operations; the skill explains how they fit together. Teach the task, not a fixed dialogue. Someone may give all the details at once, add a correction or ask a question halfway through. A useful skill explains what must be known before an action and when to ask, without making the person work through a form one message at a time. Skills live in agent/skills/<name>/SKILL.md. Flow uses the same source files in your messaging agent, standalone MCP server and generated plugin packages.

Write a skill

After adding the get_hours tool in Write a tool, create agent/skills/opening-hours/SKILL.md:
agent/skills/opening-hours/SKILL.md
The description is how an agent discovers the skill. Make it specific enough that the agent can decide to load it without reading the whole file.

Where the skill goes

createAgent({ dir }) reads AGENTS.md and skills/ from the agent folder. The model sees skill descriptions and loads the full instructions when needed.Set inlineSkills: true to include every skill in the prompt instead of loading them on demand.

Keep instructions portable

Write about your product’s workflow and name its tools. Platform formatting and send tools are already handled by Flow for messaging.
A skill shipped through MCP or a plugin must use tools that endpoint actually exposes. flow check reports references to chat-only tools; plugin generation refuses them.

Check it worked

Restart the MCP server or messaging agent, then ask “When do you open?” In the playground, turn on Debug and look for the skill load and get_hours call. A model may skip a skill it already has enough information to answer without; the important result is that the hours come from the tool. For a plugin, regenerate the output and run:
Terminal

Agent instructions and coding-agent skills

These files have different readers: flow new installs the coding-agent skills for you. Edit the files in agent/ to change how your product behaves, rather than the framework skills that explain how to build it.

Try your workflow in the playground

Switch people and channels, inspect tool calls and test sign-in.