agentleFS
Sign inStart free
alectivismalectivism/maven-template/skills/update/SKILL.md

update

Skill1 starsChanged 6 months agoMITView on GitHub

Quick context checkpoint without ending session. Use when user types /update. Saves progress to session log and updates state if needed.

61 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create, tutorial and 9 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.
  • MicrosoftSkill

    create

    Also in 4 projects that use this

  • bitwize-music-studioSkill

    tutorial

    Provides interactive guided album creation for new users. Use when the user is new to the plugin or asks for a walkthrough of the album creation process.

    Also in 3 projects that use this

  • MicrosoftSkill

    note

    Use this skill to record progress, partial findings, hypotheses, and page-anchored evidence while investigating a long document. Call Note aggressively — any time you read a page and confirm, narrow, or update your understanding of the user's question. Triggers include "jot that down", "save this finding", "note that page 7 says X", or (more often) implicit internal signals — you just learned something and want it recoverable later. Notes persist in the session and Review can select among them. Never paraphrase notes back from memory; write them as you go.

    Also in 4 projects that use this

  • kv0906Skill

    inbox

    Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.

    Also in 4 projects that use this

  • jholhewresSkill

    backup

    Backup and restore — files, databases, and system backups

    Also in 3 projects that use this

  • SidUSkill

    today

    Plan today's work using this repo's workflow. Use when the user asks for /today or phrases like "plan my day", "today's plan", "set my priorities", or "start my day".

    Also in 3 projects that use this

  • +2 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 59 edited versions we read keep these.

  • 5

    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:

    After finishing a chunk of work

    line 22
  2. Distinctive:

    Every hour or so during long sessions

    line 24
  3. Distinctive:

    When context is running low

    line 25
  4. Distinctive:

    Keep it brief. No full summary needed.

    line 36
  5. Very specific:

    If file doesn't exist, create with header: # Session Log: {TODAY}

    line 47
  6. Very specific:

    Only update state/current.md if something actually changed:

    line 50
  7. Distinctive:

    No summary. No "next actions" list.

    line 61
  8. Very specific:

    Don't use for full session wrap-up (use /end for that)

    line 71

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

Update Skill

Lightweight save without ending the session. Use frequently to preserve context.

When to Use

  • User types /update
  • After finishing a chunk of work
  • Before switching contexts
  • Every hour or so during long sessions
  • When context is running low

Process

Step 1: Identify What Changed

Quickly scan the recent conversation for:

  • Topics worked on
  • Decisions made
  • Files created/modified
  • Any state changes needed

Keep it brief. No full summary needed.

Step 2: Append to Session Log

Get today's date: date +%Y-%m-%d

Append to sessions/{TODAY}.md:

## Update: {TIME}
- {what was worked on, 1-3 bullets}

If file doesn't exist, create with header: # Session Log: {TODAY}

Step 3: Update State (if needed)

Only update state/current.md if something actually changed:

  • New open thread
  • Completed item
  • Changed priority
  • New project/task discovered

Skip if nothing material changed.

Step 4: Confirm (minimal)

One line: "Checkpointed: {brief description}"

No summary. No "next actions" list. Just confirm the save.

Output Format

Checkpointed: {2-5 word description of what was saved}

Notes

  • This is intentionally lightweight
  • Don't use for full session wrap-up (use /end for that)
  • Multiple updates per day append to the same session file

Skill created: 2026-01-22

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