Skip to content
MeloSkill

Guide

How to install an agent skill

A skill is a folder with a SKILL.md file. Compatible agents load the description at startup, then the body only when the task matches.

MeloSkill listings already print an install command. Copy it. You do not need an account here. The command talks to GitHub and to the agent folders on your machine.

1. Skills CLI

The usual command is from the open skills CLI (the same family as skills.sh). From a listing on this site it looks like one of these: 

# Whole repo
npx skills add anthropics/skills

# One folder inside a repo (what most MeloSkill listings use)
npx skills add https://github.com/anthropics/skills/tree/HEAD/skills/frontend-design

# One named skill from a catalog
npx skills add vercel-labs/agent-skills --skill react-best-practices

Useful flags:

  • -g — install for your user, not this git repo.
  • -a claude-code / -a cursor / -a codex — only those agents.
  • -s skill-name — one skill when the repo contains many.
  • -y — skip prompts once you trust the source.

Prefer the command on the listing over inventing a path. Monorepos often have several SKILL.md files; installing the repo root can dump marketing or PDF skills you did not ask for.

2. Where the files go

Default is project scope (commit the folder if the team should share it). -g is global. Paths differ by agent; the CLI creates the right one. If you install by hand, copy the folder that contains SKILL.md, not the whole monorepo.

Agent Project Global
Claude Code .claude/skills/ ~/.claude/skills/
Cursor .agents/skills/ or .cursor/skills/ ~/.cursor/skills/
Codex .agents/skills/ ~/.codex/skills/

Agents and CLI versions move these paths. If a listing’s command and this table disagree, trust the command you copied, then confirm a SKILL.md exists on disk.

3. Manual copy

No Node? Clone the GitHub path from the listing, keep the skill directory intact (SKILL.md plus any references/ or scripts/), and place that directory in the table above. Restart the agent if it does not pick the file up.

4. Did it work?

Ask the agent to do the job the skill describes — “design this landing page” for frontend-design, not “list my skills.” If nothing happens, the YAML description is usually too vague for the trigger, or the file landed in a directory the agent does not watch.

Updating is the same command again. We refresh snapshots from GitHub on a regular schedule; the last-change date on the listing is the signal that the author changed the file, not repository stars.

FAQ

Do I install every skill on a task page? No. Pick one or two whose “when to use” matches the job. Overlapping taste files will compete on triggers. The choose a skill guide walks the common overlaps.

Is this an MCP server? No. A skill is instructions. MCP is a live tool connection. Some SKILL.md files mention MCP; enabling that is a separate decision in the agent.

Can I install from this website’s copy? Don’t. Use GitHub via the command we print. Our page is a snapshot for reading; the author can change the file tomorrow.

Also