# AI use cases for Skills (vercel-labs/skills) Repo: [vercel-labs/skills](https://github.com/vercel-labs/skills) | Use cases: 5 | Page: https://dedupedai.com/use-cases/vercel-labs-skills/ The skills CLI is a TypeScript command-line tool (run as npx skills) for finding, installing, updating, and creating reusable instructions that teach coding agents how to perform tasks. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Install a skill into a project for Claude Code: https://dedupedai.com/use-cases/vercel-labs-skills/install-skill-for-claude-code/ - Try an agent skill without installing it: https://dedupedai.com/use-cases/vercel-labs-skills/try-skill-without-installing/ - Keep installed agent Skills up to date: https://dedupedai.com/use-cases/vercel-labs-skills/keep-installed-skills-current/ - Write and share a new agent skill: https://dedupedai.com/use-cases/vercel-labs-skills/write-and-share-new-skill/ - Sync Skills bundled in npm packages (experimental): https://dedupedai.com/use-cases/vercel-labs-skills/sync-skills-from-npm-packages/ ## How to install a skill into a project for Claude Code with Skills Repo: [vercel-labs/skills](https://github.com/vercel-labs/skills) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Add a published agent skill to one project so Claude Code can follow its instructions. **Who it is for:** A developer who wants Claude Code to apply a specific skill, such as web design guidelines, to the current project. **The problem:** Agent Skills are useful only when the coding agent can load them, and setting them up by hand means finding the right files and placing them in each agent's skill folder. **The outcome:** The chosen skill is installed in the current project and is available to Claude Code. ### Steps 1. Confirm Node.js 22.20 or later is installed. 2. From your project folder, run `npx skills add vercel-labs/agent-skills --skill web-design-guidelines -a claude-code`. 3. Run `npx skills list` to confirm the skill appears in the installed list. 4. Add `-g` to the install command if you want the skill available across projects. ### Prompt to paste into your agent ```text Using the vercel-labs/skills CLI, install the skill from into this project for Claude Code. Then run npx skills list and report the skill name and whether it is installed. Verify the skill appears in the list before you report success. ``` ### Caveat The README says to run Skills add from your project and that Skills install to the current project by default, so check the install location before relying on it. Risk, remote script: Skills are instructions your agent will follow, so read the SKILL.md of any skill from an unfamiliar source before installing it. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vercel-labs-skills/install-skill-for-claude-code/ ## How to try an agent skill without installing it with Skills Repo: [vercel-labs/skills](https://github.com/vercel-labs/skills) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Generate a skill prompt or launch a supported agent with a skill for a one-time run. **Who it is for:** A developer who wants to test a skill's effect on a task before deciding whether to keep it in the project. **The problem:** Installing a skill just to see what it does adds files to a project that you may later need to clean up. **The outcome:** You get the skill's prompt printed to the terminal, or a supported coding agent starts with the skill loaded, and nothing is installed. ### Steps 1. Confirm Node.js 22.20 or later is installed. 2. Run `npx skills use vercel-labs/agent-skills@web-design-guidelines --agent claude-code` to launch Claude Code with the skill. 3. To only view the prompt, run `npx skills use vercel-labs/agent-skills@web-design-guidelines` without the --agent option. 4. Read the printed or loaded prompt before you act on its output. ### Prompt to paste into your agent ```text Run the vercel-labs/skills CLI to print the prompt for the skill from , without the --agent option. Report the first five lines of the prompt and confirm that no skill was installed into the project. ``` ### Caveat The README documents launching only supported coding agents with --agent, so confirm your agent is on the supported list in docs/agents.md before you run it. Risk, remote script: Using a skill with --agent launches a coding agent with that skill's instructions, so review the printed prompt first when the source is unfamiliar. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vercel-labs-skills/try-skill-without-installing/ ## How to keep installed agent Skills up to date with Skills Repo: [vercel-labs/skills](https://github.com/vercel-labs/skills) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Check for newer versions of installed Skills, update them, or remove the ones you no longer use. **Who it is for:** A developer who has several Skills installed across projects and wants them current without re-installing each one. **The problem:** Installed Skills can fall behind their source, and tracking which ones need updates by hand is slow. **The outcome:** You know which installed Skills have updates available, and they are updated or removed in one pass. ### Steps 1. Run `npx skills list` to see the Skills currently installed. 2. Run `npx skills check` to see which installed Skills have available updates. 3. Run `npx skills update` to update them, or name specific Skills after the command. 4. Run `npx skills remove` with the skill names you no longer need. ### Prompt to paste into your agent ```text Use the vercel-labs/skills CLI in this project to list installed skills, check for available updates, and update . Report which skills changed and which were already current. Verify the list again after the update. ``` ### Caveat The README lists update and remove commands that take optional skill names, but it does not describe what update changes beyond the skill, so review the result after running it. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vercel-labs-skills/keep-installed-skills-current/ ## How to write and share a new agent skill with Skills Repo: [vercel-labs/skills](https://github.com/vercel-labs/skills) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Generate a skill template and edit its SKILL.md with instructions for your agent. **Who it is for:** A developer or team lead who has a repeated task, such as a review checklist, and wants a coding agent to follow the same steps each time. **The problem:** Teaching a coding agent a repeatable workflow in each chat session wastes time and produces inconsistent results. **The outcome:** You have a generated skill folder with a SKILL.md file that holds your instructions, ready to edit and share. ### Steps 1. Run `npx skills init my-skill` in the folder where you want the new skill. 2. Open the generated SKILL.md and write the instructions your agent should follow. 3. Read docs/creating-skills.md in the repository for the frontmatter format and discovery rules. 4. Install the skill locally with `npx skills add` to test it before sharing. ### Prompt to paste into your agent ```text Run npx skills init from the vercel-labs/skills CLI, then fill in the generated SKILL.md with instructions for . Report the path of the SKILL.md file and confirm the frontmatter follows the format in docs/creating-skills.md. ``` ### Caveat The README points to docs/creating-skills.md for the format and discovery rules, so check those details there before publishing a skill. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vercel-labs-skills/write-and-share-new-skill/ ## How to sync Skills bundled in npm packages (experimental) with Skills Repo: [vercel-labs/skills](https://github.com/vercel-labs/skills) | Difficulty: Advanced | Time: 30 minutes | Basis: From the README Link Skills that ship inside npm dependencies into your project so they update with the package. **Who it is for:** A developer whose project depends on an npm package that bundles instructions for coding agents, such as agent-browser in the README example. **The problem:** Skills shipped inside an npm package do not reach your agent unless you wire them up by hand, and they can go stale when the package updates. **The outcome:** Packaged Skills are linked into your project and follow the dependency version. ### Steps 1. Install the package and the CLI as dev dependencies with `npm install -D skills agent-browser`. 2. Run `npx skills experimental_sync -y` from the project folder. 3. Check the linked Skills in the project and confirm they match the package version. 4. Read docs/commands.md#skills-experimental_sync before relying on this feature, because the README says its behavior may change. ### Prompt to paste into your agent ```text In this project, run npm install -D skills , then npx skills experimental_sync -y. Report which skills were linked and confirm they came from the installed package. Note that this feature is experimental. ``` ### Caveat The README labels this feature experimental and says its options and behavior may change, so pin your CLI version if you depend on it. Risk, remote script: Packages you sync can bring in Skills that instruct your agent, so review the linked SKILL.md files before your agent uses them. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vercel-labs-skills/sync-skills-from-npm-packages/