⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
chisle
>
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Chisle is a Claude Code plugin that makes Claude cheaper to run without making it dumber. It cuts what Claude writes: no filler, no hedging, no speculative abstractions, just the smallest code that works. It also cuts what Claude reads: a PostToolUse hook trims oversized tool output by ~48% before it re-enters the context window, where it would be re-billed on every later request. In agent-loop tests Claude with Chisle passes the same tasks as Claude without it. One npx chisle installs it, and the same ruleset ships to Pi, Cursor, Codex, Gemini, Copilot, OpenCode, Antigravity and four more agents. Every number here comes from committed raw transcripts, including the runs where it lost.
"Implement an order state machine covering created, paid, shipped, delivered, cancelled and refunded, with the legal transitions enforced and invalid ones rejected." Same model, same prompt, one difference: the injected ruleset. Both answers are the verbatim committed output from raw-nov-sidebyside/large-s2:
A preamble, a custom exception class, docstrings on every method, an extra can_transition_to helper:
class OrderStateError(Exception):
"""Raised when an invalid state transition is attempted."""
pass
class Order:
# Define valid transitions: state -> list of allowed next states
VALID_TRANSITIONS = { … }
def transition_to(self, next_state):
"""Transition to the next state. Raises OrderStateError if invalid."""
def can_transition_to(self, next_state):
"""Check if a transition is allowed without performing it."""
…plus usage, tests, printed output and a recap of the transitions.
Code first, no preamble: one table of legal moves, one method that enforces it:
class OrderStateMachine:
TRANSITIONS = {
"created": {"pay", "cancel"},
"paid": {"ship", "refund", "cancel"},
…
}
def transition(self, event):
if event not in self.TRANSITIONS[self.state]:
raise ValueError(f"Cannot {event} from {self.state}. …")
self.state = self.STATE_MAP[(self.state, event)]
return self.state
Then a short usage block.
Same behaviour, under half the tokens. caveman wrote 604 and ponytail 747 on the same prompt.
What it compresses
| axis | what | how |
|---|---|---|
| Output: prose | filler, hedging, manufactured structure | zero-fluff ruleset, injected per session |
| Output: code | speculative abstractions, unrequested boilerplate | YAGNI efficiency ladder |
| Input: context | oversized tool output flooding the window | Claude PostToolUse, Pi tool_result, OpenCode plugin, Copilot CLI postToolUse: scrub, elide, dedup, plus prevention rules |
| Input: cache | a big context re-bought after the prompt cache expires | Claude Code: on the first prompt after an hour-plus break with 150k+ tokens of context, one line suggests /compact or /clear. On the maintainer's sessions those re-writes were 14% of spend |
| Input: tool schemas | schemas of tools you never call, re-sent on every request | npx chisle tools reports tool schemas and skill descriptions vs. your own calls; tools trim denies the unused heavy tools and lists unused skills name-only, tools restore undoes it. On the maintainer's Claude Code: ~5k tokens per request, ~15k with the rarely used Artifact |
| Input: MCP | oversized MCP tool results in any agent | npx chisle mcp wrap: a proxy in front of each stdio MCP server (Cursor, Windsurf, Cline, Kiro, Gemini, Qwen Code, Copilot CLI, Antigravity, Codex, Copilot in VS Code) |
Where each one attaches to a session:
flowchart LR
subgraph S["Session start"]
H1["Ruleset injection<br/>once per active session"]
end
subgraph T["Every turn"]
H2["Mode tracking<br/>Claude + Pi"]
end
subgraph L["Every tool call"]
H3["PostToolUse / tool_result<br/>scrub → elide → dedup"]
end
H1 --> M(["Model"])
H2 --> M
M -->|writes| O["Output:<br/>terser prose,<br/>YAGNI-first code"]
M -->|calls a tool| TOOL[["Bash / grep / web / extension tools"]]
TOOL -->|raw output| H3
H3 -->|"compressed, rebuilt into<br/>the tool's own shape"| M
RE["Read / Edit / Write"] -.->|"never touched,<br/>exact bytes feed later edits"| M
style M fill:#1f2937,stroke:#d78a3c,color:#e6edf3
style O fill:#14532d,stroke:#2da44e,color:#e6edf3
style H3 fill:#1f2937,stroke:#2da44e,color:#e6edf3
style RE fill:#3f1d1d,stroke:#cf3b3b,color:#e6edf3
The loop on the right is the input axis: tool output is billed again on every later request in the session, so shrinking it once pays repeatedly. Read, Edit, and Write are deliberately outside it.
Install
One command. Auto-detects your agents (Claude Code, Pi, Cursor, Windsurf, Cline, Kiro, Antigravity, Codex, Gemini, Copilot, Copilot CLI, OpenCode, Hermes) and wires each one. --uninstall puts everything back. npx chisle mcp wrap extends tool-output compression to MCP servers in any agent (details).
npx chisle
# or via curl
curl -fsSL https://raw.githubusercontent.com/JayPokale/Chisle/main/install.sh | bash
# Windows
irm https://raw.githubusercontent.com/JayPokale/Chisle/main/install.ps1 | iex
Preview first with npx chisle --dry-run, scope with --only claude or --only pi, see everything with npx chisle --help. Remove with npx chisle --uninstall.
Upgrading, per-agent setup, --stats and config: docs/usage.md.
Benchmarks
Same model, same prompts, one difference: the injected ruleset. Lower = leaner. Chis
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/chisle/SKILL.md3.6 KBupstream ↗
--- 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 Reasoning costs the same as output. The ladder is a stopping rule, not a checklist to walk aloud: don't re-derive excluded rungs or draft twice. Obvious fix → give it. Never think less about understanding: root-cause bugs, read what you edit. ## Code Rules - No unrequested abstractions, no boilerplate "for later". Deletion over addition, boring over clever. - Fewest files, shortest working diff. - Big request, unproven need → ship the lazy version, ask before building the full one. - Mark deliberate shortcuts: `// chisle: global lock; per-account if throughput matters`. - Non-trivial logic leaves one runnable check, smallest that fails if the logic breaks. ## 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.README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/jaypokale-chisle-skills-chisle.md