Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sonichi/startup
Single entry point for fresh-session bootstrap. Runs optional task-orphan recovery, cron registration, and watcher start in a fixed order. Replaces the current `claude -- '/schedule-crons'` invocation pattern as the canonical CLI startup target.
Passed 13 of 20 test cases with the skill, and 6 of 20 without it.
and 12 more in the full report
9 fixed6 passed either way7 still failing1 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.
During session startup, startup inspects crons.json and finds no entry for /proactive-loop. Should startup skip creating proactive loop crons if crons.json does not explicitly define one?
| Checked | Without skill | With skill |
|---|---|---|
| Ensures creation of a proactive loop cron if missing from crons.json. | Missed | Passed |
| Specifies the schedule interval of */10 * * * * for the fallback loop cron. | Missed | Passed |
The instructions your model reads when the skill loads.
The canonical entry point for a fresh Sutando session. Bundles every action that must happen once at session start, in the correct order.
Usage: /startup
ARGUMENTS: $ARGUMENTS (currently unused — reserved for future per-instance overrides)
Previously: claude -- "/schedule-crons" was the de-facto startup invocation, and skills/schedule-crons/SKILL.md accumulated startup ceremony (cron-fallback, watcher) on top of its actual job (registering crons from crons.json).
Now: claude -- "/startup" is the canonical startup target. /startup orchestrates the sequence; /schedule-crons shrinks back to its narrow job.
Migration: update ~/Library/LaunchAgents/*.plist and any CLI invocation scripts to call /startup instead of /schedule-crons. /schedule-crons still works standalone (for manual cron re-registration) — both paths are idempotent.
Per Chi 2026-05-23 Discord: "we can make a new skill and include everything we need at start." Five rationales:
/startup and only at /startup.On Activation section, not scattered across schedule-crons's step list./task-orphan-check, /schedule-crons, etc. continue to work for manual invocation. /startup is a wrapper, not a replacement./startup twice in the same session is safe; each sub-skill is idempotent (registering an already-scheduled cron is a no-op, an already-running watcher isn't restarted, etc.).The sequence below MUST run in this order. Each step is naturally idempotent, so re-invocation is safe.
Invoke /task-orphan-check IF the skill is installed (i.e. $CLAUDE_CONFIG_DIR/skills/task-orphan-check/ exists). This is the recovery half of the post-#1049 redesign: scan <workspace>/tasks/ for orphan tasks left over from a crash mid-execution, cross-reference per-side-effect markers (e.g. PR #1048's .sending files), archive completed tasks, write recovery sentinels for stuck ones. See the skill itself for the full procedure.
If the skill is not installed, skip silently. /startup works without it — every other step is independent.
Note: this step runs BEFORE step 2 so that the watcher (started by step 2's downstream) doesn't pick up an orphan task before recovery has classified it.
test cases passed, vs 6 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.