From illo
Coordinator for the illo-sidebar plugin. Use when the user references the sidebar, "the side panel", "pending inputs", or wants to resume a question Claude asked earlier. Also use when injecting a resumed question's context back into a turn.
How this skill is triggered — by the user, by Claude, or both
Slash command
/illo:sidebar-coordinatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The illo-sidebar plugin runs a tiny local daemon and a browser-based right-side
The illo-sidebar plugin runs a tiny local daemon and a browser-based right-side
panel that lists every moment Claude has been waiting on the user — questions
asked via AskUserQuestion, permission prompts, and idle stops. Each item
gently re-warns at a configurable cadence (default 300s) until the user has
either focused (hovered/clicked) or explicitly resumed it.
The daemon writes ~/.claude/illo-sidebar/pending_resume.json. The plugin's
UserPromptSubmit hook reads that file on the user's next prompt and injects
an additionalContext block describing the original question. Do not re-ask
the original question — treat the user's typed text as their reply to it.
The injected block looks like:
[illo-sidebar] User is resuming a previously surfaced pending input.
item_id: itm_xxx
title: <original question>
original_question_or_event: <serialized original AskUserQuestion payload>
excerpt: <snippet>
The text the user typed below is their reply to that.
Call /illo-status (or fetch http://127.0.0.1:<port>/state directly) and
summarize the unresolved items. Don't dump the whole JSON.
Call /illo. If they want a smaller footprint, tell them to press b inside
the sidebar window for compact-box mode.
~/.claude/illo-sidebar/daemon.log first.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub laiadlotape/illo --plugin illo