agentsclimarketplace

Session tag

Skill youkistudios/session-save-system/skills/session-tag

Local session memory for Claude Code and Codex—capture context, decisions, artifact references, and next state in Markdown and JSON.

Install
npx -y skills add youkistudios/session-save-system --skill session-tag

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Name and classify the current AI work session, save its source-attributed handoff, and route it to checkpoint or close-out. Use when the user asks to tag, name, triage, or finish organizing the current session. This is the triage gate, not the close-out.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.3 KB, 445 tokens by cl100k_base, as published. Nobody here has run it

Session tag — triage gate

Resolve this skill directory as SKILL_DIR. Read CLIENT.md beside this file for the installed client_id. Read GUIDE.md in the shared Session Save home for the complete behavioral contract.

  1. Run python3 "$SKILL_DIR/scripts/session_save.py" doctor --client <client_id> and use the returned home. Stop unless ok is true and migration_required is zero.
  2. Run project-list. Select one exact approved project only when the user’s intent is clear. Similar tags, filenames, repositories, and topic words are not identity proof. On ambiguity, ask from approved choices. For a genuinely new project, wait for explicit confirmation, then run project-register --project <project> --description <description>. Name the session <Project> Topic, purpose before work-done.
  3. Determine FINISHED, LIVE, or STALE using the guide. Default to one arc; split only when the work target changed and new assets or a day boundary exists.
  4. Run begin --client <client_id> --project <project> --name <name> --slug <slug> --status open --require-registered-project [--session-id <id>] [--model <model>]. A stable host session ID is optional; never invent one. Reuse the returned record path.
  5. Write or refresh <record>/tag.md using the guide template. Preserve record.json. Updates are in place; never create another folder manually.
  6. Run sync --client <client_id> --record <record> --status open --gist <concise-gist> --operation tag-written to atomically refresh metadata and the global index.
  7. Route FINISHED → session-summary; LIVE → session-save; STALE → archive guidance. Rename/archive only if the current client exposes that capability and the user confirms.
  8. Print the compact tag receipt with the client label and real record path.

For a sweep, produce _SWEEP-REVIEW.md first and wait for approval. Only sweep chat history the active client actually exposes. Never delete and never imply a cross-client chat sweep.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.