/ Directory / Playground / Skills-4-SE
← All servers ↗ GitHub
● Community ArabelaTso ⚡ Instant

Skills-4-SE

by ArabelaTso · ArabelaTso/Skills-4-SE

180+ task-oriented Claude Code skills across 8 packs covering the full software engineering lifecycle — bug fixing, testing, DevOps, formal verification, security.

Skills-4-SE is a curated collection of 180+ reusable skills organized into 8 packs: Bug Fixing, Code Quality, Test Automation, Requirements Engineering, Code Understanding, DevOps Automation, Formal Verification, and Security Scanner. Each skill documents inputs, outputs, failure modes, and eval criteria. Install packs individually or all at once.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Live Demo

What it looks like in practice

skills-4-se-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": {
    "skills-4-se-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/ArabelaTso/Skills-4-SE",
        "~/.claude/skills/Skills-4-SE"
      ],
      "_inferred": true
    }
  }
}

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

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

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

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

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

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

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

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "skills-4-se-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/ArabelaTso/Skills-4-SE",
        "~/.claude/skills/Skills-4-SE"
      ]
    }
  ]
}

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

~/.config/zed/settings.json
{
  "context_servers": {
    "skills-4-se-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/ArabelaTso/Skills-4-SE",
          "~/.claude/skills/Skills-4-SE"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add skills-4-se-skill -- git clone https://github.com/ArabelaTso/Skills-4-SE ~/.claude/skills/Skills-4-SE

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

Use Cases

Real-world ways to use Skills-4-SE

Install the Bug Fixing Suite for systematic defect triage

👤 Engineers dealing with a growing bug backlog ⏱ ~20 min beginner

When to use: You have unclear bug reports piling up and want Claude to reproduce, triage, and fix them with discipline.

Prerequisites
  • Clone the repo — git clone https://github.com/ArabelaTso/Skills-4-SE ~/.claude/skills/Skills-4-SE
Flow
  1. Install only the bug-fixing pack
    cd ~/.claude/skills/Skills-4-SE/skill-packs && ./install-packs.sh bug-fixing✓ Copied
    → 12 bug-fixing skills land in ~/.claude/skills/
  2. Point Claude at a failing report
    Use the bug-fixing skills: here's the report. Reproduce, isolate, propose a fix with tests.✓ Copied
    → Repro + failing test + patch, not a one-shot guess

Outcome: A discipline around bug work that survives across engineers.

Pitfalls
  • Installing all 180+ skills and watching context bloat — Install only the packs you're actively using; uninstall others
Combine with: git · filesystem

Run the Security Scanner Suite on a codebase

👤 Teams doing pre-release security reviews ⏱ ~40 min intermediate

When to use: Before shipping a release, or when onboarding a new repo.

Flow
  1. Install security pack
    ./install-packs.sh security-scanner✓ Copied
    → 13 security skills installed
  2. Run the audit flow
    Run the security-scanner suite on this repo — secret scanning, SAST, dependency audit, IaC config review.✓ Copied
    → Report with findings grouped by severity

Outcome: A repeatable pre-release security checklist driven by Claude.

Pitfalls
  • Treating findings as final without human review — The skills flag; humans triage. Keep a person on the other side.
Combine with: github

Turn a vague feature request into a written spec

👤 Tech leads turning 'we should add X' into something buildable ⏱ ~30 min intermediate

When to use: Early in a project, when the requirements are fuzzy.

Flow
  1. Install requirements pack
    ./install-packs.sh requirements-engineering✓ Copied
    → 12 requirements skills installed
  2. Use them on your feature idea
    Use requirements-engineering skills: 'we need a user dashboard'. Walk me through elicitation, acceptance criteria, and edge cases.✓ Copied
    → Questions back at you, then a structured spec

Outcome: A spec you can hand to an implementer without ambiguity.

Combine with: jira-skill

Combinations

Pair with other MCPs for X10 leverage

skills-4-se-skill + github

Run Security Scanner pack across an org's repos and open tracking issues for findings

Run security-scanner on each repo in org acme. Open a GitHub issue per high-severity finding.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
install-all-packs.sh none Rarely — prefer targeted packs 0
install-packs.sh pack name(s) Normal install path 0
install.sh from a single pack dir Inside a specific pack dir 0

Cost & Limits

What this costs to run

API quota
None
Tokens per call
Varies per skill — typically 2–10k per invocation
Monetary
Free, OSS
Tip
Install only packs you'll use — unused SKILL.md files still get surfaced to Claude's skill picker and eat tokens

Security

Permissions, secrets, blast radius

Credential storage: Skills themselves store no credentials; any that wrap APIs (e.g. security scanners) read from env
Data egress: None from the skill layer

Troubleshooting

Common errors and fixes

install.sh: permission denied

chmod +x install.sh before running

Verify: ls -l install.sh
Too many skills loaded, context full

Remove packs you don't use: rm -rf ~/.claude/skills/<pack>

Verify: ls ~/.claude/skills/

Alternatives

Skills-4-SE vs others

AlternativeWhen to use it insteadTradeoff
clawfu-skillsYou want marketing skills instead of engineeringDifferent domain
DSkillsYou want fewer, sharper CLI-oriented skillsMuch smaller surface

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills