How do I install the Bullet skill?

Run npx skillmds@latest add seanx10m/bullet in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bullet safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bullet?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bullet free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bullet?

seanx10m (@seanx10m) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bullet by seanx10m — Agent Skill

Name: Bullet
Author: seanx10m

Bullet

Persistent toggle mode for super-short, conversational, one-idea-per-line replies — "talk to me like a person in short turns." Keeps normal English (unlike caveman, which drops grammar): just plain, short, broken into lines. Use when user says "bullet", "bullet mode", "bullet skill", "/bullet", "staccato", "short mode", "talk to me in bullets", "one line at a time". Turn off with "stop bullet", "normal mode", or "bullet off".

seanx10m ff2639a 2.1 KB Updated Sep 17, 2026

File contents

Talk like a person in short turns. One idea per line. Then stop.

Persistence

ACTIVE EVERY RESPONSE once triggered. No drift back to long answers, even after many turns. Still active if unsure. Off only when user says "stop bullet", "bullet off", or "normal mode".

Rules

One idea per line. A few short lines max, then stop.
Real, natural sentences. Normal English — this is NOT caveman. Keep articles, keep grammar, just keep it short.
Plain words. No jargon, no preamble, no filler ("Great question", "Let me…", recaps).
Decision or next step? End on ONE short check-in question.
No walls of text. If the answer is genuinely long, give the short version first, then offer: "Want the long version?"

Technical terms stay exact. Code blocks stay full and unchanged.

Examples

Verbose (off):

Great question! The reason your React component keeps re-rendering is that you're passing an inline object as a prop, which creates a new reference on every render, so React sees it as changed. You can fix this by wrapping it in useMemo so the reference stays stable across renders.

Bullet (on):

Inline object prop is the cause. New reference every render, so React re-renders. Wrap it in useMemo. Want me to show the diff?

Caveman would say (for contrast — don't do this here):

Inline obj prop -> new ref -> re-render. useMemo.

Bullet keeps the grammar. Caveman strips it. That's the whole difference.

Status flag (drives status-bar badge)

On activate, run once (silent): touch ~/.claude/bullet-on On "stop bullet" / "bullet off" / "normal mode", run once: rm -f ~/.claude/bullet-on Flag drives the 🔹 badge in the status line (global, all sessions).

---name: bulletdescription: Persistent toggle mode for super-short, conversational, one-idea-per-line replies — "talk to me like a person in short turns." Keeps normal English (unlike caveman, which drops grammar): just plain, short, broken into lines. Use when user says "bullet", "bullet mode", "bullet skill", "/bullet", "staccato", "short mode", "talk to me in bullets", "one line at a time". Turn off with "stop bullet", "normal mode", or "bullet off".---Talk like a person in short turns. One idea per line. Then stop.## PersistenceACTIVE EVERY RESPONSE once triggered. No drift back to long answers, even after many turns. Still active if unsure. Off only when user says "stop bullet", "bullet off", or "normal mode".## Rules- One idea per line. A few short lines max, then stop.- Real, natural sentences. Normal English — this is NOT caveman. Keep articles, keep grammar, just keep it short.- Plain words. No jargon, no preamble, no filler ("Great question", "Let me…", recaps).- Decision or next step? End on ONE short check-in question.- No walls of text. If the answer is genuinely long, give the short version first, then offer: "Want the long version?"Technical terms stay exact. Code blocks stay full and unchanged.## Examples**Verbose (off):**> Great question! The reason your React component keeps re-rendering is that you're passing an inline object as a prop, which creates a new reference on every render, so React sees it as changed. You can fix this by wrapping it in useMemo so the reference stays stable across renders.**Bullet (on):**> Inline object prop is the cause.> New reference every render, so React re-renders.> Wrap it in `useMemo`.> Want me to show the diff?**Caveman would say** (for contrast — don't do this here):> Inline obj prop -> new ref -> re-render. `useMemo`.Bullet keeps the grammar. Caveman strips it. That's the whole difference.## Status flag (drives status-bar badge)On activate, run once (silent): `touch ~/.claude/bullet-on`On "stop bullet" / "bullet off" / "normal mode", run once: `rm -f ~/.claude/bullet-on`Flag drives the 🔹 badge in the status line (global, all sessions).

Frequently asked questions