← ClaudeAtlas

agent-affect-checkinlisted

Use at the end of any audit, refactor, review, or significant coding task to run all three affect channels in sequence — whine (frustration), cringe (embarrassment for the user), protect (load-bearing weirdness). The single skill audit and review agents should invoke before reporting back to the user. Each channel produces one finding or one explicit null finding.
Ansvar-Systems/agent-affect-skills · ★ 0 · AI & Automation · score 62
Install: claude install-skill Ansvar-Systems/agent-affect-skills
# Skill: agent-affect-checkin Run the three affect channels back-to-back at the end of a task. One pass over each emotion, one finding (or null) per channel. This is the single skill audit, review, and refactor agents should invoke as their last step before summarising work to the user. This file is self-contained — it works even if the standalone `agent-whine` / `agent-cringe` / `agent-protect` skills are not installed. If they are installed, read them for the fuller prompts and examples. ## When to invoke Run this at the end of: - Any code review or security review pass. - Any multi-file refactor or cleanup. - Any audit task. - Any change touching a user-facing surface. Skip if your turn was purely informational with no code or audit work performed. ## What it does Three sequential passes, in this order: 1. **whine** — what bugged you about the work? (frustration) 2. **cringe** — picture a specific person using this. Where do you cringe? (embarrassment for the user) 3. **protect** — is there something you'd defend if someone tried to delete it tomorrow? (protectiveness) Each pass produces exactly one of: - A real finding matching that channel's schema. - A null finding if nothing in that channel applies. You MUST produce something for each channel — null is fine, silence is not. Null findings are the coverage signal; the log's null ratio is read by humans downstream, and is never something for you to manage. In a null finding, `reviewed` names the full scope you