Agent skill · Workflow & Productivity

mcp-mastery

Complete MCP tool reference and usage patterns. Load this skill to become an expert in all 80+ GoodVibes MCP tools. Use when you need to understand tool capabilities, find the right tool for a task, or learn proper tool invocation patterns.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill mcp-mastery-mgd34msu-goodvibes-plugin --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 14 KB
Bundled scripts: none
Path: skills/ai-llm/mcp-mastery-mgd34msu-goodvibes-plugin/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# MCP Tool Mastery Master the 80+ MCP tools available in the GoodVibes plugin. This skill teaches you when and how to use each tool for maximum effectiveness. ## THE LAW: Tool-First Development **This is non-negotiable. Violating these rules means you're not doing your job.** ### Before ANY Task ```bash # 1. ALWAYS check tool schema first mcp-cli info plugin_goodvibes_goodvibes-tools/<tool_name> # 2. THEN make the call mcp-cli call plugin_goodvibes_goodvibes-tools/<tool_name> '{"param": "value"}' ``` ### The Golden Rules 1. **Never skip `mcp-cli info`** - Schemas are tool-specific. Your assumptions are wrong. 2. **Never do manually what a tool can do** - If a tool exists, use it. 3. **Skills contain expertise you lack** - Load them to become an expert. 4. **Tools provide current information** - Your training data is outdated. --- ## Quick Reference: Tool Selection by Task ### Starting Any Task | First Action | Tool | Command | |--------------|------|---------| | Understand project | `detect_stack` | `mcp-cli call .../detect_stack '{}'` | | Find relevant skills | `recommend_skills` | `mcp-cli call .../recommend_skills '{"task": "..."}'` | | Check for issues | `project_issues` | `mcp

What's inside
Steps it walks through
  1. THE LAW: Tool-First Development
  2. Before ANY Task
  3. The Golden Rules
  4. Quick Reference: Tool Selection by Task
  5. Starting Any Task
  6. Before Writing Code
  7. During Code Navigation
  8. Before Editing Code
  9. After Editing Code
  10. Debugging
  11. Security & Quality
  12. Complete Tool Catalog
  13. Discovery & Search (6 tools)
  14. Dependencies & Stack (6 tools)
Ships with 1 file
  • metadata.json
Commands it runs
mcp-cli info plugin_goodvibes_goodvibes-tools/<tool_name>
mcp-cli call plugin_goodvibes_goodvibes-tools/<tool_name> '{"param": "value"}'
WRONG - Never do this
mcp-cli call plugin_goodvibes_goodvibes-tools/detect_stack '{}'
CORRECT - Always check schema first
mcp-cli info plugin_goodvibes_goodvibes-tools/detect_stack
Read the schema output
Check all schemas in parallel
mcp-cli info plugin_goodvibes_goodvibes-tools/scan_patterns
mcp-cli info plugin_goodvibes_goodvibes-tools/project_issues
More from claude-skill-registry
All skills →
About this skill
What does the mcp-mastery skill do?

Complete MCP tool reference and usage patterns. Load this skill to become an expert in all 80+ GoodVibes MCP tools. Use when you need to understand tool capabilities, find the right tool for a task, or learn proper tool invocation patterns.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill mcp-mastery-mgd34msu-goodvibes-plugin --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going