/ Directory / Playground / ai-skills
● Community sanjay3290 ⚡ Instant

ai-skills

by sanjay3290 · sanjay3290/ai-skills

General-purpose agent skill collection for AI coding assistants — a sampler set covering everyday dev tasks.

sanjay3290/ai-skills is a general-purpose skill collection — smaller and less specialized than category-specific libraries, but handy as a sampler of common dev workflows packaged as installable skills. Works with any SKILL.md-compatible assistant.

Why use it

Key features

Live Demo

What it looks like in practice

ai-skill.replay ▶ ready
0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "ai-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/sanjay3290/ai-skills",
        "~/.claude/skills/ai-skills"
      ],
      "_inferred": true
    }
  }
}

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

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "ai-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/sanjay3290/ai-skills",
        "~/.claude/skills/ai-skills"
      ],
      "_inferred": true
    }
  }
}

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

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "ai-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/sanjay3290/ai-skills",
        "~/.claude/skills/ai-skills"
      ],
      "_inferred": true
    }
  }
}

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

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "ai-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/sanjay3290/ai-skills",
        "~/.claude/skills/ai-skills"
      ],
      "_inferred": true
    }
  }
}

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

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "ai-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/sanjay3290/ai-skills",
        "~/.claude/skills/ai-skills"
      ]
    }
  ]
}

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

~/.config/zed/settings.json
{
  "context_servers": {
    "ai-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/sanjay3290/ai-skills",
          "~/.claude/skills/ai-skills"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add ai-skill -- git clone https://github.com/sanjay3290/ai-skills ~/.claude/skills/ai-skills

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

Use Cases

Real-world ways to use ai-skills

How to sample a few general-purpose skills without committing to a framework

👤 Developers exploring what agent skills feel like ⏱ ~30 min beginner

When to use: You want to try 3-5 skills in a day before investing in a bigger library.

Prerequisites
  • Skill installed — git clone https://github.com/sanjay3290/ai-skills ~/.claude/skills/ai-skills
Flow
  1. List
    List every skill in ai-skills with a one-line what-it-does.✓ Copied
    → Inventory
  2. Try a few
    Pick 3 that look useful to a TypeScript dev and walk me through trying each.✓ Copied
    → Demo runs

Outcome: A feel for which skills you'd keep, which you'd drop.

Pitfalls
  • Skills stale relative to newer library versions — Check SKILL.md last-modified; skip ones >6 months old on fast-moving frameworks
Combine with: awesome-llm-skill

Cherry-pick one skill and keep the rest out of your folder

👤 Developers with a curated skills folder ⏱ ~10 min beginner

When to use: You only want one specific skill from the pack.

Flow
  1. Identify the one
    Which skill in ai-skills covers generating unit tests for existing code?✓ Copied
    → Specific skill name + folder
  2. Symlink only that
    Symlink that folder into ~/.claude/skills and leave the rest out.✓ Copied
    → Single skill installed

Outcome: Minimal footprint.

Combinations

Pair with other MCPs for X10 leverage

Use this as a sampler, then graduate to the bigger awesome-llm library

Try 3 skills from ai-skills, then move to awesome-llm-skills for broader coverage.✓ Copied
ai-skill + filesystem

Use filesystem MCP to scan your project, then have ai-skills generate tests or review code in-context

Read all files in src/, then use ai-skills' test scaffolding to generate unit tests for the untested modules.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
Code review patterns - PR review Claude tokens
Refactor helpers - Cleanup tasks Claude tokens
Test scaffolding - Coverage work Claude tokens

Cost & Limits

What this costs to run

API quota
None
Tokens per call
Varies per skill
Monetary
Free
Tip
Don't load all skills; pick the few you need.

Security

Permissions, secrets, blast radius

Credential storage: No credentials
Data egress: None by default

Troubleshooting

Common errors and fixes

Skill SKILL.md path nested too deep

Move individual skill folders up so SKILL.md sits at ~/.claude/skills/<name>/SKILL.md

Verify: ls ~/.claude/skills/*/SKILL.md
Skill not recognized by Claude Code after install

Restart Claude Code session — skills are loaded at startup, not hot-reloaded

Verify: Ask Claude to list available skills
Generated tests reference wrong testing framework

Specify the framework explicitly in your prompt (e.g. 'use pytest' or 'use jest') — the skill defaults may not match your project

Alternatives

ai-skills vs others

AlternativeWhen to use it insteadTradeoff
awesome-llm-skillYou want a broader, more actively-maintained catalogMore skills to sift
marketplace-skillYou want vetted skills onlySmaller catalog

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills