> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Add a custom skill

> Package your team's playbook for a class of problems as a versioned Markdown skill.

export const DocMeta = ({type, applies, owner}) => {
  const LABELS = {
    tutorial: "Tutorial",
    "how-to": "How-to guide",
    explanation: "Explanation",
    reference: "Reference"
  };
  return <div className="e6-meta">
      <span className={type === "how-to" || type === "tutorial" ? "e6-eyebrow" : "e6-eyebrow e6-eyebrow--quiet"}>{LABELS[type] || type}</span>
      {applies ? <span>Applies to: {applies}</span> : null}
      {owner ? <span>Owner: {owner}</span> : null}
    </div>;
};

<DocMeta type="how-to" applies="All deployments" />

A skill is a reusable bundle of instructions, templates and quality checks for **one capability**, such as anomaly investigation, a monthly executive report, or yield-loss root-cause analysis. It's the natural home for "the way our team always does X".

A tool is a function call. A skill is a packaged way of solving a class of problems.

## Add a skill

1. Write a Markdown skill with its purpose, when-to-use guidance, instructions, templates and checks. Use the same `SKILL.md`-style format as AgentFlow's built-in skills.
2. Choose global or project scope.
3. Save a version.
4. Attach the skill to each workflow step that needs the playbook.

## What a skill can't do

A skill supplies guidance. It doesn't grant tools: its `allowed_tools` field is authoring guidance only. The workflow step and the runtime tool boundary decide which tools can be called.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.