Mininglamp-OSS

Docs domain — create and govern documents, read and incrementally edit a doc's live body, read and batch-edit spreadsheet cells (with paged reads for large sheets), read and batch-edit whiteboard scenes, members and sharing, inline comments, versions/snapshots, and attachment metadata as a bot. Load after octo-shared.

File operations (upload/download, presigned S3 credentials) plus bot housekeeping (register, set-commands, user-info, space-members, typing, heartbeat). Load after octo-shared.

Matter (todo/task) domain — CRUD, status transitions, assignees, channels, timeline, and AI extract from chat messages. Load after octo-shared.

Messaging domain — send/edit/sync messages, read receipts, groups and threads (User Bot), and event polling. Covers App Bot DM-only constraints. Load after octo-shared.

Shared knowledge for using the octo CLI — authentication, multi-service config, output envelopes, universal flags, error handling, and common patterns. Load before invoking any octo domain skill.

Conversational cold-start advisor for Multica squads. Use this whenever the user wants to set up, configure, bootstrap, or onboard a Multica squad / team of agents — e.g. "帮我配置一个 multica 小队", "组建一个 multica 团队", "冷启动一个 squad", "建一队 agent", "set up a multica squad", "configure my squad", "onboard a team on multica", or just describes a team goal + rough roles and wants it stood up. The user only needs to describe (1) the squad's overall goal and (2) a rough team composition / division of labor; this skill clarifies the gaps through multi-turn conversation, then designs and (after approval) provisions the complete squad via the `multica` CLI: agents (with professionally authored instructions), each agent's skills, the squad with a leader, members with semantic roles, and squad-level instructions. Also triggers for incrementally updating / adding members to an existing squad. Trigger even if the user does not say the word "skill" — if they talk about standing up a Multica team, this is the entry point.

An OpenClaw loop-engineering standard built on octoim + octospec + octo-multica-cloud. A three-ring nested contract (orchestration / execution / verification) with a loop-uncheatable acceptance gate. Use when receiving a code-implementation / bug-fix / feature request, designing or reviewing cross-agent dispatch, or auditing whether a pipeline conforms to the loop standard. Triggers on "loop process", "engineering standard", "dispatch standard", "acceptance gate", "stop condition", "fake acceptance", "loop engineering". NOT for trivial one-line fixes / typos / pure config (use the trivial escape hatch and dispatch the implementer directly).

Call cloud multica (multica.imocto.cn) from octo via user-configured octo-multica-key secret. Generic/portable; onboarding guide + runtime discovery.

Run the octo-spec engineering flow from an octo chat message. A team member sends a plain-language coding request ("add X to repo Y" / "fix bug Z"); the bot onboards the repo to octo-spec if needed, runs Claude Code in headless mode through the 4-phase loop (Plan/Implement/Verify/Finish incl. learning reflow), opens a PR, and reports back in the thread. Use for octo coding requests that should produce a real PR without the user opening Claude Code. ACP-free, no multica dependency.

Use the FIRST time you bring the octospec engineering standard into a repo that does not have it yet — to onboard octospec / initialize octospec into a fresh checkout. Triggers on requests like "onboard octospec", "initialize octospec", "set up octospec here", "add the octo-spec standard to this repo", 在这个仓库接入 octospec, 启用 octo-spec 标准, 初始化 .octospec。 This is a one-time接入引导: copy the template, pin the global version, run the sync script, confirm the agent-instruction block landed, and self-check with lint. Once the repo already has a working `.octospec/`, stop using this skill — the day-to-day 4-phase flow is owned by the octospec-workflow skill instead.

Use when implementing a feature, fixing a bug, or making any non-trivial code change in this repository. Drives the octospec 4-phase engineering flow (Plan, Implement, Verify, Finish) so the change follows this repo's rules in .octospec/ and ships a PR with a linked spec. Triggers on requests like "add ...", "implement ...", "fix ...", "refactor ...", "change the ... API", 写功能, 修 bug, 加接口, 改逻辑. Skip for trivial edits (typo, docs, lint, pure config) — those do not need the flow.

Use when implementing a feature, fixing a bug, or making any non-trivial code change in this repository. Drives the octospec 4-phase engineering flow (Plan, Implement, Verify, Finish) so the change follows this repo's rules in .octospec/ and ships a PR with a linked spec. Triggers on requests like "add ...", "implement ...", "fix ...", "refactor ...", "change the ... API", 写功能, 修 bug, 加接口, 改逻辑. Skip for trivial edits (typo, docs, lint, pure config) — those do not need the flow.

Octo Bot API 文档。消息发送、群管理、Thread、文件上传、User API 等接口。API 基础地址从 OpenClaw 配置 channels.octo.accounts.<id>.apiUrl 获取。

Octo Bot API 文档。消息发送、群管理、Thread、文件上传、User API 等接口。API 基础地址通过环境变量 OCTO_API_URL 注入。

OCTO 项目 OpenAPI / swag endpoint 设计、实现、审查、修改、接入工具链。触发场景： - **加 / 改 / 审查 endpoint**："加一个 X 接口" / "设计 API" / "审查这个 endpoint" → 读 `references/api-spec.md`，按工作流走，跑 `make openapi-check`；改 endpoint 时跑 `make openapi-diff` 看 breaking - **接入新仓库**："给 X 仓库加入这套工具链" → 读 `references/adoption.md` - **工具命令咨询**："openapi-check 是什么" / "怎么跑 lint" → 读 `references/toolchain.md` 范围：API 形态（URL / schema / 错误码 / swag）+ 本地校验。**不在范围**：handler 业务实现、部署、contract test。