search-and-discovery

Search Meldoc documentation and map document relationships via backlinks.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/meldoc-io/mcp-stdio-proxy --skill search-and-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search-and-discovery
Source: https://github.com/meldoc-io/mcp-stdio-proxy/tree/main/.claude-plugin/skills/search-and-discovery
Command: npx skills add https://github.com/meldoc-io/mcp-stdio-proxy --skill search-and-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Meldoc documentation can be vast and interconnected; this skill helps users quickly locate, explore, and connect relevant docs to answer questions and audit coverage.

Core Features & Use Cases

  • Full-text search across Meldoc docs to locate relevant documents
  • Document tree navigation to understand hierarchy and context
  • Link and backlink discovery to map dependencies and connections
  • Documentation auditing to identify gaps and coverage

Quick Start

Ask the assistant to start a discovery session by exploring Meldoc docs about a topic and showing the top results with their relationships.

Frequently Asked Questions about search-and-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search across Meldoc documentation to find relevant docs?

Search Meldoc documentation by starting a discovery session to run full-text search, locate relevant documents, and display top results with their relationships.

What is the best way to map backlinks and dependencies in Meldoc docs?

Map backlinks in Meldoc docs by using link and backlink discovery to identify dependencies and connections across the knowledge base.

How do I navigate the Meldoc document tree to understand hierarchy?

Navigate the Meldoc document tree by using built-in navigation to explore document hierarchy, understand context, and map relationships across knowledge bases.

Can I audit Meldoc documentation to identify coverage gaps?

Audit Meldoc documentation by using auditing workflows to identify gaps and coverage across knowledge bases, enforcing structured interactions with frontmatter metadata.

Do I need frontmatter metadata to use Meldoc search and discovery?

Frontmatter metadata is required for Meldoc search and discovery, as the skill enforces structured interactions with Meldoc APIs and frontmatter to operate within contexts.