xerj-code
FeaturedReference-coding with XERJ. Clone the libraries that already solved your problem, index them locally, and retrieve the exact implementation before writing code — so the agent reads passages instead of re-deriving algorithms across retry loops. Use when starting a task in an unfamiliar API, porting an algorithm, or when you have already looped twice on the same error.
Install
Quality Score: 93/100
Skill Content
Details
- Author
- xerj-org
- Repository
- xerj-org/xerj
- Created
- 4 months ago
- Last Updated
- today
- Language
- Rust
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
ripwire-efficient
A token + accuracy DISCIPLINE for ANY read, not a moment: map before you open files. Reach for it the instant you catch yourself about to open more than ~2 files to figure something out — anywhere in a task. Also the moment you catch yourself typing "let me search the codebase", "let me read that file", or "let me look at a few files first": that sentence IS the trigger. File reads dominate an agent's token cost, and less context is measurably MORE accurate, not just cheaper; a small ranked map beats a fan-out of whole-file reads on both. Code-repair accuracy fell 29% → 3% as context grew 32K → 256K tokens (LongCodeBench), so "read a few more files to be safe" is the instinct this replaces, not a safe default. The reflex is one line: run the cheapest verb that answers the question, then read only the 2-3 files it ranks highest. Fires ALONGSIDE the moment skills (orient, navigate, change-check…), never instead of them. Backed by ripwire (deterministic, on PATH).
xerj
Find current XERJ documentation and API contracts for folder indexing, code retrieval, search, and agent memory. Use when integrating or operating a user-selected XERJ node.
agent-efficiency-retrofit
Analyze recent Claude Code and Codex CLI conversations for repeated inefficient tool calls, token waste, retry loops, avoidable errors, and recurring setup friction; rank improvements by benefit/ease, then implement the smallest durable guardrail after user approval.