Skip to content
Skills Library
AI & agents · Learning & explanation

sw-explain

/sw-explain

Use when the user asks what a Session Watcher metric means (br, mf, pp, u, wall, sweet, valley) or runs /sw-explain — explains the requested metric in plain language and contextualizes it for the current session.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user asks what a Session Watcher metric means (br, mf, pp, u, wall, sweet, valley) or runs /sw-explain — explains the requested metric in plain language and contextualizes it for the current session.

Original author description

Use when the user asks what a Session Watcher metric means (br, mf, pp, u, wall, sweet, valley) or runs /sw-explain — explains the requested metric in plain language and contextualizes it for the current session.

How it works

  1. Metric glossary
Original SKILL.md headings · 20 lines, 417 words
SKILL.md preview
---
name: sw-explain
description: Use when the user asks what a Session Watcher metric means (br, mf, pp, u, wall, sweet, valley) or runs /sw-explain — explains the requested metric in plain language and contextualizes it for the current session.
---

# Explain a Session Watcher metric

When the user asks about a metric:

1. Call `watcher_status`. Read `br`, `u` (the arm it puts the session on), the lamp and the wallet clock's `phase` from the reply's `reading`; a false `reading.reliable` means the session is still measuring, so say that instead of quoting values. `mf`, `pp`, `wall` and `sweet / valley` are not in `reading`: point the user at where the host shows them, in Claude Code the dashboard at the URL the reply carries, in DSH the Session Watcher tab. `mf` is the hero chart's movable reading; the others are landmarks with no numeric readout.
2. Explain the requested metric in plain language.
3. Contextualize against the flat-valley / AM-GM bound where relevant.

## Metric glossary

- **br (bill premium)** — how far the bill sits above its cost at the sweet spot, as a fraction. `BR_AMBER` and `BR_RED` are the zone boundaries. `br = mf × pp`.
- **mf (movable fraction)** — the share of cost that timing can affect. AM-GM caps it at `√2−1`, which is also why the reminder interval has a natural floor. Whatever sits above that share is cost no restart timing can reach.
- **pp** — the timing-penalty shape term `(u−1)²/(2u)`; minimized at u=1 (the sweet spot).
- **u** — normalized position, accumulated causally: each API call adds the fraction of a restart interval that the conditions in force for it imply, so u only moves forward and loading more files never walks it back. Short of a whole interval = left arm (cost still falling, so the lamp stays white or green); one whole interval = sweet; beyond it = past sweet. The lamp's colour is arm-gated this way; the carry-rent reminder is not, because it reads accumulated rent instead of the position. `uInst`, the `(x−1)/dhat` ratio, is reported beside the causal `u` as a diagnostic that nothing acts on.
- **wall** — where continuing costs more per turn than a full restart.
- **sweet / valley** — the cost-curve minimum, reported as `xSweet` and read off the reference skeleton fitted across the session's own path; the valley around it is flat (small timing penalty).

Frame reassuringly where the numbers allow it: the movable fraction bounds how much of the bill timing can reach at all, and the valley around the sweet spot is flat, so a moderate `br` on the left arm carries no urgency. `br` itself has no ceiling — `pp` grows without bound on the late arm.

Versions

The database has no other skills named sw-explain.

Database snapshot: 13.11.2026 · package version d06849398fb2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90st-explain
    Explain how a piece of code works, why it is built that way, and what that means, in plain language a person can follow. Use for 'how does X work', 'why is it like this', 'teach me this', onboarding to a subsystem, or /st-explain.
  • 90ds-explain
    Explain how a piece of code works, why it is built that way, and what that means, in plain language a person can follow. Use for 'how does X work', 'why is it like this', 'teach me this', onboarding to a subsystem, or /ds-explain.
  • 96explain
    Explain a technical concept (commit, repository, branch, environment variable, port, database, API, front end/back end, deploy, DNS, domain, build, test, lint, dependency, or any other) in plain language, applied to the user's own Builder project. Use when the user asks what a…
  • 90explain-plain
    Explain how an existing feature works in plain, non-technical language. Use when the user wants a non-technical or high-level explanation of existing logic.
  • 100session-handoff
    Capture current session state and generate a handoff prompt for seamless continuation in a new session. Use when context window is filling up, before ending a long session, or when explicitly requested.
  • 95how
    Explain how the current project, a feature, or a code path works in plain language for a beginner. Use when the user wants to understand an existing codebase or how its parts work together.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.