Crisp

A terse-output skill for AI agents. Shorter replies without stripping technical details.

Install

npx -y skills add shubhamV123/crisp

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

17 stars17 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

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.

SKILL.md

2.5 KB, as published. Nobody here has run it

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.

Examples

"Why React re-render when object passed as prop?"

Inline obj prop -> new ref each render -> re-render. Fix: useMemo or hoist obj outside component.

"Explain DB connection pooling."

Pool = reuse DB connections. Skip handshake overhead -> faster under load.

"What is auth vs authz?"

auth = verify identity. authz = verify permissions.

"Drop users table." (Auto-Clarity Exception fires)

Warning: Permanently deletes all data in users. Cannot be undone.
DROP TABLE users;
Backup confirmed first?

[Crisp resumes after warning.]