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

# Build and Publish Skills

> Teach the Inflection agents how your team works with workspace skills that every teammate's agent follows.

Skills teach the Inflection agents how your team works (your program steps, naming conventions, an email QC checklist, your brand rules) once, so every teammate's agent follows them.

## Understand Skills

A skill is a short set of instructions the agent loads when it's relevant to the task. Common skills capture:

* How your team builds a program, such as your newsletter.
* Your naming conventions and definitions.
* An email QC checklist to run before sending.
* Your brand voice and guardrails.

There are two kinds of skills:

* **Inflection skills** ship with the product and guide how the agents build audiences, emails, journeys, and more. You can read them, but you can't edit them.
* **Workspace skills** are the ones your team publishes. They are private to your workspace and available to everyone in it.

## Review the Prerequisites

* You must be a **workspace admin** to publish, update, or retire skills. Anyone in your workspace can view and use them.
* Connect the **Inflection MCP** in Claude or ChatGPT. See [Integrate with Claude](https://docs.inflection.io/agents/integrate-with-claude.md) or [Integrate with ChatGPT](https://docs.inflection.io/agents/integrate-with-chatgpt.md).

> [!NOTE]
>
> Publish and edit skills from your connected AI client. The Inflection skills management page in the app is not available yet.

## Publish a Skill

1. Write your skill as plain text, or copy an example below. Give it a clear name and a short **when to use** line.

2. In your AI client, paste the skill and ask the agent to add it as a workspace skill:

   ```txt theme={null}
   Add this as a skill in Inflection so my whole team can use it.
   Name it build-newsletter. Here's the skill: [paste your skill]
   ```

3. The agent publishes the skill and confirms.

4. Test it. In a new chat, ask the agent to do the task, such as build our newsletter, and check that it follows your skill.

## Copy an Example Skill

Copy one, then publish it with the prompt above.

**Build our newsletter**

```markdown theme={null}
# Skill: Build our newsletter

When to use: the user asks to build or draft our newsletter.

Steps:
1. Start from our Newsletter visual template.
2. Structure: preheader, header, short intro, 3 story blocks (headline + 2-3
   sentences + one link), footer with unsubscribe.
3. Greet with the recipient's first name; fall back to "there".
4. Keep each story under ~60 words; one link per story.
5. Match our brand voice: friendly and concise.
6. Save as a draft named "Newsletter - <Month> <Year>". Never send.
```

**QC an email before send**

```markdown theme={null}
# Skill: QC an email before send

When to use: the user asks to review or check an email before sending.

Check and report on:
- Subject and preheader present, concise, no leftover placeholders.
- One clear call to action; every link resolves.
- Personalization tokens have fallbacks.
- Unsubscribe link and mailing address present.
- Images have alt text; layout holds on mobile.

Output a checklist with pass/fail and specific fixes. Don't auto-apply fixes.
```

## Manage Your Skills

* **See your skills.** Ask "what Inflection skills does our workspace have?" The agent lists your workspace skills alongside the Inflection skills.
* **Read a skill.** Ask the agent to show a skill by name to see its current instructions.
* **Update a skill.** Ask the agent to update it. Each update is saved as a new version, and you can ask to see earlier versions.
* **Retire a skill.** Ask the agent to deprecate a skill you no longer use.

> [!NOTE]
>
> **Example prompts:**
>
> * "Show me our build-newsletter skill."
> * "Update build-newsletter to use 4 story blocks instead of 3."
> * "Deprecate the old QC checklist skill."

## Follow Best Practices

**Keep each skill focused.** One task per skill works better than one large skill that covers everything.

**Start with a clear when-to-use line.** The agent uses it to decide when to load the skill.

**Write steps, not prose.** Numbered steps and checklists are easier for the agent to follow consistently.

**Test after every change.** Run the task in a new chat to confirm the agent picks up the latest version.

## Get Help

If a skill isn't behaving as expected, contact your Customer Success team with a link to the conversation and what you expected.

> [!NOTE]
>
> **Additional reading:**
>
> 1. [Inflection Agents](https://docs.inflection.io/agents/inflection-agents.md)
> 2. [Inflection MCP](https://docs.inflection.io/agents/inflection-mcp.md)
> 3. [Integrate with Claude](https://docs.inflection.io/agents/integrate-with-claude.md)


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