do-shared

Consolidate MCP capability registry and dynamic discovery for do-* skills.

28|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/fabio-barboza/development-orchestrator --skill do-shared
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-shared
Source: https://github.com/fabio-barboza/development-orchestrator/tree/main/skills/do-shared
Command: npx skills add https://github.com/fabio-barboza/development-orchestrator --skill do-shared

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes MCP capability registry and discovery instructions used by execution skills, ensuring consistent routing and reuse of capabilities across do-* workflows.

Core Features & Use Cases

  • Single source of truth for MCP capabilities and registries
  • Unified discovery flow mapping MCP servers to capabilities and tools
  • Service readiness guidelines to check, reuse, and start required services before MCP operations

Quick Start

Refer to do-shared/references/do-mcp-capabilities.md, do-shared/references/do-mcp-discovery-instructions.md, and do-shared/references/do-service-readiness.md to understand MCP capabilities, discovery steps, and service readiness.

Frequently Asked Questions about do-shared

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

FAQPage Schema
How do I centralize MCP capability discovery for multiple execution workflows?

You centralize MCP capability discovery by maintaining a shared registry that maps available MCP servers to their specific capabilities and tools. This provides a single source of truth for routing execution workflows and ensures consistent reuse of discovered capabilities.

What is an MCP capability registry and when do I need one?

An MCP capability registry is a centralized reference listing available MCP servers, their tools, and supported operations. You need one when orchestrating multiple execution skills that must dynamically locate and route tasks to appropriate MCP servers based on required capabilities.

How do I check MCP service readiness before running automation tasks?

Check MCP service readiness by verifying that required services are active and reachable before executing operations. Apply service readiness guidelines to check, reuse, or start necessary services, enabling graceful error handling when MCPs are unavailable.

Can I use a shared MCP registry across different execution flows?

Yes, a shared MCP registry applies across different execution flows such as task execution, QA, and review workflows. It enforces a consistent reference for capabilities and discovery procedures, allowing all flows to locate appropriate MCP servers uniformly.

How do I handle MCP servers becoming unavailable during orchestration?

Handle unavailable MCP servers by applying service readiness checks before operations begin. The shared registry enforces graceful handling of missing capabilities, allowing execution flows to degrade safely or route to alternative MCP servers when needed.