Przejdź do treści
Biblioteka skilli
Produktywność osobista · Pisanie

Errata

/Errata

Zapisuje reklamacje, błędy, prośby o funkcje i pochwały dotyczące LifeOS i jego aplikacji jako wpisy JSONL.

Repozytorium
LifeOS ↗
Licencja
MIT
Ostatnia zmiana repozytorium
05.11.2026

Ocena i bezpieczeństwo

95/ 100Klasa: dobry
Format20 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
9
Skrypty
2
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 05.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: Tools/Er.ts, Tools/Send.ts

Co robi i kiedy

Zapisuje reklamacje, błędy, prośby o funkcje i pochwały dotyczące LifeOS i jego aplikacji jako wpisy JSONL.

Wyzwalacze z opisu

from now on
Oryginalny opis (EN)

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 Upg

Jak działa

  1. Ideal State
  2. Intent Routing
  3. Data & Config
  4. Gotchas
  5. Examples
Sekcje z nagłówków SKILL.md, w oryginale · 50 linii, 437 słów
Podgląd SKILL.md
---
name: Errata
evals:
  manual:
    reason: "whether a filed complaint carried enough context to investigate later is judged at triage time"
    falsifier: "a triage report cannot name what was requested or what the system was doing for an entry filed through /er"
metadata:
  short-description: "File feedback about LifeOS or one of its apps into the Errata complaint ledger; list recent entries; run enrichment and triage."
version: 1.2.1
description: "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)."
---

# Errata

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.

## Ideal State

- Every deliberate complaint, bug, feature request or praise the principal files becomes exactly one ledger line holding the principal's own words and enough context to investigate it a month later.
- Nothing in the ledger is invented at capture: no paraphrase, no estimated rating, no summary or tag the principal did not give, and no standing rule filed here as well as in the Upgrades store.
- Review and triage work from the same live ledger the hook and the daily job write, so what the principal reads back and what becomes an Upgrades record is one set.

## Intent Routing

| 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` |

### References

| File | Read when |
|---|---|
| `Setup.md` | first-time setup: the GitHub CLI login the Send intent needs, the ledger paths, and a read-only proof |

## Data & Config

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](Setup.md).

## Gotchas

- **Capture is verbatim because nothing can regenerate it.** The no-paraphrase and no-estimated-rating rules in Record exist because an earlier failure log let machine-filled ratings in, and those fabricated values poisoned every analysis built on it (2026-09-17 design decision). The schema validator refuses a machine source that carries a `rating`.

## Examples

```
/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
```
Pliki w paczce (9)
  • SKILL.md 4 KB
  • Setup.md 2 KB
  • Intents/Record.md 2 KB
  • Intents/Review.md 1 KB
  • Intents/Send.md 3 KB
  • Intents/Triage.md 1 KB
  • Tools/Er.ts 4 KB
  • Tools/Send.help.md 6 KB
  • Tools/Send.ts 26 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · danielmiessler/LifeOS95MIT
donald-ada/workinggenius100MIT

Migawka bazy z 13.11.2026 · wersja paczki 61ea44fe1167 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 95HillClimb
    Ulepsza elementy systemu LifeOS eksperymentami: wyszukuje błędy w Errata i Assay, sprawdza zmiany na danych kontrolnych i zapisuje utrzymane zabezpieczenia.
  • 100notion-lifeos
    Obsługuje osobisty system LifeOS w Notion (metoda PARA): dodawanie zadań, notatek i projektów, prowadzenie dziennika oraz przeszukiwanie zadań i notatek.
  • 95Migrate
    Pobiera treści zewnętrzne (markdown, instrukcje Cursor i OpenAI, eksporty Obsidian, Notion i Apple Notes), klasyfikuje je względem taksonomii LifeOS i zapisuje z informacją o pochodzeniu.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.