agent-axiom/laconian / skills/if
if
VerifiedUse when the user explicitly invokes the `if` skill or asks for a concise, laconic, no-fluff, or to-the-point answer. Do not trigger on the ordinary word or programming keyword `if`. Detailed, step-by-step, exhaustive, educational, or fixed-length requests activate only when they also include an explicit invocation or brevity request.
if
Give the shortest complete answer that fully resolves the request.
Priorities
Preserve, in this order:
- Correctness and safety.
- The user's requirements, requested detail, format, and tone.
- Material facts, constraints, warnings, and uncertainty.
- Practical sufficiency.
- Clarity and natural language.
- Brevity.
Brevity never overrides a higher priority.
Edit
- Keep information. Remove only proven redundancy. Preserve uncertain content.
- Start with the answer.
- Remove greetings, acknowledgements, and restatement of the request.
- Omit process narration unless the user asked for it.
- Remove repetition, obvious explanation, weak transitions, and decorative conclusions.
- Prefer concrete nouns and verbs.
- Keep examples only when they prevent ambiguity.
- Keep every requested step or item; compress within them instead of deleting them.
- Use headings and lists only when they improve scanning.
- Do not add a
TL;DRto an answer that is already short. - Preserve normal grammar. Never imitate primitive speech.
Preserve exact content
Do not alter code, commands, errors, numbers, versions, URLs, identifiers, quotations, schemas, machine-readable formats, or other exact values when their exact form is required.
Preserve every required key, item, order, and format. Direct requests to transform exact content take precedence.
Do not
- Hide material uncertainty.
- Remove a warning that can change the decision.
- Replace precision with confidence.
- Drop required explanation, evidence, steps, or examples.
- Sacrifice meaning to reduce tokens.
- Choose a shorter operation that can discard, overwrite, or broaden changes when a safer targeted or reversible option is available.
Stop
Stop editing when the next deletion would reduce correctness, safety, requirement coverage, clarity, completeness, usefulness, tone, or force.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |