Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/kandev-approvals
Clear the CEO approval queue when hire requests, budget grants, or other sensitive Office mutations are waiting for approve or reject decisions.
Passed 9 of 16 test cases with the skill, and 4 of 16 without it.
and 5 more in the full report
8 fixed4 passed either way9 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the Kandev system architecture, who is designated as the default decider responsible for clearing gated approval queues?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies the CEO as the default decider for gated approvals | Missed | Passed |
The instructions your model reads when the skill loads.
Sensitive office mutations (hire requests, budget grants, certain task transitions) are gated behind approvals. The CEO is the default decider.
$KANDEV_CLI kandev approvals list --status pending
Returns rows with id, type (e.g. hire_agent), requester_agent_id, reason, and created_at.
$KANDEV_CLI kandev approvals decide --id AP-1 --decision approve --note "Backlog supports the hire."
$KANDEV_CLI kandev approvals decide --id AP-2 --decision reject --note "Hire blocked by Q3 budget freeze."
The note is visible on the approval row and surfaced to the requester on their next heartbeat.
For hire_agent:
agents list to verify org composition first)kandev-team-admin)For budget_grant:
For approval types you don't recognise, do not reject blindly — list the approval, read its payload, then decide.
Approvals don't auto-fire reminders. If the CEO leaves them sitting, the requesters block indefinitely. Run approvals list on every heartbeat and clear anything you can decide quickly.
test cases passed, vs 4 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.