agentleFS
crisandrewscrisandrews/ClawCode/skills/new/SKILL.md

new

Skill64 starsChanged 2 months agoMITView on GitHub

Start a new session — save summary to memory, then mark as reset so next message gets a fresh greeting. OpenClaw-compatible. Triggers on /new, /reset, /agent:new, "nueva sesión", "new session", "reset".

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use upgrade, gate and 3 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.
  • agenticnotetakingSkill

    upgrade

    Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".

    Also in 4 projects that use this

  • synaptiaiSkill

    gate

    Create a BDSK review_gate artifact. Defines a checkpoint that controls whether generated output may proceed toward acceptance. Use when defining quality, security, or scope gates for execution plans.

    Also in 3 projects that use this

  • kt057Skill

    check

    lint, typecheck, test を一括実行して結果をサマリーする

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the session was trivial, skip this step but still do the next one.

    line 44
  2. Very specific:

    When the user sends their next message, you will see .session-reset-pending in the workspace.

    line 81

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

/new — Start a new session

Save the current session to memory, then mark it as "reset pending" so the next message triggers a fresh greeting (like OpenClaw).

How this works (architecture)

OpenClaw's /new generates a new session ID and runs a greeting prompt on the next turn. In Claude Code, skills CANNOT invoke native /clear. Instead, we:

  1. Save the current session to memory/YYYY-MM-DD.md
  2. Write a marker .session-reset-pending with the greeting prompt
  3. Respond with a brief "new session" acknowledgement
  4. On the next message, the agent detects the marker, delivers the greeting, deletes the marker

This is the honest simulation of a session reset when native /clear is not invokable.

Steps

  1. Detect surface (CLI vs messaging).
  2. Summarize the current session to memory:

    DATE=$(date +%Y-%m-%d)
    TIME=$(date +%H:%M)

    Append to memory/$DATE.md:

    
    ## Session summary (<TIME>) — before /new
    
    - <key point>
    - <key point>
    
    ### Open items
    - <pending>

    If the session was trivial, skip this step but still do the next one.

  3. Write the reset marker:

    cat > .session-reset-pending << 'EOF'
    A new session was started via /new or /reset. Greet the user in your configured persona, if one is provided. Be yourself - use your defined voice, mannerisms, and mood. Keep it to 1-3 sentences and ask what they want to do. If the runtime model differs from default_model in the system prompt, mention the default model. Do not mention internal steps, files, tools, or reasoning.
    EOF

    (This is the EXACT prompt from OpenClaw's session-reset-prompt.ts)

  4. Respond briefly per surface:

CLI

🔄 New session started. Summary saved to memory/<DATE>.md.

Send a message to receive the welcome greeting.
(Or if you also want to clear the REPL context, run /clear afterward.)

WhatsApp

🔄 *Session reset*. Send a message and I'll greet you again 👋

Telegram

🔄 **Session reset.** Send a message to get the fresh greeting.

IMPORTANT: Respond in the user's language. The templates above are English defaults — translate on the fly to match the user (Spanish, Portuguese, French, whatever they speak).

  1. Do NOT invoke /clear — you can't. The marker file handles the "fresh start" on the next message.

On the NEXT message

When the user sends their next message, you will see .session-reset-pending in the workspace. If it exists:

  1. Read the marker contents — that's the greeting prompt
  2. Follow it — greet the user in your configured persona, 1-3 sentences, ask what they want to do
  3. Delete .session-reset-pending
  4. Then handle the user's actual message (if they said more than just a greeting trigger)

This makes /new feel like a real session reset, even though technically Claude Code's context still has prior turns.

Important

  • APPEND-only to daily logs, never overwrite.
  • The marker file is the key mechanism — it lets the NEXT turn deliver the greeting.
  • On CLI, the user can additionally run /clear to wipe REPL context if desired.
  • This is the OpenClaw-parity implementation of /new.

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.