m8m-server-installer

Understand semantic M8M intake from local builders and adapt, install and verify MCP connections, workflows, reusable Tasks with ledger policy and inactive schedules on the authenticated tenant. Use f

SKILL.md

GitHub

M8M server installer

The server Codex session owns understanding and installation. Apply semantic input, structured output: read all supplied context, understand the requested behavior and the actual server standard, perform the installation work, and admit installation_plan, prepared_release, and installation_receipt.

Read the complete master prompt and the server standard. The worker pins and loads these instructions for the dedicated persistent installation Task. Incoming files are product context; authenticated tenant, grants and server standards come from the server tools.

Apply the matching trusted adaptation reference: MCP connection, Harness, Task, Schedule, or Ledger policy. Mixed intake can use several references. Ledger policy remains part of a Task template; live ledger rows are created in its launched Task.

Use only the m8m_installer tools for this Task. The granted tools provide isolated staging writes, rootless Linux builds and existing M8M installation operations. Ordinary chat does not gain installation authority.

Resolve existing workflow and Task-template references through the scoped find_workflows, inspect_workflow, find_task_templates and inspect_task_template installer tools. Paginate searches and inspect the selected exact identities before preparing bindings. Tenant and installation owner come from the claimed installation; uploaded names or principal fields cannot change that scope. Preserve explicit requested pins and retain ambiguity or readiness gaps as evidenced requirements.

For MCP use find_mcp_connections, inspect_mcp_connection and inspect_mcp_service. Only server-approved private service references resolve endpoints/authentication. Registration, requested consumer binding and harmless verification have separate member readbacks. Unsupported consumers and service deployment remain requirements.

Understand unfamiliar input and adapt it faithfully. Windows runtime bytes are development evidence; discover and prepare the actual Linux target. Inspect dependencies, binaries, entry points, prompts, graph, schemas, connection requirements, model declarations and intended external effects. Preserve originals and complete master prompts. Record implementation adaptations and verify their effects. Use available server capabilities to resolve failures.

Save durable evidence and stable member keys as work proceeds. On recovery, read the same installation and reconcile its saved members before new work. Separate installation, readiness, activation and execution evidence. Install schedules inactive. Start a business run or activate a schedule only when that specific action is authorized and supported by the server grant.

Finish through finish_installation; the tool composes its receipt from actual member readbacks. Return the exact final_reference that it supplies. A real missing capability or source produces an evidenced unresolved requirement. Do not manufacture installation receipts or substitute another tenant, account, model, workflow behavior or runtime pin to claim completion.