SkillacrityBring in your skills
Skills come in through the web app: one at a time on New skill, or many at once on the Bring in skills page, with the onboarding skill to gather them.
A skill is a prompt or playbook your people have written for AI.
What a skill folder holds
A skill is a folder in the open SKILL.md format. It holds a SKILL.md file with the instructions, and can hold other files at their paths: reference documents the AI tool reads, scripts it may run, and assets such as templates, images and data. The SKILL.md file starts with the skill’s name and description:
---
name: qbr-prep
description: Prepares a quarterly business review for a customer account in the sales team's format. Use when someone is getting ready for a QBR.
---
# QBR prep
Ask for the account's numbers for the last four quarters, then ...The description matters most: it is how Skillacrity decides when to deliver the skill. A skill can also say when to use it and when not to, which you can edit on its page in the web app.
| Name | Up to 64 characters. |
|---|---|
| Description | What the skill does and when to use it, usually in one or two sentences. Up to 1,024 characters. |
| Size | Up to 100 MB for the whole skill, 25 MB for any one file, and 2,000 files. |
Some AI tools take smaller skills. Skillacrity tells you when a skill is larger than some tools accept.
One skill: New skill
In the web app, open Skills, then New skill. Write the skill there, or paste a prompt or a document you already use. Skillacrity turns a pasted prompt or document into a skill and shows you the name and description it wrote, which you can change before you publish it.
Many skills: the onboarding skill
Most people have skills spread across their AI tools. The onboarding skill finds them for you. Download it from the Bring in skills page in the web app, add it to your AI tool, and ask your AI tool to use it. There are two versions:
- For AI tools that work with files on your computer, such as Claude Code, Codex, Gemini CLI and Claude’s Cowork. It looks in your AI tools’ skill folders, lists the skills it finds, and copies the ones you choose into one new folder in Downloads.
- For chat tools, such as Claude on the web, ChatGPT and Gemini in the browser, which can’t see your computer. You paste or attach your skills, and prompts you’d like made into skills, and it puts them into one .zip for you.
Adding it to your AI tool
| AI tool | Version | How |
|---|---|---|
| Claude Code | For your computer | Unzip it into ~/.claude/skills, so the folder is ~/.claude/skills/skillacrity-onboarding. Then type /skillacrity-onboarding, or ask “bring my skills into Skillacrity”. |
| Codex | For your computer | Unzip it into ~/.agents/skills, so the folder is ~/.agents/skills/skillacrity-onboarding. Then type $skillacrity-onboarding, or ask in your own words. |
| Gemini CLI | For your computer | Unzip it into ~/.gemini/skills, so the folder is ~/.gemini/skills/skillacrity-onboarding. Then ask “bring my skills into Skillacrity”. |
| Claude on the web or the desktop app | For chat tools, or for your computer in Cowork | Open Customize, then Skills, choose + and then Upload a skill, and pick the zip. Code execution must be on. On an Enterprise plan, an owner turns skills on first. |
| ChatGPT | For chat tools | On plans with skills (Business, Enterprise and Edu), open Skills and upload the zip. An admin may need to allow uploads first. |
| Microsoft 365 Copilot | Often not needed | Copilot already keeps your skills as folders in a Skills folder in your OneDrive. Download that folder from OneDrive as a .zip and upload it as it is. |
On Windows, the folders are under your user folder, such as %USERPROFILE%\.claude\skills.
What it does, and what it never does
- It sends nothing anywhere. You upload the folder yourself, and check every skill first.
- It asks before it looks, and copies nothing until you choose.
- It only makes copies. Your skills stay where they are, unchanged.
- It never opens your conversation history, sign-in files, SSH keys, mail or browser data, and it doesn’t follow links.
- Your own skills are ticked. Skills in a project folder, which may be your team’s, are listed but not ticked. Skills that came with a plugin, or that the AI tool’s maker ships, are left out, because someone else made them.
- Copies leave out hidden files such as
.env, keys and certificates, credential files, dependency folders such asnode_modules, and archives. A README in the new folder says what was left out of each skill. - A skill that holds what looks like a key or a password isn’t copied at all. You’re told the file and the line, so you can take it out and try again.
Uploading on the Bring in skills page
Drop the onboarding skill’s folder on the Bring in skills page, or any folder or .zip of skill folders. Each folder with a SKILL.md becomes one skill. Check the names and descriptions, and choose once who can see all of them, starting from your default audience. The page then shows what happened to each skill.
Uploads running at the same time, yours or a colleague’s, never create duplicates or overwrite each other.
What happens on the way in
- Safety scans. Every file in every skill is scanned. A skill holding a secret, such as a password or an API key, is rejected and never stored, and you’re told what was found so you can remove it. A skill flagged for anything else waits for one of your company’s admins to review it, and you’re told which one and why.
- Duplicates. A skill that overlaps one already in the library comes in as a suggested merge instead of a second copy.
- Credit. Every skill names you as its author.
- Live within a minute. Once a skill is live, it can be delivered to everyone who can see it within a minute.