mcp-discovery SKILL.md skillC

mcp-discovery from opensesh/design-ops is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add opensesh/design-ops/mcp-discovery@git:20260419.8b28338

Pins git:20260419.8b28338 in mdr.lock. Pin the fingerprint instead.

Audit grade
C, 14 of 17 checks passed
Kind
SKILL.md skill
Repository
opensesh/design-ops
Path
skills/mcp-discovery/SKILL.md
Versions recorded
3
Latest version
git:20260419.8b28338, committed Apr 19, 2026
First version recorded
Apr 17, 2026
Size
15,242 bytes
Repository stars
23
License
Apache-2.0

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# MCP Discovery Skill

Dynamic MCP package discovery at runtime. Instead of relying on a static registry, this skill verifies MCP availability by querying npm, GitHub, and vendor documentation.

## Purpose

When a user selects a tool during `/design-ops:setup`, this skill discovers the best connection method:
1. Check for official/vendor MCPs
2. Evaluate community packages (with quality metrics)
3. Find API documentation for direct integration
4. Return a recommendation with confidence level

## Why Dynamic Discovery?

- 100+ potential tools across operations/design/analytics
- Static registries become stale immediately
- New MCPs are published constantly
- Tool-agnostic design requires runtime discovery

---

## Trigger

Invoked by `tool-evaluator` skill during setup flow:

```yaml
skill: mcp-discovery
input:
  tool: "monday"
  pillar: "operations"
```

---

## Discovery Flow

```
User selects tool (e.g., "Monday.com")
           │
           ▼
┌─────────────────────────────────────────────────────────────┐
│  Step 1: Check Known Tools (fast path)                      │
│  - Look up in known_tools.yaml for common tools             │
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add opensesh/design-ops/mcp-discovery@sha256:a7cd7b9565dc2683

The line at the top of this page pins the label git:20260419.8b28338, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_caq3goy5l5b6tvag.svg)](https://markdownregistry.com/a/art_caq3goy5l5b6tvag)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 3 versions of this file, between Apr 17, 2026 and Apr 19, 2026, about one every day.

versioncommittedcommitsizeaudit
git:20260419.8b28338 latest2026-04-19 8b28338 15,242 BC view · diff
git:20260419.159a7c82026-04-19 159a7c8 15,242 BC view · diff
git:20260417.a569a342026-04-17 a569a34 13,119 BC view

Audit of the latest version

C  14 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • fail: Frontmatter block present
  • fail: Frontmatter declares a name
  • fail: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (15242 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

opensesh/design-ops · 23 stars · license Apache-2.0 · pushed 2026-10-13 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_caq3goy5l5b6tvag
GET https://markdownregistry.com/api/v1/resolve?ref=opensesh/design-ops/mcp-discovery
GET https://markdownregistry.com/api/v1/blob/a7cd7b9565dc2683e0ad9832ba27f8922c190c7e789e8b98f830f965ab9fda1a

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from opensesh/design-ops

brand-guidelines SKILL.md skill
opensesh/design-ops · skills/brand-guidelines/SKILL.md · Use when user mentions "brand", "Open Session colors", "Aperol", "Charcoal", "Vanilla", "brand guidelines", or works on…
v1.0.0 · audit A · 23 stars
design-system-quality SKILL.md skill
opensesh/design-ops · skills/design-system-quality/SKILL.md · Use when reviewing UI/frontend code, conducting PR reviews for components, checking design system compliance, or after…
v1.0.0 · audit A · 23 stars
frontend-design SKILL.md skill
opensesh/design-ops · skills/frontend-design/SKILL.md · Use when building UI components, making design decisions for frontend work, reviewing UI implementation quality, or…
v1.0.0 · audit A · 23 stars
tool-evaluator SKILL.md skill
opensesh/design-ops · skills/tool-evaluator/SKILL.md
git:20260417.4f9c495 · audit C · 23 stars

Every file in opensesh/design-ops

Browse by kind, by grade C, or by owner.