Skip to content
Back to skills

Pith

BSecurity

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

  • 98 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 26, 2026
ai-agentssecurity

Security analysis

B85/100
  • highPerforms destructive filesystem operations

Pro shows the line behind each finding and how to fix it

Scanned May 27, 2026

npx -y skills add abhisekjha/pith --skill pith --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pith?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pith
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/abhisekjha-pith/badge)](https://www.skillsdirectory.com/skills/abhisekjha-pith)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.