agentsclimarketplace

Session handoff

Skill bglglzd/agent-workflows/plugins/agent-workflows/skills/session-handoff

Portable Markdown workflows for AI coding agents — session handoffs, project audits, and product discovery.

Install
npx -y skills add bglglzd/agent-workflows --skill session-handoff

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

  • 24 days oldThe repository was created 24 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.
  • 1 stars1 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

Capture a durable, privacy-safe handoff at the end of a coding or research session. Use when Codex must preserve repository state, decisions, validation results, blockers, and exact next steps so the next human or AI agent can resume without rediscovering context.

SKILL.md

1.8 KB, 332 tokens by cl100k_base, as published. Nobody here has run it

Session Handoff

Preserve the state needed to resume work accurately. Do not treat a chat summary as durable project memory.

Workflow

  1. Inspect the workspace before writing: git status, current branch, latest commit, relevant changed files, project docs, and safe command output from this session.
  2. Reuse the project's existing memory or handoff convention. If none exists, create docs/ai/SESSION_CONTEXT.md as the current source of truth and docs/ai/SESSION_LOG.md as an append-only dated record.
  3. Update the current-context file with:
    • goal and current repository state;
    • completed changes with relevant file paths;
    • decisions and rationale;
    • system, deployment, PR, issue, or external-service context that is safe to record;
    • commands run and validation results;
    • risks, blockers, and unknowns;
    • ordered next actions and a precise resume checklist.
  4. Append a concise dated log entry with the completed work, validation, and next action.
  5. Finish by naming the updated files, the highest-priority next action, and the remaining unknowns.

Guardrails

  • Never copy tokens, passwords, private URLs, connection strings, .env values, or customer data into project memory.
  • Do not modify application code, infrastructure, or external systems merely to create a handoff.
  • Preserve history instead of overwriting useful records.
  • Mark unverified details as Unknown. Do not infer them from incomplete context.
  • Include exact file paths, branch or PR identifiers, and commands wherever they make resumption faster.

Gives 0 of the 12 instructions most agent orchestration skills give in 332 tokens

Counted across 742 of the 995 authors here whose files we hold, read 2026-08-07

  • reference existing artifacts by path or URLin 53 of 742, across 25 files
  • run the full test suite after integrating changesin 51 of 742, across 19 files
  • dispatch one agent per independent problem domainin 50 of 742, across 17 files
  • verify fixes do not conflictin 45 of 742, across 13 files
  • include a suggested skills section in the documentin 45 of 742, across 17 files
  • redact sensitive informationin 41 of 742, across 11 files
  • save to the temporary directory of the operating systemin 39 of 742, across 10 files
  • tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
  • spot check agent changes for systematic errorsin 34 of 742, across 7 files
  • write a handoff document summarising the current conversationin 31 of 742, across 6 files
  • Assign each agent a specific scopein 23 of 742, across 8 files
  • provide specific scope and clear goalin 23 of 742, across 5 files

Said here and by no other author read

  • reuse the project's existing handoff convention
  • create context and log files if no convention exists
  • update the current-context file with repository state
  • record completed changes with file paths
  • list ordered next actions and a resume checklist
  • append a concise dated log entry

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

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.