How to Share AI Skills and Workflows Across a Team
Share AI skills by publishing them in one place the whole team can reach, with access set by group and the integrations each skill needs attached. The person who knows the work writes the skill, teammates refine it, and it appears in every member's portal and assistant. In Metorial, Magic Skills are written in a collaborative editor, shared with groups through portals, and can sync one way to a GitHub repository, so nobody needs a GitHub account to contribute.
A skill captures how your team does a job, so an agent follows the same steps every time instead of improvising. The value comes from sharing it, and that is where most teams get stuck: skill files end up in one person's folder, or in a repository only engineers can edit.
What makes a skill worth sharing?
It does one job the team does often, it is named for that job ("Summarize Linear escalations", not "Linear helper"), and it names the tools it uses. A skill that needs Linear and Slack is only useful to someone who has both connected.
How do you share a skill across a team?
1. Draft it where the expert can edit it. In Metorial, Magic Skills are written in a collaborative editor. A support lead can draft a refund skill without opening a repository.
2. Attach the integrations it needs. Link the skill to the approved integrations it uses. They show on the skill card in the portal, so people can see what access the workflow uses.
3. Keep it private while drafting. Invite a few teammates to refine the instructions before it goes wider.
4. Share it with groups. Publish it to the team's portal and allow the groups that should see it. Admins can also publish approved skills directly from the dashboard.
5. Use it from the assistant. Clients that support skills load it, and people call it by name, commonly with a slash command such as /summarize-escalations.
How do you keep skills in Git without making everyone use Git?
Back a skill marketplace with a GitHub repository. Metorial then syncs every skill change to the repository, one way. Engineers keep a versioned copy in Git, and everyone else edits in Metorial.
How do you keep shared skills safe?
Set the execution policy once: whether skills can run scripts, which file extensions they can include, and where files can live. Because a skill uses approved integrations, it cannot reach a tool the person running it has not been allowed to use, and every call it makes is logged in Tracing.
Frequently asked questions
What is an AI skill?
A packaged set of instructions, files, and tool access that tells an agent how to do a specific job the way your team does it, such as handling a refund request or researching an account before a call.
Why not keep skills in a Git repository?
A repository works for engineers. For sales, support, or finance, it means a GitHub account, a pull request, and a review for every change, so the people who know the work stop contributing.
Which assistants can use shared skills?
Clients that support skills, such as Claude Code and Cursor, can load them and usually invoke them by name with a slash command. The integrations a skill uses reach any MCP-capable assistant.
Can a skill run scripts?
Only if you allow it. In Metorial, admins decide whether skills can include and run script files, which file extensions are allowed, and whether files can sit outside the standard directory structure.
Who should be able to publish a skill?
Anyone can draft one privately. Publishing to a group should go through the team lead or an admin, so each team sees a short list of skills that work.