Module install 

Resolved install payloads — what an adapter actually writes to disk.

These types are produced by the resolver (Step 6+) from a manifest DepSpec plus registry metadata, and consumed by adapter trait methods. Skill and McpServer are fleshed out for v0.1; the other primitives are opaque markers that get full schemas as each adapter step lands.

Structs

Command

Hook

McpServer

A resolved MCP server ready to install. The adapter writes the transport into the agent’s MCP config (e.g. .mcp.json for Claude Code).

Prompt

Skill

A resolved skill ready to install. Identity is owner/name@version; integrity covers the concatenated, sorted file contents (see compute_integrity).

SkillFile

One file inside a skill bundle (e.g. SKILL.md, reference/usage.md). The path is relative to the skill’s install root.

Subagent

Enums

McpTransport

How an MCP server is launched / reached. BTreeMap keeps env + headers in deterministic order for hashing and write-out.

Functions

compute_integrity

Compute an Integrity over a slice of skill files. Stable across runs and machines because files are sorted by relative path first.