agentleFS
potentiavisionpotentiavision/partner-jarvis-starter/.claude/skills/session-continuity/SKILL.md

session-continuity

Skill0 starsChanged 4 months agoMITView on GitHub

Use at session start, session end, project switches, or whenever current goal and next action are uncertain.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify the current repository path.

    line 10
  2. Very specific:

    Read config/operator_profile.json, state/SESSION_STATE.md, and state/DECISIONS.md.

    line 11
  3. Distinctive:

    If files conflict, ask the operator which fact is current before acting.

    line 13
  4. Very specific:

    Update state/SESSION_STATE.md with verified current truth.

    line 17
  5. Very specific:

    Add only durable architectural choices to state/DECISIONS.md.

    line 20
  6. Distinctive:

    Never store secrets or raw private conversations.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 6 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

Session Continuity

Start

  1. Verify the current repository path.
  2. Read config/operator_profile.json, state/SESSION_STATE.md, and state/DECISIONS.md.
  3. Summarize active goal, current focus, blocker, and exact next action.
  4. If files conflict, ask the operator which fact is current before acting.

End or switch

  1. Update state/SESSION_STATE.md with verified current truth.
  2. Include one exact next action and all unresolved blockers.
  3. Append checks and outcomes to state/ACTION_LOG.md.
  4. Add only durable architectural choices to state/DECISIONS.md.
  5. Never store secrets or raw private conversations.

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.