Manage custom skills and scheduled tasks
manage_agent_custom_skillCreate and manage an agent's custom skills and scheduled tasks: upsert instructions or cron prompts, rename, delete, view history, and revert to prior versions.
Instructions
Create and manage a deployed agent's own skills. A custom skill (key cs-...) is standing instructions the agent follows, for example a tone or an approval policy. A scheduled task (key cs-cron-...) is a prompt the agent runs by itself on a cron schedule, for example a weekly report. Actions: upsert creates or updates one (a bare key such as "weekly-report" updates the agent's own entry of that name when there is one, and otherwise gets its prefix from kind or interval; the result gives the final key); rename changes the key of one you created; delete removes one you created together with its history (needs confirm: true); history shows the current text in full and lists earlier versions, the template default and ready-made templates (key "cs-my-custom-strategy" or "cs-cron-my-scheduled-task" gives starter templates); revert restores the template default or an earlier version (needs confirm: true). Schedules use the agent's time zone, which is UTC unless it was set with update_agent; a new task without interval runs Mondays at 10:00. Every scheduled run spends the agent's credits, so confirm the schedule with the user. Entries from the agent's template, cs-approval-policy and the scheduled tasks its skills brought cannot be deleted or renamed: set enabled false instead. The agent restarts when the text, schedule or on/off state changes. get_my_agent lists the current entries. Registry skills are switched with apply_agent_skills instead. On a team agent this needs a team admin or the person who deployed it; other team members read each entry in full with get_my_agent (entry). The agents playbook (get_playbook) covers custom skills and schedules.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | The entry's key: a full key (cs-... or cs-cron-...) or a bare slug such as "weekly-report" (lowercase letters, digits, single dashes). A bare slug names the agent's existing entry of that name, whichever kind it is. | |
| kind | No | skill (instructions, cs-) or scheduled_task (runs on a schedule, cs-cron-). Decides the prefix of a bare key; without it a new bare key becomes a custom skill unless interval is given. | |
| limit | No | history: how many versions to return, newest first (default 20). | |
| value | No | upsert: the instructions (custom skill) or the prompt to run (scheduled task). Required when creating. | |
| action | Yes | What to do. | |
| source | No | revert: preset (the template default) or history (an earlier version). | |
| confirm | No | delete and revert: true to do it after the user agreed. Without it they only describe what would happen. | |
| enabled | No | upsert: true to turn it on, false to turn it off. New entries start on. | |
| new_key | No | rename: the new key, of the same kind. | |
| interval | No | upsert, scheduled tasks only: a 5-field cron expression such as "0 9 * * 1-5" (weekdays 09:00). Omit to keep the current schedule, or Mondays 10:00 for a new task. | |
| agent_guid | Yes | The deployed agent's guid, from list_my_agents. | |
| version_id | No | revert with source history: a versionId from action history. | |
| description | No | upsert or rename: a short summary the agent uses to pick the skill. Fixed for entries that come with the agent. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | ||
| kind | Yes | ||
| entry | No | ||
| action | Yes | ||
| status | Yes | ||
| created | No | ||
| history | No | ||
| message | Yes | ||
| restart | No | ||
| schedule | No | ||
| warnings | Yes | ||
| agentGuid | Yes | ||
| renamedTo | No | ||
| templates | No | ||
| nextAction | No | ||
| revertResult | No | ||
| presetDefault | No |