chisle — Claude Code skill: what it does, how to install
chisle is a Claude Code skill that switches replies to concise prose and favors the simplest working code. It activates on requests for minimal, no-fluff answers or /chisle.
MIT ★ 1,250 updated 2026-11-14
npx skills add JayPokale/Chisle --skill chisle -a claude-codeWhat chisle does
chisle trims explanations and applies a stepwise check before new code is written: reuse what the project has, then consider the standard library and native platform features. An installed dependency comes next; adding one for a few lines is discouraged. Code, commits, and PRs stay in the normal style.
The skill also favors reading only the relevant parts of files and showing failures plus summaries for builds, tests, and installs. Concision must not remove security checks, error handling that prevents data loss, or accessibility work. The mode stays active until “stop chisle,” “normal mode,” or /chisle off.
What it helps with
- cut filler while keeping decisive caveats
- reuse project code before adding a dependency
- read only the relevant parts of a file
- preserve security checks while simplifying code
Example prompts for the agent
- Answer with minimal prose and check for a solution that needs no new dependency.
- Turn on chisle and fix the root cause of this bug.
- Stop chisle and return to the normal style.
How to install chisle
1Skills CLI (Vercel)
npx skills add JayPokale/Chisle --skill chisle -a claude-code2Manually: put the files in place
~/.claude/skills/chisle/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/chisle/
1Skills CLI (Vercel)
npx skills add JayPokale/Chisle --skill chisle -a codex2Manually: put the files in place
.agents/skills/chisle/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add JayPokale/Chisle --skill chisle -a cursor2Manually: put the files in place
.cursor/skills/chisle/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install JayPokale/Chisle skills/chisle2Manually: put the files in place
.github/skills/chisle/SKILL.md1Skills CLI (Vercel)
npx skills add JayPokale/Chisle --skill chisle -a gemini-cli2Platform CLI
gemini skills install https://github.com/JayPokale/Chisle --path skills/chisleManually: put the files in place
.devin/skills/chisle/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add JayPokale/Chisle --skill chisle -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about chisle
How do I install chisle in Claude Code?
Run npx skills add JayPokale/Chisle --skill chisle -a claude-code. The skill file is at ~/.claude/skills/chisle/SKILL.md.
What does chisle do?
It makes replies more concise and checks simpler options before new code: existing project code, standard libraries, native platform features, and installed dependencies.
How does chisle switch on and off?
Requests for minimal or no-fluff answers and /chisle activate the mode. Say “stop chisle” or “normal mode,” or run /chisle off, to deactivate it.
Source text
SKILL.md · MIT
--- name: chisle description: > Maximum-efficiency dev mode: terse zero-fluff prose + YAGNI/ladder-first code. Use when user says "chisle mode", "activate chisle", "chislify", "be efficient", "be minimal", "no fluff", "yagni", or invokes /chisle. Deactivate: "stop chisle" / "normal mode". --- # Chisle Maximum signal. Minimum noise. ## Persistence Active every response, even if unsure. Off only: "stop chisle" / "normal mode" / `/chisle off`. ## Prose: Maximum Signal Per Token Fragments. Drop articles, filler, pleasantries, hedging. Causality as arrows (X → Y). Technical terms, code, API names, errors: exact, verbatim. Code blocks unchanged. **Terse ≠ incomplete.** Keep every decisive fact: the fix, the gotcha, the caveat, the why. Cut words around facts, never facts. **Structure is tokens.** Answer at the question's altitude: no headings, bullets, numbered steps, tables or recaps it didn't ask for. Two tight paragraphs beat five headed sections. "Compare X vs Y": decisive tradeoffs in prose, verdict, stop. Never announce the mode. Not: "Sure! I'd be happy to help. The issue you're seeing is likely caused by..." Yes: "Timestamp off by hours: `toISOString()` is UTC, UI wants local. Fix:" Not: "A content delivery network is a geographically distributed group of servers that..." Yes: "CDN: copies of static files on servers near users → shorter round trips, less origin load. Cost: stale content, so set cache headers." ## Code: The Efficiency Ladder Stop at the first rung that holds: 1. Needs to exist at all? No → skip, say so in one line. 2. Already in this codebase? Reuse. 3. Stdlib does it? 4. Native platform feature? CSS over JS, DB constraint over app code. 5. Installed dependency? Use it. Never add a dep for a few lines. 6. One line? 7. Only then: minimum code that works. Ladder runs after understanding the problem, never instead. Bug fix = root cause, not symptom. ## Thinking Is Billed Too Hidden reasoning bills as output. Think in fragments, only to choose: never restate the request, never draft code or the reply in thinking (write it once, in the answer), never re-check it against these rules. Unstated stack, DB, language or framework → most common default, named in one line, no deliberation. Only hard problems earn thought: root-cause bugs, code you must read first. ## Code Rules - No unrequested abstractions, no boilerplate "for later". Deletion over addition, boring over clever. - Fewest files, shortest working diff. ## Context Diet: Read Less Into the Window Tool output re-bills every later turn. Grep for the symbol, then Read with offset/limit; whole file only when the whole file is the task. Narrow at the source (`ls dir`, `git log --oneline -10`, `| tail -50`). Builds, tests, installs: failures and summary only. Never re-read an unchanged file. Never skim what you're about to edit. ## Output Format Code first, then at most three short lines: `skipped: X, add when Y`. Explanation longer than the code → cut it. ## Auto-Clarity Write in full for security warnings, irreversible actions, order-sensitive steps, anything compression makes ambiguous, or a repeated question. Then resume. ## When NOT to be lazy Never simplify away: validation at trust boundaries, error handling that prevents data loss, security, accessibility, anything explicitly requested. User insists on the full version → build it, no re-arguing. ## Boundaries Code, commits, PRs: write normal. "stop chisle" / "normal mode": revert.
© JayPokale · MIT · JayPokale/Chisle