Skip to main content
A skill is a reusable set of instructions that teaches an agent how to approach and execute a task. It packages an outcome-oriented procedure with the approved tools an agent may use, so the capability can be reused across supported models, agents, and gateways.

​
Plan the skill

Start with a specific business outcome rather than a list of tools. For example, a customer-support skill can define the full process for gathering customer context, checking documentation, resolving the request, and escalating when necessary. Before authoring, identify:
  • The task objective and expected result.
  • The tools required to complete the task.
  • Constraints, approval steps, and escalation conditions.
  • The response format that makes results useful to the requester.
  • The teams, gateways, and audiences allowed to use the skill.

​
Create a skill

  1. Open Skills Hub in MCP Foundry.
  2. Select New Skill.
  3. Enter a descriptive name and description.
  4. Optionally add licensing and compatibility information for skills shared across teams or environments.
  5. Attach the MCP tools the skill is permitted to use.
  6. Select the MCP gateways that may expose the skill.
  7. Set ownership and visibility.
  8. Add the markdown instructions, then select Create Skill.

​
Write effective skill instructions

The markdown instructions are the operating procedure an agent reads when the skill is activated. Make them explicit and structured so behavior remains consistent across different underlying models. Include these sections where relevant: Avoid instructions that depend on hidden knowledge or unspecified tool behavior. State the expected checks before write operations and what the agent should do when a required tool or resource is unavailable.

​
Validate and distribute the skill

After creation, use the skills list to preview the skill, download its markdown, or edit its configuration. Test it with representative requests through each selected gateway before making it broadly available.
  1. Confirm the skill exposes only the tools selected during creation.
  2. Verify its instructions produce the required response format and honor guardrails.
  3. Test failure and escalation paths, not only successful requests.
  4. Confirm that only the intended gateways and clients can discover the skill.
  5. Update the skill’s gateway configuration whenever its distribution requirements change.
Governance note: A skill’s portability does not broaden its permissions. The attached tools, gateway configuration, virtual-server composition, and backend credentials should all remain least-privileged for the task.

​
Maintain reusable capabilities

Assign a responsible team and review skills when workflows, tools, policies, or model behavior change. Reuse the same skill across agents instead of copying its instructions into individual applications. This keeps the organizational procedure in one governed location while allowing the implementation behind the agents to evolve. For related assets, see Manage MCP capabilities and MCP Foundry concepts.