القائمة
Use when working in a persistent-slot workspace that uses docko. Covers slot claims, delegated teammate inheritance, and the rule that code edits inside slots/ require an active claim.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Runtime adapter guidance for the docko repository. Use when working on runtime-specific packages, template installers, hook flows, snippet assets, runtime documentation, or when extending support beyond the current Claude Code adapter.
Documentation and docs-sync guidance for the docko repository. Use when editing README, docs, examples, snippets, onboarding guides, or public positioning so the written guidance stays aligned with the implemented protocol and adapters.
Protocol, schema, and CLI contract guidance for the docko repository. Use when changing registry or session shapes, claim and delegation behavior, stale cleanup, authorization, or the public CLI behavior that reflects those semantics.
Repository onboarding and working conventions for the docko monorepo. Use when an agent needs to understand the repo layout, choose the right docs or commands, plan a change, or verify work without crossing the core, cli, adapters, docs, and tests boundaries.
| name | workspace-orchestration |
| description | Use when working in a persistent-slot workspace that uses docko. Covers slot claims, delegated teammate inheritance, and the rule that code edits inside slots/ require an active claim. |
Use this skill whenever work touches files in slots/ or when the user asks about workspace coordination.
/dock-status or docko status --root . --brief.docko slot acquire --root . --branch <branch> --task "<task>" --brief when you want docko to choose the next available slot using round-robin selection.docko claim --root . --resource slot --id <slot> --branch <branch> --task "<task>" only when you already know the exact slot.docko release --root . --resource slot --id <slot>Prefer slash commands when installed:
/dock-status/dock-claim <slot> <branch> <task>/dock-heartbeat <slot>/dock-release <slot>slots/*.AMBIGUOUS_SESSION, retry with an explicit --session <id> from docko session list --root . --brief; do not end existing sessions unless the user asked for cleanup.--clone-when-busy to docko slot acquire.docko is not runnable, check DOCKO_BIN. If it still fails, stop and tell the user.docko/registry.json during normal work.