discovery
Skill and MCP tool discovery guide — teaches agents how to find skills and tools.
Best use case
discovery is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Skill and MCP tool discovery guide — teaches agents how to find skills and tools.
Teams using discovery should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/discovery/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How discovery Compares
| Feature / Agent | discovery | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Skill and MCP tool discovery guide — teaches agents how to find skills and tools.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## Skills & Discovery **Skills** -- context-aware prompts for common workflows. - Browse: `list_skills()` on `gobby-skills` - Load: `get_skill(name="skillname")` on `gobby-skills` - Hubs: `search_hub(query)` on `gobby-skills` **MCP Tools** -- progressive disclosure: 1. `list_mcp_servers()` -- discover servers 2. `list_tools(server)` -- discover tools 3. `get_tool_schema(server, tool)` -- get params 4. `call_tool(server, tool, arguments)` -- execute
Related Skills
project-discovery
Systematic project orientation for unfamiliar codebases. Automatically activates when Claude detects uncertainty about project state, structure, or tooling. Analyzes git state (branch, changes, commits), project type (language, framework, structure), and development tooling (build, test, lint, CI/CD). Provides structured summary with risk flags and recommendations. Use when entering new projects or when working on shaky assumptions.
progressive-discovery
Progressive disclosure pattern for MCP tools and skills. Teaches agents just-in-time discovery to minimize token usage.
product-discovery
Conducts discovery sessions for features/products. Explores concept definition, business model, user journeys, competitive analysis, scoping decisions, and data modeling. Use when you need to explore "what is X", "let's understand", "discovery for", or the /discovery command.
customer-discovery
Find where potential customers discuss problems online and extract their language patterns. Provides starting points for community research, not exhaustive coverage.
code-discovery
Helpers to discover, rank, and invoke repository symbols from natural language with minimal context.
blueprint-discovery
Discovery phase for blueprint workflow - interview triggers, acceptance criteria, and feature classification
ae-sdd-discovery
Discover high-level architectural requirements for change-set specs
api-documentation-discovery
Use when APIs fail repeatedly with version-related errors (method not found, wrong arguments, unknown flag) or when about to use library APIs with uncertain knowledge - guides finding current, accurate documentation instead of guessing from training data
guid-universal-technology-discovery
Discover and identify any technology, framework, or system without prior knowledge. Analyzes files, configurations, dependencies, and usage patterns to understand project technology stack from C source files to Kubernetes manifests.
skills-discovery
Search for and install Agent Skills that give you specialized capabilities. Before starting work, ask might a skill exist that handles this better than my base knowledge? If the task involves specific technologies, frameworks, file formats, or expert domains. Search proactively, even if the user doesn't mention skills. Skills encode best practices, tools, and techniques you wouldn't otherwise have. Also use when users explicitly ask to find, install, or manage skills.
project-context-discovery
Discover project structure, package managers, test frameworks, and automation without hardcoded assumptions
discovery-interview
Deep interview process to transform vague ideas into detailed specs. Works for technical and non-technical users.