About dcode-runner
dcode-runner is an agent skill for running an explicitly requested prompt through the local dcode CLI. It emphasizes accurate provider attribution and checking execution receipts and fallback status.
Key features
- 01Run prompts through local dcode CLI
- 02Preserve provider attribution
- 03Inspect receipts and fallback status
Use cases
- 01Run a manually requested dcode task
- 02Verify which provider returned a result
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ robsonrung/ rar-skills --skill dcode-runnerAfter installing, type/dcode-runnerin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
agents/openai.yamlreferences/command-reference.mdcontinuation.mdruntime-reference.mdscripts/run_dcode.pytests/test_run_dcode.pyDetails
From the project READMEDcode Runner
Execute the caller's scoped prompt through the local CLI. Shared roles, envelope keys, and result handling live in shared/references/runner-common.md. Preserve seat fidelity: name the provider that actually answered, and report unavailable or unverified seats honestly.
Native routing
Read shared/references/host-model-execution.md before choosing an external route. If the current host can dispatch the exact selected model with the required effort, isolation, and receipt policy in a native subagent or task thread, use that route. agents/openai.yaml is host UI metadata; it does not dispatch a native model.
Invocation
Set SKILL_DIR to this loaded skill directory in the same shell call:
SKILL_DIR="<absolute path of this skill directory>";
python3 "$SKILL_DIR/scripts/run_dcode.py" "<scoped prompt>" --json
An approved workflow supplies the exact model, effort, role, tool mode, and receipt policy. Pass those approved options and --disable-fallback; this basic example does not authorize a different route.
Runtime boundaries
- Use only for an explicitly requested manual dcode run. This wrapper cannot bind an exact model and cannot be an approved implementation or review route.
- The user's existing model and credentials stay configured in dcode.
--modelis a metadata label and is not forwarded. - Permission checks stay enabled unless an authorized call passes
--auto-approve. Prompt and file context may be sent to the configured provider. - Analysis roles use a read-only prompt overlay, not an enforced sandbox. Isolate the workspace for untrusted input; do not treat
--restrict-toolsas a security boundary. - Direct calls have a labelled fallback chain when the CLI is missing. Do not attribute a fallback answer to dcode. Use
--disable-fallbackwhen the caller requires that seat. - Native output has no session ID. Resuming the latest session uses shared state and must not run concurrently against the same home.
Load by need
- references/command-reference.md: flags, examples, native mappings, and return codes when composing a non-basic invocation.
- references/runtime-reference.md: authentication, fallback conditions, configuration, and extended envelope fields when configuring a route or interpreting its result.
- references/continuation.md: only when resuming a session or managing a background job.
Result
Read agent_message and the wrapper envelope. Check success, serving-model receipt, effective runner/provider, and any fallback or malformed-output status. A completed process alone does not prove the requested task or model was used. Report touched files when the caller authorized edits.