← DelegentCONTENT HISTORY
WHAT CHANGED
Update to Delegent
Snapshot Nov 18, 2026 · 06:18 UTC · version 0.3.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Delegent and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Set up Delegent. Use when the user asks to set up Delegent, its routines or schedules, or when delegent_get_setup_status says setup should be offered.",
"included_files": [],
"name": "set-up-delegent",
"skill_md_contents": "---\r\nname: set-up-delegent\r\ndescription: Set up Delegent. Use when the user asks to set up Delegent, its routines or schedules, or when delegent_get_setup_status says setup should be offered.\r\n---\r\n\r\n# Set up Delegent\r\n\r\nDelegent works best when a few routines keep it current. This app runs the schedules; Delegent records what is set up.\r\n\r\n## 1. Check status\r\n\r\nCall `delegent_get_setup_status`.\r\n- `declined`: do not offer again unless the user asks.\r\n- `set_up`: show what is running and offer only `missing_recommended`.\r\n- `not_set_up` or `unknown`: continue.\r\n\r\n## 2. Show value first\r\n\r\nIf the user has not used Delegent here yet, run one piece now on real data, for example today's `plan-my-day-and-week` or `follow-up-atron`. People set up routines after they have seen the result.\r\n\r\n## 3. Recommend the core set\r\n\r\n| Routine | When (default) | What it does |\r\n|---|---|---|\r\n| Morning brief | Weekdays 07:30 | Today's meetings with prep, due tasks, follow-ups. Mondays add the week ahead. |\r\n| Daily wash-up | Weekdays 18:00 | Tells you what happened and keeps Delegent up to date. |\r\n\r\nOptional: midday check (13:00), weekly review (Fri 16:00), delegation chase (Tue and Thu 10:00), monthly SteerCo prep (first Monday).\r\n\r\nTwo scheduled tasks cover the core. Some plans cap active scheduled tasks, so fewer, bundled routines are better.\r\n\r\nSay this once: **scheduled runs work well on a faster, lower-cost model.** If this app lets you choose a model for scheduled tasks, pick one.\r\n\r\n## 4. Ask for settings in one message\r\n\r\nTimezone; times; which routines; for the wash-up, the auto-save level (see `routine-daily-wash-up`).\r\n\r\n## 5. Create the schedules\r\n\r\nFor each routine the user picks, use this app's scheduling feature with the self-contained run instruction from its routine skill:\r\n- `routine-morning-brief`\r\n- `routine-daily-wash-up`\r\n- `routine-midday-check`\r\n- `routine-weekly-review`\r\n- `routine-delegation-chase`\r\n- `routine-monthly-steerco`\r\n\r\nName the app's integrations explicitly in the instruction (Delegent, plus mail or calendar if used), so unattended runs can reach them.\r\n\r\n## 6. Record it\r\n\r\nAfter the app confirms each schedule, call `delegent_save_routine_setup` with the routines, schedules and host. If the user says no, record `declined: true`.\r\n\r\nTell the user:\r\n- when the first run is,\r\n- that unattended runs cannot ask questions, so anything needing a decision appears under **Needs you** in the run's output, where they can reply, and\r\n- how to pause, change or delete a routine.\r\n\r\nIf this app has no scheduler, or cannot reach Delegent in unattended runs, say so. Offer the run instructions as prompts to use manually. Record nothing as scheduled.\r\n"
}SHA-256 of public snapshot: fee021a863dd4cee7017dee4849549473d3ab51ad80d06ff1c16a0769149fcfc