Skills and Agents Library

Skills that make Claude Code more capable. Install one with a single command.

Browse the live catalog at skillsandagents.co · Built and maintained by Skills and Agents Co

Each skill adds a specific capability to Claude: check your business cashflow, see where your brand shows up in ChatGPT, fix your Ghost site's Google indexing, walk through filing an unemployment claim. One install, and Claude instantly knows how to do the job.

This repo is the source of truth for every skill we publish. Each is MIT-licensed, version-tagged, and ready to drop into Claude Code, Claude Desktop, or any Anthropic-compatible runtime that loads SKILL.md files.

Install the plugin marketplace

Add the marketplace once, then install any plugin from it:

/plugin marketplace add skills-agents-co/skills-and-agents-library

/plugin install financial-pulse@skills-and-agents

Swap financial-pulse for any plugin listed in .claude-plugin/marketplace.json. financial-pulse connects to Mercury, Ramp, and Grasshopper for a cashflow pulse. product-builder bundles code review, PR summaries, research briefs, competitor intel, and document drafting.

Who this is for

• End users who want Claude to handle a specific task end-to-end — no prompting tricks, no glue code. Pick a skill, install it, ask Claude.
• Product managers evaluating what Claude skills look like in the wild — real-world scope, packaging, and triggers worth borrowing.
• Developers building their own skills and agents — every folder here is a working reference you can fork, study, or PR against.

What's inside

Find a skill by what you want to do

More skills land here regularly. Star or watch this repo or follow the catalog to catch new releases.

Install in 30 seconds

Every skill installs the same way: download one pinned tarball, extract the skill's whole folder into ~/.claude/skills/, then restart Claude Code. Extracting the folder, not just SKILL.md, is what brings along the scripts/ and references/ files a skill's own instructions actually run.

(
  set -e
  skill="resume-tailor"   # <-- change me to the skill's folder (see note below)
  ref="v1.39.0"            # pinned release; matches index.json's skillFileUrl

  # The install removes "$HOME/.claude/skills/$skill" before it copies. If
  # $skill were empty or a path, that line would delete the wrong directory —
  # every skill you have installed — so refuse anything but a plain name.
  # The last arm rejects any character outside a folder name, which also keeps
  # a glob like "*" out: bsdtar treats a member pattern as a glob, so "*" would
  # extract the entire repository instead of one skill.
  case "$skill" in
    ""|.|..|*/*|-*|*[!A-Za-z0-9._-]*)
      echo "Set skill to a plain folder name, e.g. resume-tailor" >&2; exit 1 ;;
  esac

  work="$(mktemp -d)"
  trap 'rm -rf "$work"' EXIT

  curl -fsSL --connect-timeout 10 --max-time 120 --retry 3 --retry-delay 2 \
    --retry-connrefused --retry-max-time 120 -o "$work/repo.tgz" \
    "https://codeload.github.com/skills-agents-co/skills-and-agents-library/tar.gz/$ref"

  mkdir -p "$work/staged"
  topdir="$(tar -tzf "$work/repo.tgz" | grep -m1 '/' | cut -d/ -f1)"
  tar -xzf "$work/repo.tgz" --strip-components=2 --no-same-owner --no-same-permissions \
    -C "$work/staged" "$topdir/$skill"

  dest="$HOME/.claude/skills/$skill"
  rm -rf "$dest"
  mkdir -p "$(dirname "$dest")"
  cp -R "$work/staged" "$dest"

  echo "Installed to $dest"
)

The block runs in a subshell (the parens) so skill, ref, and the other variables it sets do not leak into your shell, and set -e inside it means a failed download or a bad skill name stops the install instead of leaving a half-populated directory that looks successful. It downloads and unpacks into a scratch directory first and only touches ~/.claude/skills/ once the extraction has succeeded, so a failed install leaves nothing behind: no empty skill folder for Claude Code to find, and no stray tarball. Re-running it replaces the install rather than merging into it, so a file dropped from a later release does not survive as a stale leftover.

What to put in skill. For almost every entry it is the folder name shown in the table above (resume-tailor, ceo-todo, and so on) — which is also the slug. It is not the slug for the four agents that ship inside another skill's folder: ceo-todo-daily installs as skill="ceo-todo", and financial-pulse-grasshopper, financial-pulse-mercury, and financial-pulse-ramp all install as skill="financial-pulse". Installing one of those pulls in the whole parent skill (including its other agents), which is expected — the agent file itself is the payload you actually run.

Installing an agent takes one more step. Claude Code loads subagents from ~/.claude/agents/, not from inside a skill folder, so the four agent entries above need their markdown copied out after the install block runs. Otherwise the file is on disk and the agent still does not register:

(
  set -e
  agent="ceo-todo-daily"   # <-- or financial-pulse-grasshopper / -mercury / -ramp
  skill="ceo-todo"         # <-- the folder it ships in, per the paragraph above

  # Each name is checked on its own. Testing "$agent$skill" would only catch an
  # empty value when BOTH were empty, so an empty $agent with a real $skill
  # sailed through.
  for name in "$agent" "$skill"; do
    case "$name" in
      ""|.|..|*/*|-*|*[!A-Za-z0-9._-]*)
        echo "Set agent and skill to plain names, e.g. ceo-todo-daily / ceo-todo" >&2; exit 1 ;;
    esac
  done

  mkdir -p "$HOME/.claude/agents"
  cp "$HOME/.claude/skills/$skill/agents/$agent.md" "$HOME/.claude/agents/$agent.md"
  echo "Installed agent to $HOME/.claude/agents/$agent.md"
)

The fastest path is skillsandagents.co — every skill's catalog page will generate this exact pinned command for you, copy-paste ready, once the catalog site adopts the manifest this repo now publishes. Until then it still generates the older single-file command, so the command above is the one to use by hand in the meantime.