myco:myco-symbiont-integration

Guides development and debugging of Myco symbiont integrations across agents.

12|2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/goondocks-co/myco --skill myco-myco-symbiont-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: myco:myco-symbiont-integration
Source: https://github.com/goondocks-co/myco/tree/main/.agents/skills/myco-symbiont-integration
Command: npx skills add https://github.com/goondocks-co/myco --skill myco-myco-symbiont-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building and maintaining a robust Myco symbiont integration across agents, including manifest-driven capture, hook templates, and installer wiring, with solid lifecycle handling and debugging guidance.

Core Features & Use Cases

  • Declarative manifest-driven capture rules and domain-keyed schemas
  • Installer integration, skill discovery, and MCP tool verification
  • Runtime command redirection, portability fixes, and universal stop-buffer fallbacks
  • Session validation, scratchProbe usage, and phantom-session defenses

Quick Start

Implement a complete Myco symbiont integration guided by the manifest-driven workflow described.

Frequently Asked Questions about myco:myco-symbiont-integration

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

FAQPage Schema
How do I debug a Myco symbiont integration across different AI agents?

Debug a Myco symbiont integration by using manifest-driven capture rules and session validation. This workflow addresses hook templates, installer wiring, and runtime command redirection for agents like Claude, Codex, and Cursor.

What is manifest-driven capture and how does it work for symbiont integrations?

Manifest-driven capture uses declarative rules and domain-keyed schemas to record symbiont data. It provides a structured method to define what information is captured across different agent environments during integration.

Does Myco symbiont integration support portable MCP configuration for multiple agents?

Yes, Myco symbiont integration supports portable MCP configuration via registration.mcpCwd. This feature enables SDK-specific MCP behavior and tool verification to be applied consistently across Claude, Codex, Cursor, and OpenCode.

How do I handle lifecycle recovery and stop-buffer patterns in a symbiont integration?

Handle lifecycle recovery by implementing universal stop-buffer fallbacks and runtime command redirection. These patterns prevent data loss during session validation and defend against phantom sessions.

Why is my symbiont integration failing MCP tool verification during installer skill discovery?

MCP tool verification fails if the installer skill discovery process cannot validate registered tools against the manifest. Ensure your API-type verification discipline and installer wiring correctly match the SDK-specific MCP behavior.