/ Directory / Playground / oaustegard/claude-skills
← All servers ↗ GitHub
● Community oaustegard ⚡ Instant

oaustegard/claude-skills

by oaustegard · oaustegard/claude-skills

One marketplace repo that ships the same skills to both Claude Code (via /plugin) and Claude.ai (via ZIP upload) with semver releases.

oaustegard/claude-skills is a Claude Code plugin marketplace that doubles as a distribution channel for Claude.ai. Each skill is published as a SKILL.md + assets; Claude Code users add the marketplace with one command and then /plugin install specific skills, while Claude.ai Pro/Team users download release ZIPs and upload them via Skills Settings. Built with an automated PR workflow for ZIP uploads and CI/CD hooks so teams can integrate the marketplace into their repos.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Live Demo

What it looks like in practice

oaustegard-claude-skills.replay ▶ ready
0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "oaustegard-claude-skills": {
      "command": "claude",
      "args": [
        "plugin",
        "marketplace",
        "add",
        "oaustegard/claude-skills"
      ],
      "_inferred": false
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "oaustegard-claude-skills": {
      "command": "claude",
      "args": [
        "plugin",
        "marketplace",
        "add",
        "oaustegard/claude-skills"
      ],
      "_inferred": false
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "oaustegard-claude-skills": {
      "command": "claude",
      "args": [
        "plugin",
        "marketplace",
        "add",
        "oaustegard/claude-skills"
      ],
      "_inferred": false
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "oaustegard-claude-skills": {
      "command": "claude",
      "args": [
        "plugin",
        "marketplace",
        "add",
        "oaustegard/claude-skills"
      ],
      "_inferred": false
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "oaustegard-claude-skills",
      "command": "claude",
      "args": [
        "plugin",
        "marketplace",
        "add",
        "oaustegard/claude-skills"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json
{
  "context_servers": {
    "oaustegard-claude-skills": {
      "command": {
        "path": "claude",
        "args": [
          "plugin",
          "marketplace",
          "add",
          "oaustegard/claude-skills"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add oaustegard-claude-skills -- claude plugin marketplace add oaustegard/claude-skills

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use oaustegard/claude-skills

Add the marketplace to Claude Code and install a skill

👤 Claude Code users who want curated skills without hunting repos ⏱ ~5 min beginner

When to use: You want to try one of the skills and keep them updatable.

Prerequisites
  • Claude Code installed — https://claude.com/claude-code
Flow
  1. Register the marketplace
    /plugin marketplace add oaustegard/claude-skills✓ Copied
    → Marketplace listed in /plugin marketplace
  2. Browse and install
    /plugin install <skill-name>@oaustegard-claude-skills✓ Copied
    → SKILL appears under the active skills list
  3. Verify activation
    Ask Claude to do a task the skill targets; confirm it activates.✓ Copied
    → Skill-specific behavior observable in the response

Outcome: A working installed skill with a clear upgrade path.

Pitfalls
  • Installing without reading the SKILL.md — you get behavior you didn't expect — Read the marketplace page for each skill before /plugin install
Combine with: claude-skill

Provision the same skills across a team via CI/CD

👤 Eng leads / platform teams standardizing AI tooling ⏱ ~30 min intermediate

When to use: You want every dev on the team to get the same skills without manual setup.

Prerequisites
  • Repo with a .claude/ config directory — Create one at repo root if missing
Flow
  1. Pin the marketplace in .claude/settings.json
    Edit .claude/settings.json to auto-add the marketplace for this repo.✓ Copied
    → New contributors' Claude Code adds it automatically
  2. Pick the skill set
    List the skills you want installed repo-wide.✓ Copied
    → Small, reviewable list
  3. Automate via the installer
    Run the provided bash installer in CI to pin versions per repo.✓ Copied
    → Deterministic skill set checked into repo config

Outcome: Every teammate's Claude Code behaves consistently — no more 'works on my IDE'.

Pitfalls
  • Auto-installing a skill with heavy side effects without opt-in — Default off, opt-in per developer for anything that writes or calls out
Combine with: agent-skills-cli-skill

Distribute a skill to Claude.ai users via release ZIPs

👤 Skill authors who want both Claude Code and Claude.ai reach ⏱ ~45 min intermediate

When to use: You've built a skill and want it installable on the Claude.ai web/mobile app too.

Prerequisites
  • Fork or local copy of the marketplace repo — Follow the contribution workflow in README
Flow
  1. Add skill under the repo structure
    Open a PR with your skill folder and SKILL.md.✓ Copied
    → PR passes the marketplace's validation workflow
  2. Tag a release
    Tag 1.0.0; the workflow builds a ZIP.✓ Copied
    → Release with ZIP artifact
  3. Hand off to Claude.ai users
    Share the release URL; users upload via Skills Settings.✓ Copied
    → Skill shows up in users' Claude.ai workspace

Outcome: One source of truth, two distribution channels.

Pitfalls
  • Forgetting to bump SKILL.md metadata.version when tagging — Version in the file must match the git tag or users get stuck on old versions
Combine with: awesome-claude-skill

Combinations

Pair with other MCPs for X10 leverage

oaustegard-claude-skills + claude-skill

Learn the general skill authoring pattern and publish via this marketplace

Write a SKILL.md per the standard; publish it via the oaustegard marketplace release flow.✓ Copied
oaustegard-claude-skills + agent-skills-cli-skill

Use the CLI to lint and validate skills before publishing

Run agent-skills-cli on your SKILL.md before opening a PR.✓ Copied
oaustegard-claude-skills + awesome-claude-skill

Discover skills elsewhere and mirror/publish them with attribution

Check awesome-claude-skill for existing skills before reinventing.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
/plugin marketplace add marketplace: str Once, to subscribe to the marketplace 0
/plugin install <skill>@<marketplace> skill + marketplace To add a specific skill 0
bash installer skill list + target project Bulk/selective install per repo 0

Cost & Limits

What this costs to run

API quota
None
Tokens per call
Skills are local files, not API calls
Monetary
Free; Claude.ai ZIP upload requires Pro or Team
Tip
Keep individual skills focused; bundle-activations add up.

Security

Permissions, secrets, blast radius

Credential storage: No credentials in the marketplace itself
Data egress: Skills run locally; any network activity is up to the individual skill

Troubleshooting

Common errors and fixes

Marketplace not found

Confirm you typed 'oaustegard/claude-skills' exactly; ensure Claude Code is up to date.

Verify: /plugin marketplace list
Skill install succeeds but the skill never activates

Open the SKILL.md and check frontmatter 'description' — that's what triggers activation. Also ensure the skill is enabled in Claude settings.

Verify: head ~/.claude/skills/<skill>/SKILL.md
Claude.ai upload rejected

ZIP must contain SKILL.md at root. Re-zip from inside the skill folder, not the parent.

Verify: unzip -l release.zip | head

Alternatives

oaustegard/claude-skills vs others

AlternativeWhen to use it insteadTradeoff
claude-skillYou want to author one skill, not a marketplaceNarrower scope
awesome-claude-skillYou're browsing lists, not subscribing to a live marketplaceStatic curation vs live releases
skills-skillYou want a skill that helps you build skills, not distribute themDifferent part of the pipeline

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills