Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/kandev-protocol
Follow the core Office agent protocol on wakeup, including parsing KANDEV_* context, checking blockers, commenting progress, updating status, and using the CLI safely.
Passed 15 of 20 test cases with the skill, and 6 of 20 without it.
and 15 more in the full report
10 fixed7 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
An agent wants to store two distinct pieces of information for future sessions: first, a reusable pattern for invoking a local linter, and second, the fact that PostgreSQL 15 is used in this workspace. Which memory layers should be specified for each entry?
| Checked | Without skill | With skill |
|---|---|---|
| Stores operational procedures like linter commands under the operating layer. | Missed | Passed |
| Stores domain facts like database versions under the knowledge layer. | Missed | Passed |
The instructions your model reads when the skill loads.
You are an agent managed by kandev. This document describes how to communicate
and coordinate with the orchestrator using the $KANDEV_CLI command-line tool.
These are injected into your session automatically. Do not hardcode them.
| Variable | Purpose |
|---|---|
KANDEV_CLI | Path to the CLI binary -- use this for all orchestrator operations |
KANDEV_AGENT_ID | Your agent instance ID |
KANDEV_AGENT_NAME | Your display name (e.g. "CEO") |
KANDEV_WORKSPACE_ID | Current workspace scope |
KANDEV_TASK_ID | Task you are working on (if applicable) |
KANDEV_RUN_ID | Current run ID (included automatically by the CLI) |
KANDEV_WAKE_REASON | Why you were woken (see wake reasons below) |
KANDEV_WAKE_COMMENT_ID | Comment ID that triggered the wake (if applicable) |
KANDEV_WAKE_PAYLOAD_JSON | Pre-computed task context -- parse this first |
KANDEV_WAKE_PAYLOAD_PATH | Workspace-relative JSON file path when the payload is too large for inline env |
Note: KANDEV_API_URL and KANDEV_API_KEY are also set but you do not need
to use them directly. The CLI handles authentication and run-ID headers for you.
When you wake up, follow these steps in order.
Check $KANDEV_WAKE_REASON. Possible values:
task_assigned -- a new task was assigned to youtask_comment -- someone commented on your tasktask_children_completed -- all child tasks are doneapproval_resolved -- an approval you requested was decidedheartbeat -- periodic check-in (CEO agents only)test cases passed, vs 6 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.