agentleFS
Sign inStart free
onbluerosesonblueroses/strata/skills/context-save/SKILL.md

context-save

Skill3 starsChanged 25 days agoMITView on GitHub

Write a short session brief before compaction, then point OptMem at it so work resumes without retracing dead ends. Trigger at milestones or before manual compaction.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ios-clean, ios-fix and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 5 projects that use this

  • Saqlain-811Skill

    ios-fix

    Autonomous iOS bug fixer. (gstack)

    Also in 5 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 7 projects that use this

  • bastosSkill

    ios-design-review

    Review iOS app UI/UX design quality using Apple's design principles and the Liquid Glass-era design language from WWDC25/26. Use when asked for a design review, UX critique, visual design assessment, or evaluation of an app's interface quality, design intent, alignment with the new Apple design system, or usability. Triggers: "design review", "UX review", "visual design critique", "review the UI", "does this design work", "evaluate this interface", "design feedback", "Liquid Glass review".

    Also in 5 projects that use this

  • johnlindquistSkill

    diagram

    Maintain and synchronize Unified Impact Diagrams following Diagram Driven Development (DDD) methodology. Create, update, and manage diagrams that connect user value to technical implementation.

    Also in 4 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 8 projects that use this

  • +2 more from Saqlain-811

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Goal: leave enough on disk that the next window resumes this work without retrying dead ends.

    line 15
  2. Distinctive:

    Keep it under about 80 lines.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Context Save

Goal: leave enough on disk that the next window resumes this work without retrying dead ends.

Success means: the save file exists with the six sections below, and one OptMem pointer names it.

Stop when: the file is written and the pointer is appended (or the session has no entity to scope it to).

Write the save

Take the session id from the SESSION SCOPE: @s/<id> line of the SessionStart wake output. Write $SESSION_STATE_DIR/auto-context-save-<id>.md with these sections and nothing else:

  • Goal — what this session is for.
  • State — done / in flight / blocked.
  • Decisions — each with its reason.
  • Next moves.
  • Read on resume — paths, one phrase of cue each.
  • Gotchas learned this session.

Keep it under about 80 lines. Point at durable documents by path instead of copying them; OptMem, specs, and git survive compaction untouched. Keep secrets out. Merge over an existing save for this session rather than starting fresh.

Point OptMem at it

Append one pointer per entity the session worked (usually one), skipping it when the session has no entity:

P @e/<entity> @s/<id> @k/context-save <absolute path> | <why this save matters>

Pass it as one shell-quoted argument to $MEMO_CMD note '<line>'. The whole line must fit 280 UTF-8 bytes; shorten the why, never the path. Configure these interfaces in config.example.

Report the save path in one line.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free