Stall to alert color escalation
Skill vishuwa2004/cskill-agents/agents/codex/skills/stall-to-alert-color-escalation
Build curated agent skills for coding CLIs, terminal tools, context engines, remote bridges, and multi-agent runtimes
npx -y skills add vishuwa2004/cskill-agents --skill stall-to-alert-color-escalationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Blend spinner or progress colors toward an alert hue as stall intensity rises so stuck work becomes visually obvious without changing layout.
SKILL.md
1.6 KB, as published. Nobody here has run it
SKILL: Stall-to-Alert Color Escalation
Domain: terminal-ui Trigger: Use when a spinner or progress indicator should warn about stalls without replacing itself with a larger warning UI. Source Pattern: Distilled from reviewed stall-sensitive terminal indicator rendering patterns.
Core Method
Start with the indicator's normal theme color, then interpolate it toward a known alert color as stall intensity rises. If exact color math is unavailable, fall back to a semantic alert token instead of failing. This creates a smooth escalation path that preserves the indicator's footprint while still making degraded states obvious.
Key Rules
- Drive the escalation from a normalized stall intensity rather than fixed hardcoded time branches inside the renderer.
- Keep a safe fallback path when literal color parsing fails.
- Preserve the same spinner or indicator footprint while only changing color and, if needed, subtle glyph intensity.
Example Application
For a long-running build spinner, fade the normal accent color toward red as the system detects a likely stall, while keeping the same single-cell spinner slot.
Anti-Patterns (What NOT to do)
- Do not swap the spinner for a larger banner at the first sign of delay.
- Do not hardcode one threshold and one end-state color without a smooth ramp.
- Do not let stall visuals change the indicator's size or alignment.