Skip to main content
Skills are versioned packages of reusable instructions and supporting files. Each package contains a portable SKILL.md with metadata and Markdown instructions. Your organization maintains the library; each person chooses which Skills their agent can use.

Choose Skills for Your Agent

Open Skills and turn on Use in my agent for a Skill. Existing Skills and newly published Skills start off for everyone. Enabled Only filters the list to your selections. Selecting a Skill does not grant authoring permission or change another person’s choice, including in another organization. Your selection follows the Skill’s current published version automatically. A draft-only or retired Skill can remain selected but is unavailable to your agent. Organization retirement overrides every user’s selection until it is re-enabled. Changes apply to subsequent server requests across your existing connections. Your client may need to refresh its local catalog. Instructions and files already loaded into an agent’s context cannot be erased by turning a Skill off.

Create and Publish

Users with Skill Authoring permission can select Create Skill, enter the name, slug, description and instructions, and add supporting files. A slug uses lowercase letters, numbers and single hyphens. Uploaded portable SKILL.md frontmatter is preserved; written instructions receive frontmatter from the form. Creating a Skill saves a draft. Detail-page edits autosave to the draft and leave the published instructions and files unchanged. Select Publish Draft to save pending edits and publish explicitly. Publication completes in the request after structural and file-integrity checks. A save failure or stale version blocks publication; resolve the error or refresh before trying again. Flowglad does not score instruction quality, install dependencies, import scripts or run Skill tests. Supporting scripts are reference files. Use an Automation with its own code when work needs execution, a schedule or an event trigger. Skill History retains earlier versions and legacy verification evidence. Eligible reference versions can be restored; original legacy files remain readable. Retire for Organization removes shared availability while retaining history and personal choices. It is separate from Use in my agent.

Use MCP Progressively

Ordinary tools work without the native Skills extension:
  • skills.list discovers your selected, published Skills as metadata.
  • skills.get loads one Skill’s instructions and file manifest.
  • skills.read_file loads supporting files in authenticated chunks when needed.
Native skills/list and skills/get expose the same selected organization Skills alongside Flowglad’s separate bundled authoring guides. Client support varies; connecting does not guarantee a client refreshes its catalog automatically. Each content request rechecks current access, selection and publication. Local folder installation or synchronization is not part of this feature.

Author with MCP

Use skills.list with view: "authoring" and skills.get with view: "authoring" to inspect the shared library before editing. These require skills:write on your membership and MCP grant. Admins can grant Skill Authoring in Settings → Team. Personal selection does not require this permission. skills.create and skills.update with action: "content" save drafts synchronously. skills.publish explicitly publishes an exact revision against the expected current publication. Large packages use skills.create_package_upload_session, exact uploads, then skills.finalize_package_upload_session. Repeating finalization of the same session retrieves its original result. After an uncertain create response, inspect the known resource before retrying; do not create duplicates. Skill components created by workflow templates are unpublished, unselected drafts. The outer template apply has its own progress tracking; it does not start a separate Skill verification job. Publishing a Skill never activates an Automation or Site.