If you already use Claude Code but still repeat “follow our PR template” every session, the highest-leverage layer in 2026 is Agent Skills: versioned SKILL.md workflows the agent loads on demand. We published a Skills repo roundup earlier this year; by October, official plugin packs, community lists, and companion GitHub tools matured further. This guide ranks what is worth installing, how to pair Skills with MCP, and how to run them on Mac or cloud Mac hosts.
What Skills are—and how they differ from prompts
A Skill is a folder with YAML frontmatter and SKILL.md. Claude Code reads name/description first, then loads the body only when relevant—progressive disclosure that beats stuffing runbooks into CLAUDE.md.
| Mechanism | Best for | Typical path |
|---|---|---|
| CLAUDE.md / AGENTS.md | Repo facts: build commands, layout | Repository root |
| Skills | Reusable workflows: release, audit, split PRs | ~/.claude/skills or .claude/skills |
| MCP | External tooling: issues, DBs, browsers | Client MCP config |
| Hooks | Deterministic automation after saves | .claude/settings.json |
Unlike Graphify + OpenCode structure memory, Skills answer how to do it right, not where code lives. Use both: query the graph, then invoke an iOS release checklist skill.
2026 tiered picks
Official and marketplace
anthropics/skills — still the default install via marketplace, not a blind full-repo clone:
/plugin marketplace add anthropics/skills
/plugin install document-skills@anthropic-agent-skills
/plugin install example-skills@anthropic-agent-skills
anthropics/claude-plugins-official — skill-creator for packaging team workflows. anthropics/claude-code plugin-dev skills — patterns for slash commands and CI-friendly agents.
Community GitHub
travisvn/awesome-claude-skills— discovery only; star and copy single skill dirs.developmentseed/skills— multi-IDE layout reference.agentskills/agentskills— spec source forallowed-toolsand interoperability.
.claude/skills + awesome lists for discoveryBeyond Skills: GitHub tools
anthropics/claude-code-action— run Claude Code in GitHub Actions; skills define review steps.- Usage CLIs (community) — e.g. token/session cost trackers to see which workflows burn quota.
- Team skill repos — submodule or monorepo path with PR review, better than manual scp to cloud Macs.
Install checklist
- Claude Code ≥ 2.1.
- Install document-skills + example-skills.
- Add
.claude/skills/<name>/SKILL.mdwith your build/release parameters. - Verify by listing skills in a repo session.
- On cloud Mac: persist
~/.claudeor rsync team skills on checkout.
Cursor Skills and MCP
Same Agent Skills standard: copy dirs to ~/.cursor/skills / .cursor/skills. Keep MCP for live APIs; keep long runbooks in Skills.
Governance
- One verb phrase per skill name; clear description triggers.
- Tighten
allowed-toolsfor risky shells. - PR-review team skills like code; retire unused skills quarterly.
FAQ
How many Skills should I install?
5–8 global, plus 2–3 project-specific. Start with official packs.
Can I git clone entire repos into ~/.claude/skills?
Prefer single skill subfolders or marketplace installs.
Skills vs MCP?
Skills = procedures; MCP = external systems.
Restart after edits on remote Mac?
2.1+ hot reload; persist skill paths on durable volumes.
Bottom line: install anthropics/skills and skill-creator first, use awesome lists to discover, team repos to govern, and claude-code-action plus cost CLIs to operationalize—fewer, sharper skills beat chasing every new GitHub repo.