How Skills work
How CustomGPT.ai Skills let you split your agent's persona into small, named, reusable instruction sets.
This article explains what a Skill is and how your agent decides when to use one. Refer to Create and manage Skills to add your first one.
What a Skill is
A Skill is a named, self-contained set of instructions for one job - specific translation instructions, an onboarding sequence, a sequence in which MCP connectors should be used. It has a name and its own block of instructions, written the same way you'd write your main persona, just scoped to that one task.
Why Skills exist
Your agent's behavior normally lives in one persona instruction box. The more you ask of your agent, the longer that box gets - more rules, more exceptions, more edge cases - until it's hard to read and risky to edit. Skills split that single box into focused, named pieces you can build, edit, and reuse on their own.
How your agent uses a Skill
A Skill doesn't run on its own and isn't a separate agent. Your agent only reaches for a Skill when your main persona tells it to. You reference a Skill by name, in plain language, from your main persona - for example, "use the Onboarding skill when a customer tells they are a new user" - and the agent applies that Skill's instructions when the situation matches.
Skills and your other settings
- Actions and integrations: Skills shape your agent's instructions, they don't limit what it can reach. While a Skill is active, your agent still has full access to your knowledge base, Actions, and integrations.
- Query cost: Applying a Skill doesn't add to your query cost. Its instructions replace part of your persona at the right point in the flow, rather than adding an extra step.
- Persona Expert Mode: Skills are separate from the Persona Expert mode. Editing sub-personas in Expert mode has will not affect content of your Skills, but may affect when they are called.
Example use cases
- Split a support agent's refund, troubleshooting, and escalation flows into three Skills, then tell the main persona which one to use first.
- Build separate Qualifier, Objection Handler, and Demo Booking Skills so a sales agent treats a browsing visitor differently from a ready-to-buy lead.
- Move a long onboarding sequence into its own Skill so new users get a consistent walkthrough without cluttering the main persona.
- Break a large, hard-to-edit persona into one Skill per task, so a teammate can fix one flow without touching the rest.
- Reuse a Skill that already works well, like a proven escalation flow, as a starting point on a new agent.
Related articles
Updated about 1 hour ago