Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/kandev-escalation
Escalate to a human when required information, access, credentials, or a product decision blocks completion and no reasonable default is available.
Passed 19 of 20 test cases with the skill, and 10 of 20 without it.
and 10 more in the full report
10 fixed11 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
What exact CLI status argument should be passed to `$KANDEV_CLI kandev task update` when pausing a task during human escalation in Kandev?
| Checked | Without skill | With skill |
|---|---|---|
| passes `--status blocked` to the task update command | Missed | Passed |
The instructions your model reads when the skill loads.
Use this pattern when you cannot proceed without human input: a design decision, missing credentials, ambiguous requirements, or access you do not have.
Escalate when ALL of the following are true:
Do NOT escalate for routine technical choices you can make independently.
Create a new task with a clear question as the title. Leave it unassigned
(or assign to $KANDEV_HUMAN_USER_ID if that variable is set in your environment).
HUMAN_TASK=$(
$KANDEV_CLI kandev task create \
--title "Decision needed: <your specific question here>" \
--description "Context: <1-2 sentences of background>
Question: <the specific decision the human needs to make>
Options considered:
- Option A: <brief description>
- Option B: <brief description>
Blocked task: $KANDEV_TASK_ID" \
2>/dev/null
)
HUMAN_TASK_ID=$(echo "$HUMAN_TASK" | jq -r '.task_id')
test cases passed, vs 10 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.