simplicio-orient

Routes fact queries to shell commands and clamps command output to reduce token usage.

9|Updated May 8, 2026
One-click install
npx skills add https://github.com/simpletibr/simplicio-loop-marketing --skill simplicio-orient-simpletibr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simplicio-orient
Source: https://github.com/simpletibr/simplicio-loop-marketing/tree/main/.claude/skills/simplicio-orient
Command: npx skills add https://github.com/simpletibr/simplicio-loop-marketing --skill simplicio-orient-simpletibr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM agents waste large amounts of context tokens narrating filesystem facts, git state, and verbose build/test output that the terminal can answer exactly and cheaply. This Skill substitutes deterministic shell commands for LLM reasoning about facts and clamps command output by 60-90% before it reaches context. ## Core Features & Use Cases - Terminal-first substitution table: Cross-platform commands (git, gh, rg, python3) for file existence, branch state, PR lookups, disk space, and JSON extraction, so facts come from the shell instead of LLM guesses. - Output-reduction catalog: Per-command clamp recipes for test runners, type checks, diffs, lints, and commits, with signal-tiered truncation caps that always preserve error lines. - Failure-safe tee cache: On non-zero exits, full unfiltered output is written to a log file and only the path is surfaced, with a retrieve convention to fetch the original on demand. - Use Case: While running a CI fix loop, an agent clamps a raw tsc --noEmit output from roughly 2000 tokens down to about 80 tokens of error lines, keeping the full log recoverable via the tee cache if more context is needed. ## Quick Start Ask the agent to check the current git branch and run the test suite using terminal-first commands with clamped output instead of narrating the results.

Frequently Asked Questions about simplicio-orient

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce token usage from shell command output in AI agents?

Clamp command output before it reaches context using per-command recipes: collapse successful runs to one line, keep only error lines from type checks and test runners, and dedup repeated lines with counts. Full output stays recoverable in a tee log file on failure.

How to get git branch and PR status without wasting LLM tokens?

Run deterministic commands like `git rev-parse --abbrev-ref HEAD` for the branch and `gh pr list --head <branch> --json number` for PR lookups. The terminal answers these facts exactly, while the LLM would only approximate them at higher token cost.

Does output clamping work on Windows, Linux, and macOS?

Yes, the substitution table prefers cross-platform tools like git, gh, rg, and python3 so one command works everywhere. OS-specific fallbacks such as Test-Path or nproc are used only when no cross-platform alternative exists.

What happens when a clamped command fails or output is truncated?

On any non-zero exit, the full unfiltered output is written to a tee log file and only the path is surfaced in context. The agent can retrieve the original by path with optional line ranges or grep patterns, so no failure detail is permanently lost.

When should output clamping be skipped?

Never clamp structured JSON output piped to another consumer, write or confirm operations, or security-sensitive commands like force-push and production deploys. Safety overrides brevity, and any error or warning line forces full signal-preserving truncation instead of collapse.