One Link Installs
Your Whole AI Setup

You spend months teaching AI how you work and what your business does. Then a teammate asks how you did it and the honest answer is four links, a zip file, and a paragraph of instructions. They install two things and give up.

On August 7, 2026, skills.sh shipped Skill Packs, which fixes exactly that. You bundle your skills into one pack and it gives you a single link. The other person runs one command and has your setup.

The genuinely useful part is that it is not locked to one AI. You use Claude, someone else uses Cursor or Codex, and the same skills work for all of them. Below is my own pack, ready to install in one command, plus how to build your own and the checklist to run before you install anyone else's.

40+ skills, free. Works in Claude, Claude Code, Codex, and Cursor.

Run it from the project folder you want the skills in, or your home folder to get them everywhere. Then restart your AI tool. Skipping that restart is why most people think it did not work.

Inside are the nine skills I built and use daily, including the Humanizer, the harness architect, and the founder council. The rest are the best open-source ones I found, mostly context engineering, writing, and design. Every community skill keeps its original author and license.

You do not install the tool first. It runs through npx, which means the command downloads it, uses it, and gets out of the way. Open your terminal in the project folder you want the skills in, then:

1. A whole pack: run npx skills add followed by the pack URL, which looks like https://skills.sh/p/ and then the pack id.
2. A single skill from GitHub: run npx skills add followed by the owner and repo, for example npx skills add vercel-labs/agent-skills.
3. Global instead of one project: run it from your home directory so the skills land in the global folder and follow you into every project.
4. Skip the telemetry: put DISABLE_TELEMETRY=1 in front of the command if you would rather it not phone home.

Then restart your AI tool so it picks up the new files. If a skill does not seem to be firing, that restart is the reason nine times out of ten.

A skill is not a document. It is instructions your AI will follow with whatever access you already gave it. Installing a stranger's pack is closer to running their script than reading their blog post, and packs are unlisted so there is no rating to lean on.

None of that means avoid them. It means spend ninety seconds first. The checklist below is short on purpose, so you will actually use it.

The reason to build one is not tidiness. It is that your team stops getting different results from the same request.

1. Gather first, and be ruthless. Open your skills folder and pull out only the ones you actually reach for. Four good skills beat twenty you forgot you had, and a bloated pack is one nobody navigates.
2. Put each skill in its own folder. This is the step that trips everyone. A skill is a folder named after the skill with a SKILL.md inside it. Not a loose file, and not a file named after the skill. Get this wrong and the builder tells you it found no skills at all.
3. Check your frontmatter. Every SKILL.md opens with three dashes, then name, then description, then three dashes, and that block has to be the very first thing in the file. Nothing above it, not even a comment. And if your description contains a colon followed by a space, wrap the whole description in quotes or it will be silently rejected.
4. Go to skills.sh/packs/create and sign in with Vercel. Add a name and a short description, then choose the Vercel team you want to share it with.
5. Add your sources. You can mix public skills from the directory, your own files, folders or a zip, and skills from GitHub repos you connect. One thing to know: connecting a repo pulls in every valid skill in it, with no way to cherry-pick. If you only want three skills out of someone's twenty, download them and upload just those.
6. Strip anything private before you upload. Real client names, keys, internal links, anything you would not email outside the company. Packs are unlisted but not access-controlled, so anyone with the link can view and install it.
7. Create it, then check the count. If the number of skills is lower than what you uploaded, some got rejected for the frontmatter reasons above. Find them before you share the link.
8. Share the link with one line, not a paragraph. The install command and what to expect. That is the whole point of a pack.

If you want a place to find skills worth putting in a pack, I walked through the free directory and how to spot the good ones in the skills marketplace guide.