# qaskills [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/PramodDutta/qaskills  
**GitHub Stars:** 245  
**npm Downloads (last month):** 500  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/qaskills

## Description
Search, inspect, and install 400+ QA testing skills from qaskills.sh into any MCP client.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "qaskills": {
    "command": "npx",
    "args": ["-y","@qaskills/cli"]
  }
}
```

## Documentation

## What qaskills MCP server does

The qaskills MCP server connects an MCP-compatible coding agent to the qaskills.sh QA skills directory. It gives the agent a way to discover testing guidance instead of requiring the developer to browse the website or manually copy skill files. The catalog covers areas including end-to-end, API, unit, performance, security, accessibility, mobile, contract, load, and CI/CD testing.

The available catalog includes skills such as Playwright E2E Testing, Cypress E2E Testing, Jest Unit Testing, Pytest Patterns, OWASP Security Testing, k6 Performance Testing, Appium Mobile Testing, and Bug Report Writing. The repository also documents curated packs for broader combinations, including a Playwright-focused pack and an API testing toolkit.

## How it works

An MCP client starts the package with npx and communicates with it over the standard MCP process configuration. The agent can then call six tools:

- `search_skills` finds skills by query.
- `get_skill` retrieves information about a selected skill.
- `get_skill_content` reads the skill's content.
- `install_skill` installs a selected skill for the agent.
- `list_categories` returns available skill categories.
- `get_leaderboard` retrieves leaderboard information.

Installing a skill places its `SKILL.md` in the appropriate agent configuration directory. The repository describes the related CLI as detecting the active AI agent and choosing the correct location. The MCP server is intended for searching and installing from inside the agent rather than for running the tests itself.

## Setup and configuration

For Claude Code, add the server with:

```bash
claude mcp add qaskills -- npx -y @qaskills/mcp
```

Other MCP clients can use an equivalent stdio entry:

```json
{
  "mcpServers": {
    "qaskills": {
      "command": "npx",
      "args": ["-y", "@qaskills/mcp"]
    }
  }
}
```

The README specifically shows Cursor and Windsurf as examples of clients that can use this configuration. No environment variables or external service credentials are documented as required. The package is run on demand through npm's `npx` command.

## Tools and capabilities

The qaskills MCP server is suited to agents that need to identify a relevant QA pattern, inspect its instructions, and install it into the current coding-agent environment. For example, an agent can search for API testing, inspect a Playwright skill, and install it before generating tests. Category and leaderboard tools support browsing beyond a single keyword search.

The broader QASkills project also provides a command-line interface with commands for searching, listing installed skills, adding skills, and removing them. Those CLI commands are separate from the six MCP tools, so teams should choose the MCP package when they want agent-driven access through an MCP client.

## Limitations and notes

Installing a skill supplies instructions to the coding agent, but does not install Playwright, Cypress, Selenium, or another testing framework. The README names support for multiple AI agents, while this listing only documents the MCP setup directly for Claude Code and generic MCP configuration examples for Cursor and Windsurf.

_Full upstream README: https://allmcps.com/mcp/qaskills/readme_