Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

docko-adapters

Étoiles1

Forks0

Mis à jour24 juillet 2026 à 17:51

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

4riel

4riel/docko

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	docko-adapters
description	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.

docko Adapters

Read first

docs/adapter-spec.md
docs/claude-code.md
packages/adapters/claude-code/src/index.ts
packages/adapters/claude-code/templates/
tests/claude-code-adapter.test.mjs
For Codex-specific wording, verify AGENTS.md, skills, subagents, and hooks claims against official OpenAI docs.

Reference model

Treat the Claude adapter as the reference implementation for installer structure, template layout, and runtime-to-protocol mapping.
Be explicit about what is implemented versus what is only documented or planned.
Claude Code is the only first-class Docko adapter today.
Codex guidance is currently manual and docs-driven. Do not imply a shipped Codex adapter unless this repo gains a package, templates, and tests for it.
OpenAI documents Codex hooks, including Windows-specific command and managed-directory fields. Do not present hooks as Docko's default Codex path until this repo ships and tests a dedicated Codex adapter.

Change rules

Keep adapters thin and avoid changing ownership semantics in adapter code.
Put runtime-specific templates, snippets, and helper assets beside the adapter that owns them.
Update templates, examples, docs, and tests together.
If runtime-specific commands are added to the CLI, document them in docs/cli-reference.md.
For Codex or OpenAI-specific guidance, verify against official OpenAI docs before writing instructions.
For future runtimes, keep design notes clearly labeled as future or guidance-only until implementation exists.

Verify

pnpm build
pnpm check
pnpm test
Focus on tests/claude-code-adapter.test.mjs plus any new adapter coverage when verification needs to be selective.

Plus depuis ce dépôt

même dépôt

workspace-orchestration

4riel/docko

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.

2026-07-241

docko-docs

4riel/docko

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.

2026-07-011

docko-protocol

4riel/docko

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.

2026-07-011

docko-repo

4riel/docko

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.

2026-07-011

name	docko-adapters
description	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.

docko Adapters

Read first

docs/adapter-spec.md
docs/claude-code.md
packages/adapters/claude-code/src/index.ts
packages/adapters/claude-code/templates/
tests/claude-code-adapter.test.mjs
For Codex-specific wording, verify AGENTS.md, skills, subagents, and hooks claims against official OpenAI docs.

Reference model

Treat the Claude adapter as the reference implementation for installer structure, template layout, and runtime-to-protocol mapping.
Be explicit about what is implemented versus what is only documented or planned.
Claude Code is the only first-class Docko adapter today.
Codex guidance is currently manual and docs-driven. Do not imply a shipped Codex adapter unless this repo gains a package, templates, and tests for it.
OpenAI documents Codex hooks, including Windows-specific command and managed-directory fields. Do not present hooks as Docko's default Codex path until this repo ships and tests a dedicated Codex adapter.

Change rules

Keep adapters thin and avoid changing ownership semantics in adapter code.
Put runtime-specific templates, snippets, and helper assets beside the adapter that owns them.
Update templates, examples, docs, and tests together.
If runtime-specific commands are added to the CLI, document them in docs/cli-reference.md.
For Codex or OpenAI-specific guidance, verify against official OpenAI docs before writing instructions.
For future runtimes, keep design notes clearly labeled as future or guidance-only until implementation exists.

Verify

pnpm build
pnpm check
pnpm test
Focus on tests/claude-code-adapter.test.mjs plus any new adapter coverage when verification needs to be selective.