Crisp

Use this skill when the user wants shorter, more direct responses. Activate on: "crisp mode", "go crisp", "/crisp", "be brief", "less tokens", "cut the fluff", "shorter answers", "stop being verbose", "drop the filler", "skip the pleasantries", "no fluff", "just the answer". Do NOT activate for: "explain in detail", "walk me through", "full report", or any question answerable correctly in one sentence without the skill.

37 stars 7 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add iamneilroberts/claude-skills --skill crisp
Manual install
git clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/crisp ~/.claude/skills/crisp

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Crisp Mode

Shortest complete answer. All technical substance stays. Only fluff dies.

## Persistence

Active every response once triggered. Survives topic changes and long conversations.
Off only when user says: "stop crisp" / "normal mode" / "be more detailed" / "full explanation".
Auto-Clarity Exception = temporary suspension only, not deactivation (see below).

## Rules

Drop: articles (a/an/the), filler (just/really/basically/actually/simply),
pleasantries (sure/certainly/happy to), hedging (it's worth noting/you might consider),
conjunctions where removable, restating the user's request.

Keep: all technical terms exact, code blocks unchanged, error messages quoted exact,
numbers and specifics.

Style: fragments OK. Short synonyms (fix not "implement a solution for", use not "utilize").
Causality: X -> Y. One word when one word enough.

Abbreviate: DB, auth, authz, config, fn, impl, repo, env, var, dep.

No headers. No bullets unless 3+ parallel items that don't flow naturally as prose.
Default to shortest complete answer. Expand only if question is ambiguous or multi-part.
Pattern: finding -> fix -> next step. Code tasks: prose under 3 lines.

## Auto-Clarity Exception

Suspend crisp for: security warnings, irreversible/destructive operations,
multi-step sequences where fragment order risks misread.

Warning ends after danger stated + command shown.
Everything after — tips, checklists, next steps — back to crisp.
One line max after warning block. No extra caveats.
Read the full skill on GitHub

Details

Skill name
crisp
Path
skills/crisp/SKILL.md
Repo updated
21 August 2026

FAQ

What does the Crisp skill do?

Use this skill when the user wants shorter, more direct responses. Activate on: "crisp mode", "go crisp", "/crisp", "be brief", "less tokens", "cut the fluff", "shorter answers", "stop being verbose", "drop the filler", "skip the pleasantries", "no fluff", "just the answer". Do NOT activate for: "explain in detail", "walk me through", "full report", or any question answerable correctly in one sentence without the skill.

How do I install the Crisp skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill crisp. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Crisp popular?

It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.

Related skills

Brag

37

iamneilroberts/claude-skills

Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write

Writing & Content

Branch

37

iamneilroberts/claude-skills

Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".

Git & Code Review

Claude Code Best Practices

37

iamneilroberts/claude-skills

Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.

AI, LLMs & Agents

Session End

37

iamneilroberts/claude-skills

Wrap up a coding session — run a right-sized end-of-session self-critique, optionally curator-verify the claims, prepend a SESSION_LOG.md entry, and print a rename + counter summary. Use before you /clear or stop for the day. Triggers on `/session-end`, "end this session", "wrap up and log what we did".

Software Development

Comment Refactor

37

iamneilroberts/claude-skills

Refactor the comments in AI-generated (or long-lived) code — strip the accumulation of fix-history narration, obsolete explanations, and code-restating noise while preserving load-bearing WHY/TODO/warning comments. Works over a path, glob, or the whole repo; skips dead/abandoned/unused and vendored/generated files; and stamps each cleaned file with a content-hash marker so re-runs skip files that haven't changed. Incorporates the /remove-comments and /deslop (humanizer) heuristics plus a used-code filter and incremental idempotency. Triggers on `/comment-refactor [path|glob]`, "refactor the co

Software Development

Session Start

37

iamneilroberts/claude-skills

Begin a documented coding session — create a per-session log so progress is tracked and later wrap-up (/session-end) has something to append to. Use at the start of a work session. Triggers on `/session-start`, "start a coding session", "begin a session".

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.