DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to install a skill into a project for Claude Code with Skills

Add a published agent skill to one project so Claude Code can follow its instructions.

Authorization notice. Skills is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Remote script. Skills are instructions your agent will follow, so read the SKILL.md of any skill from an unfamiliar source before installing it.

Who it is forA developer who wants Claude Code to apply a specific skill, such as web design guidelines, to the current project.

The problemAgent 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 outcomeThe chosen skill is installed in the current project and is available to Claude Code.

What you need first

  • Node.js 22.20 or later
  • A terminal opened in your project folder
  • A supported coding agent installed on your machine, such as Claude Code, Codex, or Cursor

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 for your agent

Using the vercel-labs/skills CLI, install the <skill name> skill from <source repo> 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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page