A skill is a set of instructions your team writes once: how to copy-edit a page, run a launch checklist, brief a designer. Agents and chats load it when a task calls for it, and Claude and ChatGPT read the same copy through the MCP server. Update the skill and everything follows the new version.
Skills or tools?
A tool is something the AI can do: list campaigns, read a PostHog insight, publish a Webflow page. Tools come with each integration you connect, and you never write one. A skill is how you want the work done, written in your own words, and it often uses several tools while it runs. If tools are the knives and pans, a skill is the recipe. Tools live with their integration in Settings; skills live here.
Create a skill
- Select Skills in the sidebar.
- Select New skill.
- Give it a Name: lowercase letters, numbers and hyphens, like
copy-editing. This is how agents and chats refer to it. - Write a Description of what it does and when to use it. Agents read this to decide when the skill applies, so include the situations that should trigger it.
- Write the Instructions in Markdown: steps, examples, edge cases.
- Select Create skill.
Any team member can create, edit and delete skills. Names are unique within a team.
Use a skill in chat
Ask for it by name: “Copy-edit this page with our copy-editing skill”. Ada loads the instructions and follows them for the rest of her reply. She also picks a skill up on her own when your request matches its description, so a clear description matters more than a clever name.
Use a skill in a custom agent
Custom agents see the same skills. Put a line such as “Always apply the copy-editing skill before publishing” in the agent’s instructions and it loads the skill on every run, including runs that happen without you.
Built-in skills
Growth Method ships its own skills too: the campaign and goal workflows such as create-campaign, plan-campaign and analyse-campaign. They show until you create your first skill, then step aside; turn on Show built-in skills above the list to see them again, and select View to see what each one does, which agent runs it and how it starts. Growth Method manages these, so you cannot edit them.
Use skills from Claude or ChatGPT
Once your AI client is connected to the MCP server, your team’s skills are available there too:
- In Claude, each skill appears as a prompt. In Claude Code, type
/and pick the entry named after the server and the skill, for example/mcp__growth-method__copy-editing. - In any client, including ChatGPT, ask for the skill by name and the client loads it with the load-skill tool.
- To create or update a skill from your client, ask it to save the skill to Growth Method. It shows you the name, description and instructions and asks you to confirm before anything changes. Saving replaces the whole skill, which makes it a good way to publish a SKILL.md file you keep locally.
A skill you create from a client appears in that client’s list after it reconnects.
One Markdown field, no attachments
A Growth Method skill is the instructions field and nothing else. There is no
folder for reference files, so a local skill that points at a references/
directory or other sidecar files loses them when it is saved. Before you
publish one, fold anything the instructions depend on into the Markdown
itself, or cut it. Everything the AI needs to follow the skill has to be in
that one field.
Keep your clients in step
The team copy in Growth Method is the one to trust. Whenever you write or change a skill in a connected client, it offers to save it to Growth Method. To catch up later, run the sync-skills prompt. Any client that shows prompts has it; in Claude Code it is a slash command. In a client that keeps skills as files, such as Claude Code or Cursor, it compares each local skill with the team copy, lists what is new or changed, and saves each one after you confirm. In a client without skill files, such as Claude on the web, it shows the team’s skills and offers to turn instructions you keep pasting into a skill. Once a skill is saved, delete the local file and use the Growth Method one.
Keep skills focused
Only the name and description of each skill travel with every message. The instructions load when the skill is used. So a long skill costs nothing until it runs, but a vague description means it never runs. Describe the trigger, keep the steps concrete, and split two jobs into two skills.