Skills and MCP by task
For each task we gathered the catalog cards closest to it in meaning. Every card has an install command and an access level, and the number on a tile shows how many tools on the topic the catalog has.
Picks
- Security and pentest395 on the topicFor example: HACK.SKILLS, VulnClaw, SkillSpectorExtended for 2, broad for 10Access of the cards: Extended for 2, broad for 10
- DevOps1,598 on the topicFor example: kmcp, kubectl-mcp-server, DevOps AI ToolkitExtended for 2, broad for 10Access of the cards: Extended for 2, broad for 10
- QA and testing811 on the topicFor example: agent-qa, qa-skills, Test Automation Skills and AgentsMinimal for 1, extended for 8, broad for 3Access of the cards: Minimal for 1, extended for 8, broad for 3
- 1C development244 on the topicFor example: 1C MCP Toolkit, 1C Client MCP Server, MCP server inside 1CExtended for 6, broad for 6Access of the cards: Extended for 6, broad for 6
- Code reviewFor example: agentsre, agent-reviews, Code Review SkillsMinimal for 5, extended for 6, broad for 1Access of the cards: Minimal for 5, extended for 6, broad for 1
- UI design1,172 on the topicFor example: qiaomu-design, Superdesign, UI SkillsMinimal for 8, extended for 4Access of the cards: Minimal for 8, extended for 4
Your task is not listed
Describe the task in plain words or paste package.json. Foxx AI finds matching skills, MCP servers and CLI tools in the catalog and explains why it chose them.
FAQ
The whole catalog
Every card by type, agent and Russian service, with filters and sorting.
How are the picks built?
Each task has a demand description. Catalog cards are compared with it by meaning, and the closest ones make the pick. Picks are rebuilt automatically as new cards arrive.
Why do DevOps and security have many broad access cards?
These tools run commands on servers and clusters and change their settings, so their access is broad. The access level is on every card, and the rules are on the methodology page.
How is a pick different from a catalog section?
A section shows every card of one type, for example all MCP servers. A pick gathers different types for one task: skills, MCP servers and CLI tools together.