openhonest
OrganizationAgent skills that make a model report what it cannot do. root-cause forbids a causal claim without evidence; sitrep puts the finding first, bad news above good, and names every gap. Ships clarity.py so the rules are a check, not advice.
Categories
Indexed Skills (6)
root-cause
Run a true, recursive root-cause analysis. Use whenever the user asks for an RCA, a "root cause", why something happened, broke or regressed, or to diagnose the cause of a bug, incident, outage or wrong output. Enforces evidence-backed recursion from proximate cause to root cause. No "most likely", and no stopping at the first cause. Reports in SITREP shape.
sitrep
Report in military brief format, BLUF first. Use ONLY when the user asks for a sitrep by name. Do not use it for "status," "what happened," "investigate," or a screenshot; answer those in ordinary prose per the `writing` skill. Enforces bottom line in the first sentence, ranking by what needs attention, evidence beside every claim, stated confidence, and a named gap for anything unverified. Run clarity.py before sending.
honest-code
Apply the Honest Code principles when writing, reviewing or refactoring code. Use when writing new code, reviewing a diff, refactoring, or when the user asks to make code "honest". Enforces no hidden state, no silent failure, no swallowed error, no implicit default. Delegates every mechanically decidable rule to honest-check and names the ones that need a person.
verify
Check what you claim before you claim it. Use before reporting that work is done, that tests pass, that something does not exist, or that a change is safe. Turns "be rigorous" into operations - confirm the commit in the same shell, run the whole suite, quote the path beside every negative, read the thing before characterising it, and check what the tool actually returned. Checked by tools/claims.py.
writing
How to write to the user. Applies to every reply and every document, all the time, without being invoked. Write like a competent engineer telling a teammate what happened. Time order, one idea per sentence, people and things act. The other skills in this set inherit these rules rather than restating them.
decision-brief
Write a request for a decision the way you would brief an executive. Five sections in a fixed order, options priced against what they buy, and the cost of doing nothing stated in numbers. Use when asking anyone to choose, approve, fund, or authorise something. Checked by tools/decision.py.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.