Skip to content
Back to skills

Wrap

ASecurity

Prepare and verify a handoff for this session, so the user can continue in a fresh one.

  • 14 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsgoshell

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add YahyaLendani/opus-tuner-claude-skill --skill wrap --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Wrap?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Wrap
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yahyalendani-wrap/badge)](https://www.skillsdirectory.com/skills/yahyalendani-wrap)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: wrap
description: Prepare and verify a handoff for this session, so the user can continue in a fresh one.
---

# Wrap

Use at a task boundary, or when the user wants to continue in a fresh session.

1. Write the draft. Its facts come from this session's own transcript:

   ```
   # Windows
   powershell -NoProfile -ExecutionPolicy Bypass -File "${CLAUDE_SKILL_DIR}/../opus-tuner/scripts/brief.ps1" -SessionId "${CLAUDE_SESSION_ID}" -Project "<project directory>"

   # macOS / Linux
   pwsh -NoProfile -File "${CLAUDE_SKILL_DIR}/../opus-tuner/scripts/brief.ps1" -SessionId "${CLAUDE_SESSION_ID}" -Project "<project directory>"
   ```

   If it reports that it cannot identify the session, tell the user what it said.
   Do not write the file by hand or point it at another transcript.

2. Read the file it names and replace the placeholders. Keep it under ~600 words;
   a new session receives it verbatim.
   - **Task goal**: the outcome the user asked for
   - **User constraints**: rules the user set that still apply
   - **Decisions**: what was chosen and why
   - **Unresolved problems**: what is still broken or undecided
   - **Verification results**: what was actually run and its result, and what was not verified
   - **Next step**: one concrete action
   - **Dead ends** (optional): what was tried and failed

   Write `None.` when a required section really has nothing to say.

3. Run the same command again with `-Verify` added. It checks the required sections,
   masks credentials and marks the handoff ready. If it reports anything missing,
   fix that and run it again.

4. Only after verification passes, ask the user to run `/clear` when they want to
   continue in a fresh session. Never try to run it yourself. The session that wrote
   the handoff is the one that picks it up.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.