see `state/skills/snappy-default/SKILL.md` Steps .md file to compare - side-by-side diff against snappy-default
snappy-default
description: "Triggers on prompt mention of 'snappy-default'."
What it does for you
Switches your status bar back to the simple summary view.
What it produces
A recent result, so you can see the kind of work it returns.
loading…
How to get it
These run inside the Snappy workspace. Want this working in your business? I set skills like this up with you, in one focused week.
For developers how this skill is built, graded, and how it runs
at a glance- the short version
what's inside - the parts that make up a skill 2/4 present
A skill is just a few plain-text files. Only the main one is required. The rest are optional, added as the work needs them. This is what the skill is made of; how it runs is just below.
state/skills/snappy-default/SKILL.md
present
state/lib/snappy-default.ts
not present
state/bin/snappy-default/
not present
state/skills/snappy-default/AGENTS.md
present
how it's graded - what counts as a good run 3 criteria · 3 deterministic
Each row is one thing a good run has to get right. deterministic means a quick check decides, pass or fail. judge means the AI reads the result and rates it. Grading each piece on its own (instead of one overall score) shows exactly where a run fell short, so the fix is obvious.
how it runs - the shared frame every skill uses 3/5 present
Every skill runs the same way. One part does the work, a separate part checks it, and a short loader hands the AI exactly what it needs for the job. Anything this skill doesn't use shows a one-line note saying why, on purpose, not by accident.
state/log/evals.ndjson - Idempotent: clearing an already-default view is a no-op pass.
what it has learned - fixes written back in over time sample
When a run hits something this skill didn't handle, the fix gets written back into the skill so it doesn't happen again. FIXED means it was corrected on the spot. LOGGED means it's queued for a bigger rewrite. Either way, the skill gets a little better and never makes the same mistake twice.
- Loading feedback rows…
how the work flows- step by step
SKILL.md- the skill, written out in plain English
snappy-default
One job: clear state/log/byline-view.json so the byline returns to its default 1-2 line summary. Counterpart to /snappy-agents and any future channel-flip skills.
Usage
/snappy-default
Steps
- Run:
python3 -c "import json; open('$HOME/projects/snappy-os/state/log/byline-view.json','w').write(json.dumps({'view':'default','set_at':''})+'\n')"
- Confirm by running
bash $HOME/projects/snappy-os/state/bin/statusline.sh
- should show the compact summary, not a per-agent list.
- Log eval row to
state/log/evals.ndjson:
{ts, skill:"snappy-default", verb:"clear-view", score: 1 if cleared else 0}
Why
The 5-min auto-revert in statusline.sh handles the common case (operator forgets they flipped the view). This skill is the manual escape hatch.
Eval
Shape-gate:
state/log/byline-view.jsonhasview: "default"after invocation.- Statusline render does NOT contain the agents-detail header line.
Score = 1 if both pass; else 0.
Gotchas
- Idempotent: clearing an already-default view is a no-op pass.
- Same as
/snappy-agents: no cron, no daemon - statusline reads on render.
Rubric
criteria:
- name: byline_view_is_default
kind: deterministic
check: "The content of $HOME/projects/snappy-os/state/log/byline-view.json should be {\"view\":\"default\",\"set_at\":\"\"} after skill execution."
- name: statusline_shows_compact_summary
kind: deterministic
check: "The output of 'bash $HOME/projects/snappy-os/state/bin/statusline.sh' should not contain an agents-detail header line after skill execution."
- name: eval_row_logged
kind: deterministic
check: "A new row `{ts, skill:\"snappy-default\", verb:\"clear-view\", score: 1}` should be appended to $HOME/projects/snappy-os/state/log/evals.ndjson, where ts is the current timestamp."AGENTS.md- what the AI loads when this skill comes up
snappy-default - loader
Per-turn rules for the snappy-default skill. Full reference: state/skills/snappy-default/SKILL.md. Do not skip these.
Critical Rules
- Idempotent: clearing an already-default view is a no-op pass.
Commands
| ui dashboard | state/skills/snappy-default/resources/ui.openui | |invoke: see state/skills/snappy-default/SKILL.md Steps section |eval log: state/log/evals.ndjson (skill: "snappy-default")
Self-Test
An agent reading this should correctly:
- [ ] Know which lib/bin artifact backs this skill (or that it is prose-only)
- [ ] Know what to write to
state/log/evals.ndjsonafter invoking - [ ] Know the eval mode (auto / shape / manual) from the .md frontmatter
Self-report
If this loader fell short, append a line:
echo "[$(date -u +%FT%TZ)] snappy-default: <what was missing>" >> state/log/loader-feedback.log
<!-- kernel-ok: historical attribution for the PID-loader pattern. -->
Self-correcting loader (PID feedback)
This is the rule that makes loaders learn. Ported from snappy-kernel, where it demonstrably worked: the snappy-dom-cartographer skill mapped Skool admin UI once, every later ship-agent inherited the full map for free.
Before you finish, do two things:
1. Fix gaps (P - proportional). MANDATORY. If this loader didn't cover your case - if you had to read another file, run an undocumented command, work around a wrong selector, or discover a quirk - you MUST attempt an Edit to this AGENTS.md before you log.
- Default action: edit this file. Surgical. Add the missing line, table
row, or code example where it belongs. No restructuring.
- Only
LOGGEDis allowed when: the fix needs >10 lines, spans multiple
files, or requires a structural rewrite. In that case the state/regen/drain.sh queue picks it up asynchronously.
- "I didn't have time" / "it's minor" / "the next agent will figure it out"
are NOT valid reasons. Minor gaps compound - that's the whole point of this loop.
- Concrete example of a valid P-fix: discover
agent-browser screenshot
takes path positionally not as --output <path>. One line in a table. Edit it in. Do not just log it.
- The goal: the next agent never has to leave the loader.
2. Log the result.
echo "[$(date -u +%FT%TZ)] snappy-default: <what was missing or fixed> [FIXED|LOGGED]" >> state/log/loader-feedback.log
FIXED= you patched this loader inline (P-fix).LOGGED= too large for inline; the PostToolUse enqueue + Stop-hook drain
will rewrite the loader from scratch on next session-end.
Do not skip this. Every agent run must leave the system better than it found it. The loader is the setpoint; you are the sensor; the gap is the error signal; closing the gap is the correction.
OpenUI Resource
- Skill-owned OpenUI Lang resource:
state/skills/snappy-default/resources/ui.openui. Read it before rendering or editing this skill's generated component surface. - Treat this resource as a first-class artifact of the skill, not a generic chat response. Improve it when the skill's user-facing output needs to become richer.
- System resources compose OpenUI primitives and inherit SnappyChat tokens. Use
ui_contract: brandedin SKILL.md only for deliberate platform or client visuals.
api.ts- the code it can call
⚠ no api.ts - this skill has no typed action surface
scripts- helper scripts it can run
prose-only skill - 2 inline code blocks live in SKILL.md above (no state/bin/ sidecar yet).
how we check it- the checks, plus the last 10 runs
| timestamp | verb | score | primary_issue | artifact |
|---|---|---|---|---|
| 2026-04-27 04:35Z | - | 1.00 | - | - |
| 2026-04-21 15:58Z | - | 1.00 | - | - |
| 2026-04-21 15:57Z | - | 1.00 | - | - |
| 2026-04-21 03:53Z | - | 1.00 | - | - |
| 2026-04-19 23:24Z | - | 1.00 | - | - |
| 2026-04-27 04:35Z | - | 1.00 | - | - |
| 2026-04-21 15:58Z | - | 1.00 | - | - |
| 2026-04-21 15:57Z | - | 1.00 | - | - |
| 2026-04-21 03:53Z | - | 1.00 | - | - |
| 2026-04-19 23:24Z | - | 1.00 | - | - |