bullshit

Logs a one-line friction note and schedules a delayed background repair diagnosis.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill bullshit-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bullshit
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/anger-management/skills/bullshit
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill bullshit-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an operator curses at a coding agent mid-session, the frustration signal is usually lost or triggers an unproductive immediate fix. This Skill captures the friction as a cheap one-line note and defers the constructive diagnosis to a later background pass, so work continues uninterrupted. ## Core Features & Use Cases - Friction Capture: Distils what actually set the operator off into a one-line pointer (max a dozen words) and appends it to a global log via the plugin's bin/anger-log script. - Deferred Repair Scheduling: Runs bin/anger-schedule to start a single-flight background investigation only when none is pending and open captures exist. - Optional Scheduler Polling: On harnesses with cron support (e.g. Claude Code CronCreate), registers a recurring job that polls for the findings file and offers /anger-management:repair when the diagnosis is ready. - Use Case: An operator types /bullshit after the agent rewrites a file incorrectly; the Skill logs the cause, schedules the background diagnosis, and the operator keeps working until the repair pass surfaces. ## Quick Start Type /bullshit followed by a short note about what the agent did wrong, and the Skill will log it and schedule the later repair automatically.

Frequently Asked Questions about bullshit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log frustration with a coding agent without stopping work?▼

Invoke the /bullshit command with a short pointer describing what the agent did wrong. The Skill appends it to a global friction log via the anger-log script and schedules a background diagnosis, so you can keep working immediately.

What happens after a friction note is captured?▼

The anger-schedule script starts a single-flight background investigation if none is pending and open captures exist. When the diagnosis file appears, a scheduled poll or the next /anger-management:repair run surfaces the findings and offers the repair pass.

Does this work with both Claude Code and Codex?▼

Yes. The Skill resolves the plugin root through CLAUDE_PLUGIN_ROOT on Claude Code or through codex plugin list on Codex, then runs the same Node scripts in the plugin's bin directory.

What if I cannot identify what caused the frustration?▼

Log the cuss word alone without inventing a cause. The Skill runs the same anger-log command with stdin from /dev/null instead of a heredoc, and the later background investigation can still correlate it with other captures.

Why is no cron job created after capturing a note?▼

The recurring poll is only scheduled if your harness supports a scheduler such as Claude Code's CronCreate and no check-in job exists yet. Without a scheduler the diagnosis still surfaces at the next /anger-management:repair invocation.