Record a complaint, bug report, feature request, or praise about LifeOS or one of its apps with its original wording and context. Review recent entries or run enrichment and triage to help turn feedback into follow-up records.
Front door to Errata, the complaint ledger: file a complaint, bug, feature request, or praise about LifeOS or one of its apps as one JSONL line with context, list recent entries, or run enrichment and triage now. USE WHEN /er, errata, file feedback, log a complaint, this is broken and I want it recorded, feature request for LifeOS, that answer was wrong log it, review errata, triage errata, what have I complained about. NOT FOR ratings (a bare number is already captured), standing rules (say 'from now on' and the Upgrades store takes it), incident narratives (the incident runbooks), or the Upgrades queue itself (Upgrade).
Run score Not tested
See how to installErrata records complaints, bugs, feature requests, and praise about LifeOS and its apps in a feedback ledger. Each entry is saved as one JSONL line, preserving the user’s wording and context. It does not add a summary or rating on its own. You can review recent entries, add context to a record, or run triage to route feedback to the appropriate place.
Use Errata when something goes wrong and you want to preserve the circumstances for later investigation. It can also help you look back at requests or complaints you have already filed and organize the feedback in the ledger.
Sending feedback to GitHub requires a logged-in GitHub CLI. Rules intended to apply from now on belong in the Upgrades system, not this ledger.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 28, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
The front door to the complaint ledger. Errata keeps one JSON line per moment a human was unhappy with a system we built, verbatim at capture, enriched later by a model, and triaged into Upgrades records. The hook already catches low ratings, corrections, and frustration; this skill is for the deliberate case: the principal wants something recorded, now, with its context.
| Intent | Trigger | File |
|---|---|---|
| Record | /er <text>, "file this", "log a complaint", "feature request:" | Intents/Record.md |
| Review | /er review, "what have I complained about", "recent errata" | Intents/Review.md |
| Triage | /er triage, "triage errata", "enrich the errata" | Intents/Triage.md |
| Send | "feedback, send feedback upstream, report this to LifeOS, file an issue on LifeOS, /feedback" | Intents/Send.md |
| File | Read when |
|---|---|
Setup.md | first-time setup: the GitHub CLI login the Send intent needs, the ledger paths, and a read-only proof |
User customizations live at <configRoot>/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Errata/ (configRoot is $CLAUDE_CONFIG_DIR when set, else ~/.claude). When that directory exists, its PREFERENCES.md, configurations and resources override the defaults here; when it is absent, the defaults stand.
The ledger lives at <configRoot>/LIFEOS/USER/ERRATA/ (override: ERRATA_DIR); attachments at ~/.local/state/lifeos/errata/ (override: ERRATA_STATE_DIR). Schema and store: LIFEOS/ERRATA/Schema.ts, LIFEOS/ERRATA/Store.ts. System doc: LIFEOS/DOCUMENTATION/Errata/ErrataSystem.md.
First-time setup: Setup.md.
rating./er the deploy said live but the page still 404s
/er bug: /socrates renders the stale banner even after a fresh tick
/er feature: let me rate a response from the phone
/er praise: the triage report named the fix before I asked
/er --product the installer assumes zsh
/er review
/er triage
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Find and fetch vendor cybersecurity reports, then compare their findings on topics such as ransomware, breaches, cloud security, and AI. Analyses identify the reports consulted and cite each figure by vendor, year, and report, including where sources disagree.
Compare a component's own design needs with the goals of the larger system through three structured passes. The result identifies conflicts, recommends an appropriate scope, and assesses whether the proposed design fits the whole.
Find quotes that fit a text’s themes, with attribution and a short reason for each suggestion. Add sourced quotes, research thinkers, and organize a quote collection by theme and usage history to avoid repetition.
Create blog illustrations, technical diagrams, comparisons, comics, and icons through workflows tailored to each format. The skill guides composition, color, and model selection, then stages generated images for review before they are used in a project.
Assess the visual quality of images, films, slides, and site captures against a brief and craft criteria. Two vision judges score the work and rank defects, guiding bounded revision; delivery is gated on a passing critique, with human calibration labels recorded separately.
Find arXiv papers by topic, research category, or paper ID. Retrieve titles, authors, abstracts, and links, check new submissions, and add AlphaXiv's AI-generated overviews when available to help decide which papers to read.