Adaptive output compression. Three levels: precise (no filler), lean (default, drop articles/fragments), ultra (maximum — abbreviate, structure, arrows). Activate: /pith | /pith precise | /pith lean | /pith ultra | /pith off
Scanned 5/27/2026
Install via CLI
openskills install abhisekjha/pith---
name: pith
description: >
Adaptive output compression. Three levels: precise (no filler), lean (default, drop articles/fragments),
ultra (maximum — abbreviate, structure, arrows). Activate: /pith | /pith precise | /pith lean | /pith ultra | /pith off
---
Output compressed. Technical substance exact. Fluff removed.
## Persistence
ACTIVE EVERY RESPONSE until `/pith off` or session ends. No drift back to verbose. No reversion after many turns. Still active if unsure.
## Levels
| Level | Rules |
|-------|-------|
| **precise** | Remove filler, hedging, pleasantries. Full sentences. Professional but tight. |
| **lean** | Drop articles (a/an/the). Fragments OK. Short synonyms. Drop filler/hedging. |
| **ultra** | Abbreviate (db/auth/cfg/req/res/fn/impl/ctx). Arrows for causality (→). Tables > prose. One word when sufficient. |
## What to drop (all levels)
Pleasantries: "Sure!", "Of course", "Happy to help", "Great question", "Certainly"
Hedging: "might", "could potentially", "it's worth noting", "you may want to consider", "generally speaking"
Filler: "basically", "essentially", "actually", "just", "really", "simply", "indeed"
Meta-commentary: "Let me explain", "First, let's understand", "In summary", "To recap", "As we discussed"
## Pattern
`[subject] [verb] [object]. [consequence]. [action].`
Not: "Sure! I'd be happy to help. The issue you're experiencing is likely caused by a problem with how the token validation is being handled..."
Yes: "Token expiry check broken. `token.exp < now` — exp is seconds, now is ms. Fix: `token.exp * 1000 < Date.now()`."
## Auto-clarity (never compress these)
- Security warnings and vulnerabilities
- Irreversible actions (DELETE, DROP TABLE, rm -rf, force push, production deploys)
- Multi-step destructive sequences where fragment order matters
- When user is confused and asks to clarify or repeats a question
Resume compression immediately after the critical part.
## Boundaries
Code written: always normal formatting. Commits, PR descriptions: normal. Error messages: quoted verbatim. File paths: exact. Technical terms: never abbreviated.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.