sdk-tool-inventory

Validate loaded Copilot SDK tools and skills against declared configuration.

3|5|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ronniegeraghty/hyoka --skill sdk-tool-inventory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdk-tool-inventory
Source: https://github.com/ronniegeraghty/hyoka/tree/main/.squad/skills/sdk-tool-inventory
Command: npx skills add https://github.com/ronniegeraghty/hyoka --skill sdk-tool-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Introspects what tools, skills, and MCP servers were actually loaded into a Copilot SDK session, enabling guards and validation against the declared configuration.

Core Features & Use Cases

  • Inventory verification: verify the set of loaded skills, MCP servers, and tools matches the intended configuration.
  • Diagnostics and reporting: surface load status in reports and tests, facilitating debugging when agents have reduced capabilities.
  • Guardrails and testing: enables tests that assert tool availability and triggers alerts if expected tools are missing.

Quick Start

Run a Copilot session and observe the SessionEvents to verify loaded skills and MCP servers against the declared configuration.

Frequently Asked Questions about sdk-tool-inventory

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

FAQPage Schema
How do I verify which tools and skills are loaded in a Copilot SDK session?

To verify loaded tools and skills in a Copilot SDK session, parse session events to cross-reference the loaded inventory against your declared configuration. This process identifies missing tools and validates that MCP servers match the intended setup.

Why does my Copilot agent have reduced capabilities during a session?

Reduced capabilities in a Copilot agent often occur when expected tools are missing from the loaded inventory. Running a diagnostic validation cross-references session events with declared configuration to surface missing tool warnings and identify the gap.

Can I set up guardrails to test tool availability in Copilot sessions?

Yes, you can establish guardrails and testing protocols to assert tool availability in Copilot sessions. By validating the loaded tool inventory against declared configuration, tests trigger alerts if expected MCP servers or skills are missing.

What is the best way to diagnose missing MCP servers in a Copilot session?

The best way to diagnose missing MCP servers is to introspect session events and cross-reference them with your configuration. This validation surfaces load status reports and produces missing tool warnings for accurate debugging.

How do I validate tool inventory across multiple Copilot sessions?

You validate tool inventory across multiple Copilot sessions by parsing session events for skills and MCP reports. Cross-referencing these events against the declared configuration provides diagnostic reports and missing tool warnings for each session.

Do I need additional dependencies to check tool availability in Copilot SDK?

No additional dependencies are required to check tool availability in the Copilot SDK. The validation process directly parses session events to cross-reference loaded skills and MCP servers against the intended configuration and output warnings.