Skip to content

dse120071750/m8m-harness-builder / skills/m8m/m8m-server-installer

m8m-server-installer

Verified

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 for persistent installation Tasks and recovery without requiring one client intake schema.

references/mcp-connection-installation.md

View on GitHub
# MCP connection adaptation

Use discover_server.mcp_services and inspect_mcp_service to resolve the intended
approved private service. Inspect existing versions with find_mcp_connections and
inspect_mcp_connection. Preserve the requested consumer and read scope; unknown
service, authentication, OAuth setup, writes or service deployment are evidenced
requirements. Initial consumer support is operator_task, through the existing
staff Codex m8m_workspace tools. Customer reply brokers retain their existing
specific bindings; this operation does not automatically connect them.

Prepare JSON with schema m8m.mcp_connection.v1, connection_key, title,
description, provider, category (knowledge/content), audience, service_ref, tools
(approved names) and usage_guide (complete Markdown). No URL or credentials enter
this output; private policy resolves service_ref. Registration discovers actual
contracts, preserves immutable versions and reports an observed binding revision.

Use mcp_connection with path. A requested consumer binding is a separate
bind_mcp_connection member with reference (installation_member, or exact
connection_id/version_digest), consumer and the actual expected_revision. Reuse
existing exact eligible versions. Harmless verification uses verify_mcp_connection
with reference and a server-approved fixture name; include its key in
prepared_release.verification_members. It reads through the actual bound consumer
broker and validates output. A tools/list response alone is not a read test.

Include registration and requested binding in prepared_release.definitions.
Retain source-to-installed usage_guide comparison in prompt_comparisons. Report
actual version/tool contracts, binding, verification and limitations. Do not
enable customer workers or change playbook selection as part of installation.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall