> ## Documentation Index > Fetch the complete documentation index at: https://docs.flowglad.com/llms.txt > Use this file to discover all available pages before exploring further. # Skills > Create reusable instructions for chats and automations Skills are reusable packages of instructions and optional supporting files. They let your team define a repeatable way to complete a task once, then apply it consistently across Flowglad. Each Skill has a name, a slash-command slug, a description, and instructions written in Markdown. Supporting files can provide additional context or resources needed to follow those instructions. ## Use Flowglad as your team's Skill library Flowglad keeps each Skill as a versioned package. Publishing a change creates a new revision instead of replacing the previous package in place. Organization admins can open a Skill's **History** to inspect its revisions, compare changes, restore an earlier revision, or discard a draft when those actions are available. This gives your team one governed place to maintain reusable instructions while preserving which version was active at a given time. Draft and rejected revisions do not replace the active version. ### Manage Skills through MCP After you connect the Flowglad MCP server, an agent can inspect and manage your organization's Skill library for you: * `skills.list` returns the Skills visible to the connection. * `skills.get` returns the latest and active revision metadata for one Skill. * `skills.create` submits a new Skill package. * `skills.create_candidate` submits a new revision of an existing Skill. * `skills.publish_revision` verifies and publishes a deferred revision. Creating or updating Skills requires the `skills:write` permission on both the teammate's organization membership and the MCP connection's grant. If you add the permission after connecting the server, reconnect Flowglad MCP and authorize `skills:write` so the write tools become available. **Permissions:** Admins have Skill authoring access by default. To give a Contributor the same access, open **Settings** → **Team**, select the teammate, and enable **Skill Authoring**. This grants permission to create and update organization Skills without making the teammate an admin. ## Load Flowglad MCP Skills into your agent The Flowglad MCP server advertises `io.modelcontextprotocol/skills` during MCP initialization. This tells compatible clients that the server implements the agent Skill methods `skills/list` and `skills/get`. Each returned Skill includes `skill://` resource URIs and content digests; clients can retrieve the files with `resources/read`. Connecting the server does not guarantee that a client will call `skills/list` or install the returned packages. Client support varies. Add a startup instruction to ChatGPT / Codex or Claude when you want the agent to refresh the Flowglad registry at the beginning of each session. **MCP naming:** The names are intentionally different. `skills.list` with a dot is a Flowglad tool for your organization's versioned Skill records. `skills/list` with a slash is an MCP protocol extension method for discovering agent-facing Skill packages. ### Add the startup instruction Create the destination directory once before starting a new session, then add the matching instruction block below. #### ChatGPT / Codex Create the ChatGPT / Codex destination directory with `mkdir -p ~/.agents/skills`. Put the following block in `~/.codex/AGENTS.md` to apply it to every project, or in a repository's `AGENTS.md` to share it with that repository's team. ```markdown AGENTS.md theme={null} ## Flowglad MCP Skill bootstrap At the start of every new session, before handling the first task: 1. Confirm that the Flowglad MCP server is connected. 2. Refresh the agent Skill catalog from Flowglad. Prefer the advertised `skills/list` MCP extension method. If the client does not expose that method directly, use the Flowglad server's `resources/list` method and select resources whose URIs begin with `skill://flowglad/`. 3. For every returned Skill, retrieve its manifest with `skills/get` when available, then read each listed resource with `resources/read`, beginning with `SKILL.md`. 4. Synchronize the package into `~/.agents/skills//`. Compare the returned content digests and rewrite only new or changed Flowglad-managed files. Never overwrite or delete unrelated local Skills. 5. Treat the refreshed Flowglad package as the source of truth for this session. Make the synchronized Skills available for automatic matching and explicit `$skill-name` invocation. 6. If this ChatGPT / Codex client cannot call the Skill or resource methods, report that limitation once and continue without claiming that the registry was refreshed. ``` #### Claude Create the Claude destination directory with `mkdir -p ~/.claude/skills`. Put the following block in `~/.claude/CLAUDE.md` to apply it to every project, or in a repository's `CLAUDE.md` to share it with that repository's team. ```markdown CLAUDE.md theme={null} ## Flowglad MCP Skill bootstrap At the start of every new session, before handling the first task: 1. Confirm that the Flowglad MCP server is connected. 2. Refresh the agent Skill catalog from Flowglad. Prefer the advertised `skills/list` MCP extension method. If the client does not expose that method directly, use the Flowglad server's `resources/list` method and select resources whose URIs begin with `skill://flowglad/`. 3. For every returned Skill, retrieve its manifest with `skills/get` when available, then read each listed resource with `resources/read`, beginning with `SKILL.md`. 4. Synchronize the package into `~/.claude/skills//`. Compare the returned content digests and rewrite only new or changed Flowglad-managed files. Never overwrite or delete unrelated local Skills. 5. Treat the refreshed Flowglad package as the source of truth for this session. Make the synchronized Skills available for automatic matching and explicit `/skill-name` invocation. 6. If this Claude client cannot call the Skill or resource methods, report that limitation once and continue without claiming that the registry was refreshed. ``` You can ask ChatGPT / Codex or Claude to add the appropriate block to its own user-level instruction file. Review the proposed edit before accepting it because that file affects future sessions. The instruction is a best-effort agent bootstrap; if your environment must refresh Skills deterministically, implement the same synchronization in a trusted `SessionStart` hook or your MCP client integration. ## Where Skills are used Invoke an enabled Skill with its `/` in: * Space chats * Automation instructions You can add request-specific context after the slash command. Flowglad combines that context with the Skill's reusable instructions for the current task. Only Skills available in the current organization and Space context can be invoked. ## Creating and maintaining Skills Open the **organization menu** → **Skills** → **New Skill**. In the **Skill** tab, enter **Name**, **Slug**, optional **Description**, and the reusable instructions in **Markdown**. Use the **Files** tab for any supporting package files, then select **Create Skill**. The Slug uses lowercase letters, numbers, and hyphens, begins with a letter or number, and is what users type after `/`. Creating or editing a Skill produces a draft. On the Skill detail page, edits autosave; select **Publish Draft** to verify and publish the draft. If verification fails, use the displayed diagnostics to correct the draft and publish again. Use **History** to inspect revisions, restore a superseded revision, or discard a mutable draft when those actions are available. **Disable Skill** removes it from chat and Automation resolution without deleting revision history; **Enable Skill** makes it available again. ## Invoke a Skill In the chat composer, type `/` and choose an available Skill, or type its exact `/`. Add the request-specific context after the slash command. The same slash command can be included in Automation definitions. Only enabled, available Skills appear for the current context. If the product presents a **Run skill** confirmation card, review the inputs and confirm it there; that one-off run flow is not available in every organization. ## Create or edit a Skill with chat In a Space chat, ask chat to create or edit a Skill. Review the proposal, select **Start Skill-work**, follow the activity, and use **Save Skill and Enable** when the result is ready. ## Start from a Skill template The **Skills** page includes **Skill Templates**. Search or filter the catalog, preview a template, and select **Copy Skill**. The copy becomes an organization Skill that can be edited and published like any other Skill. ## Skills and Automations A Skill defines how to perform reusable work. It does not decide when that work runs. Use an Automation when work needs to run on a schedule or in response to an event. An Automation can invoke one or more Skills so the same process can be reused across recurring work and chats.