rahmanef63/mso/mso-agent-bootstrap

/mso-agent-bootstrap — first-call map for every AI surface

MSO is one capability kernel with several presentations. ChatGPT, Cursor, the terminal mso agent, and Alfa-via-gateway all reach the same maximal host power. Compact schemas, dot.case Alfa names, and catalog-first terminal packs are presentation, not missing features.

Trigger and boundaries

• Use when: starting an MCP session, teaching an agent how MSO works, or choosing

the first tools before a mutation.

• Do not use when: a narrower official skill already matches (deploy, repo-work,

camoufox, integrations) and you already know the map.

• Required context: token scope (read/write/exec) and whether the project

id/path is already known.

Fast route

1. skills_search query mso-agent-bootstrap, or skills_read this id. ChatGPT may

already have the published copy; still prefer the live catalog when unsure.

1. projects_list if the project is unresolved. Honor scan.truncated.
2. workflow_start once for multi-step work; pass exact workflow_id thereafter.

Skip this on a read token. Do not call skills_search immediately before startup for the same task. If the user is continuing work from a dead/overlong conversation and did not provide a session id, call agent_session_resume with the project when known. It auto-selects the newest relevant unfinished workflow/session and returns a safe continuation recipe. Never ask the user to hunt for an MSO session id unless recovery is genuinely ambiguous or no matching durable state exists.

1. Project MCP: project_capabilities → project_mcp_tools → project_mcp_call.

Never fuse discover and call. Never copy project tool names into the global catalog.

1. Credentials: integration_query → private setup/verify → integration_execute.

Never put secrets in chat or tool arguments.

1. Prefer read_pipeline and bounded fs_*/sys_*/vps_status before exec_run.
2. Mutate infra only through bounded tools with confirm. Doctor/health first.

Then verify and workflow_finish, or workflow_cancel.

Surface tips

Tool routing

Hard constraints

Do not hide ChatGPT tools to compress context. Do not fuse project MCP discover/call. Do not put secrets in args. Keep read < write < exec. Reusing an index or recipe does not skip auth.

Full matrix: `docs/AGENT-BOOTSTRAP.md`.

Verification contract

• Expected state: the agent can name the next bounded tool for the task.
• Targeted checks: scope matches the tool; workflow_id is exact when required.
• Runtime proof: live GET /mcp toolset and a real call through the chosen path.
• Visual proof: screen_capture only when UI actually changed.
• Diff boundary: no unrelated refactors; no credential values in traces.

Failure and rollback

Stop when project identity or scope is ambiguous. Preserve the first error. Never force-push, dump ~/.mso, or treat a zero exit as proof.

Recipe memory

Save redacted steps only. Never persist file bodies, tokens, cookies, or secret-bearing argv. A failed run is evidence, not a replacement for a verified recipe.