← the whole session plugin/skills/info/SKILL.md

Summarize the session's UX intent in one sentence and evaluate compaction value.

Session Info

Before your output, print ## INFO_SUMMARY on its own line. This marks the block so it's easy to find again in the transcript, and so the local record-writing step below (or, if the person later builds their own compaction-admin surface, an automated extractor) can find it.

1. UX intent (one sentence)

Eval and discern what the exact specific UX change will be if the full intent of this session — articulated and/or deduced from the user's words — is realized. State it in one nuanced sentence.

Keep it high-level and purposeful. Not a list of everything done — the WHY behind it all.

WRONG: "When a visitor lands on the site, they encounter 17 articles (4 featured pieces + 13 deep dives) reorganized under a single new section with a new callout at the top..."

RIGHT: "Fully optimize the site for the specific experience a first-time evaluator needs, with visible evidence of the work actually functioning."

2. Compaction value

On the next line, state:

Compaction Gains: {num}%

Calculate by evaluating the quantity of new discernments, progress, insights, principles, and outcomes generated since the last compaction in this session. If no compaction has happened yet this session, rank as 100%.

Save it somewhere real (MANDATORY)

A summary that only exists in the transcript is lost the moment the session ends unless something writes it down. After printing the one-sentence intent and the Compaction Gains: N% line:

  1. Get this session's id: alignment-harness session-id. This resolves the real per-session id safely even when multiple agents are running concurrently — never read it from a shared file that could return the wrong session's id under concurrency.
  2. Append one line to the local record store:
    DIR=$(alignment-harness records session-info)
echo '{"sessionId":"<id from step 1>","intent":"<the one-sentence intent, exactly as stated above>","gains":<the integer from Compaction Gains>,"at":"<ISO timestamp>"}' >> "$DIR/log.jsonl"
  3. If the person has their own compaction-admin surface or API configured for this project, write there too (or instead) — this local file is the default that always works, not a replacement for something they've already built.

This is a small, cheap step and there's no reason it should silently do nothing — if you skip it, say so, rather than printing the summary and leaving it to evaporate at session end.