OpenMAIC Skill

Use this as a guided, confirmation-heavy SOP. Do not compress the whole setup into one reply and do not perform state-changing actions without explicit user confirmation.

Core Rules

• Move one phase at a time.
• Before any state-changing action, ask for confirmation.
• If local state already exists, show what you found and ask whether to keep it.
• Do not assume the OpenClaw agent's own model or API key will be reused by OpenMAIC.
• OpenMAIC classroom generation uses OpenMAIC's server-side model configuration (openmaic.yml and the model settings in the web app).
• This skill must not rely on any request-time model or provider overrides.
• Only that server-side configuration may control provider selection and defaults.
• Do not default to asking the user to paste API keys into chat.
• Prefer guiding the user to edit local config files themselves.
• Do not offer to write API keys into config files on the user's behalf.
• Once setup is complete and the user clearly asks to generate a classroom, do not ask for a second confirmation before submitting the generation job.
• Keep confirmations for local file reads such as reading a PDF from disk before uploading it.

Optional Skill Config

If present, read defaults from ~/.openclaw/openclaw.json under:

{
  "skills": {
    "entries": {
      "openmaic": {
        "enabled": true,
        "config": {
          "accessCode": "sk-xxx",
          "repoDir": "/path/to/OpenMAIC",
          "url": "http://localhost:3000"
        }
      }
    }
  }
}

• If accessCode is present, default to Live Demo mode and skip the mode-selection prompt, unless the user's intent is to extend/build on OpenMAIC (see the exception in Phase 0).
• Use repoDir and url only as defaults for local mode.
• Still confirm before acting.

SOP Phases

0. Choose Mode