Kandev Routines
Apps & Automationkandev-routinesKandev Routines is an Agent Skill for apps & automation published in the kdlbs/kandev repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Create, inspect, pause, resume, or delete recurring Office routines when work should run on a cron schedule or webhook trigger.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/kdlbs/kandev/blob/HEAD/apps/backend/internal/office/configloader/skills/kandev-routines/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/kandev-routines, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Routines — schedule recurring tasks
Routines fire on cron or webhook and create a fresh task each time, assigned to a specific agent. Use them when work needs to happen on a clock (daily standups, weekly reports, hourly health checks).
List existing routines
$KANDEV_CLI kandev routines list
Create a daily standup routine
$KANDEV_CLI kandev routines create \
--name "Daily standup" \
--task-title "What did each agent ship today?" \
--task-description "Summarise yesterday's commits and PRs across the team. Post to #engineering." \
--assignee A-ceo \
--cron "0 9 * * MON-FRI" \
--timezone "Europe/Lisbon"
This creates the routine and attaches a cron trigger in one command. The CLI does two API calls under the hood (routine + trigger); the response is the trigger row.
Pause, resume, delete
$KANDEV_CLI kandev routines pause --id R-1
$KANDEV_CLI kandev routines resume --id R-1
$KANDEV_CLI kandev routines delete --id R-1
Required inputs
--name— display name; users see this on the Routines page.--task-title— title for every task this routine creates. Supports{{name}}and{{date}}placeholders.--task-description— agent instructions for each fire.--assignee— the agent ID that receives the task. For coordinator work, this is the CEO; for distributed checks, a worker or specialist.--cron— standard 5-field cron expression.
When NOT to create a routine
- One-off work — just
tasks createdirectly. - A reaction to a specific event — use a workflow trigger or webhook channel, not a routine.
- Something the CEO heartbeat already covers (e.g. checking for new comments — that's automatic).