Stats
Actions
Tags
From in-the-loop
Read and optionally modify the in-the-loop configuration at `~/.in-the-loop/config.json`.
How this skill is triggered — by the user, by Claude, or both
Slash command
/in-the-loop:configThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read and optionally modify the in-the-loop configuration at `~/.in-the-loop/config.json`.
Read and optionally modify the in-the-loop configuration at ~/.in-the-loop/config.json.
{
"frequency": "sometimes",
"difficulty": "intermediate"
}
frequency — how often questions appear:
every: every stop / every 5th tool useoften: every 2nd stop / every 8th tool usesometimes (default): every 3rd stop / every 12th tool userarely: every 5th stop / every 20th tool usedifficulty — question complexity:
beginner: fundamental conceptsintermediate (default): design decisions, trade-offs, best practicesadvanced: edge cases, security, performance, architecture~/.in-the-loop/config.json. If it doesn't exist, treat the defaults above as the current config.$ARGUMENTS), parse them:
--frequency <value> — must be one of: every, often, sometimes, rarely--difficulty <value> — must be one of: beginner, intermediate, advanced~/.in-the-loop/ if needed, then write the updated config as formatted JSON.npx claudepluginhub elishahodes/in-the-loopBuilds a throwaway prototype to answer a design question about UI appearance or state/logic behavior. Guides you through two branches: interactive terminal app for logic validation, or multiple UI variations for visual exploration.