Openmaic

clarify language field accepts only zh-CN | en-US; update stale enableTTS description to reflect actual server-side TTS capability

- Major update: Introduces a full SOP-style, phase-based guided setup and usage flow for OpenMAIC, handling both hosted and local modes. - Adds new reference files for cloning, flow, startup modes, provider keys, and hosted mode to structure step-by-step guidance. - Now enforces explicit confirmation before all state-changing actions, progressing only one phase at a time. - Integrates support for optional skill config, defaults, and local/hosted mode decision logic. - Moves all credential handling to server-side configs and guides the user without requesting keys in chat or offering to write configs. - Refines response style: shorter steps, explicit options, and a clear summary after each completed action.

- Major simplification: Replaced detailed step-by-step SOP with a concise, direct guide for generating AI-powered interactive classrooms. - Removed all in-depth setup, confirmation phases, and config instructions. - Skill now activates via natural language triggers (e.g., "teach me", "generate classroom", "上课"). - Workflow: Collect topic requirements, generate a classroom, monitor progress, and share the classroom link. - Language can be specified (defaults to Chinese). - Basic error handling added: explain failures and offer to help refine user requests.

Security: access codes are now read from skill config file (~/.openclaw/openclaw.json) instead of being pasted into chat. Skill auto-detects stored access code and skips mode selection. Users are guided to edit the config file for credential setup.

Add hosted mode: users with an access code from open.maic.chat can skip local setup and generate classrooms directly via the hosted API. Includes Phase 0 mode selection, Bearer token auth, independent quota (10/day), and error handling guidance.

Initial release of the OpenMAIC skill, providing a guided, confirmation-based SOP for setup and classroom generation: - Guides users step-by-step through cloning or selecting the OpenMAIC repo, selecting a startup mode, and configuring provider API keys. - Enforces explicit confirmation before any state-changing actions. - Directs users to edit local config files themselves—never asks for API keys to be pasted into chat. - Includes clear instructions for starting OpenMAIC, verifying service health, and generating classrooms from requirements or PDFs. - Utilizes local OpenClaw config defaults if present, but always confirms actions with the user. - Outlines response and confirmation practices for a safe, user-involved setup flow.