
shubhamv123/crisp
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
A terse-output skill for AI agents. Shorter replies without stripping technical details.
概要
A terse-output skill for AI agents. Shorter replies without stripping technical details. "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by a problem in your authentication middleware where the token expiry check is using the wrong comparison operator..." Bug in auth middleware. Token expiry check uses < not <=. Fix: crisp was inspired by existing terse-output and agent-behavior work, including: - Caveman by Julius Brussee - Caveman skill by Matt Pocock - Common “no fluff” prompting patterns used in coding-agent workflows crisp is my professional-tone variation of this idea: normal concise replies, no meme-style output, and careful preservation of code, errors, commands, numbers, and risky-operation context. crisp focuses on concise replies that still sound normal and professional. The goal is not maximum compression at all costs. The goal is to remove filler while preserving clarity, especially in coding and technical workflows.
README
以下は原文 README の抜粋です。原文を見る。
crisp
A terse-output skill for AI agents. Shorter replies without stripping technical details.
Before / After
Without crisp:
“Sure! I’d be happy to help you with that. The issue you’re experiencing is likely caused by a problem in your authentication middleware where the token expiry check is using the wrong comparison operator…”
With crisp:
Bug in auth middleware. Token expiry check uses
<not<=. Fix:if (now <= expiry) { ... }
Same technical details. Fewer words.
Attribution
crisp was inspired by existing terse-output and agent-behavior work, including:
- Caveman by Julius Brussee
- Caveman skill by Matt Pocock
- Common “no fluff” prompting patterns used in coding-agent workflows
crisp is my professional-tone variation of this idea: normal concise replies, no meme-style output, and careful preservation of code, errors, commands, numbers, and risky-operation context.
Why crisp
crisp focuses on concise replies that still sound normal and professional.
The goal is not maximum compression at all costs. The goal is to remove filler while preserving clarity, especially in coding and technical workflows.
crisp is designed to stay terse by default, but use clearer wording when compression could make the answer unsafe or ambiguous.
For destructive operations, security warnings, and irreversible actions, crisp instructs the agent to use clear full-sentence warnings before returning to concise output. The goal is faster reading without compressing the parts where clarity matters.
// Destructive op — crisp uses clear prose first:
Warning: This permanently destroys all data in `users`. Cannot be undone.
DROP TABLE users;
Verify backup first. ← concise mode resumes here
Install
crisp follows the Agent Skills specification. It works with any agent that supports skills.
npx skills add shubhamv123/crisp
Any other agent / browser:
Paste the contents of SKILL.md at the start of your conversation:
“Follow these instructions for this entire conversation: [paste SKILL.md]”
Usage
| What you type | What happens |
|---|---|
crisp mode |
Activates crisp |
go crisp |
Activates crisp |
/crisp |
Activates crisp |
be brief |
Activates crisp |
cut the fluff |
Activates crisp |
stop crisp |
Back to normal |
normal mode |
Back to normal |
explain in detail |
Back to normal |
Once active, crisp stays on for the entire conversation — no need to re-trigger every message.
What crisp reduces
- Unnecessary openings: “sure”, “happy to help”, “great question”
- Soft filler: “basically”, “actually”, “simply”, “just”
推奨ツール
別のキーワードを試すか、フィルタを外してください。
インストール
npx skillfish add shubhamv123/crisp