사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/hu3rror/my-skills --skill handoff시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the OS temp directory, resolved explicitly ($env:TEMP on Windows; $TMPDIR, else /tmp, on Linux / WSL / macOS) - not the current workspace. A bare /tmp/... path reaching a Windows-native tool (node, python, pi's write) resolves to C:\tmp\... instead, so pass the resolved absolute path on Windows.
Report the document's path back to the user as a copy-paste-ready pi @ mention: one leading @, the absolute path with forward slashes, wrapped in double quotes, and nothing else on that line. Example: @"C:/path/to/handoff-xyz.md" on Windows (the %TEMP% directory, e.g. under AppData/Local/Temp); @"/tmp/handoff-xyz.md" elsewhere.
The quotes are load-bearing, not decoration: in pi's prompt editor, @ opens a fuzzy file-completion popup, and pressing Enter while it is open applies the popup's top suggestion instead of sending. An unquoted or backslash-slashed Windows path after @ becomes one long completion token that the popup clobbers on Enter. The quoted form (@"...") ends the token at the closing quote, so no popup ever opens and the pasted path survives verbatim. Keep the closing quote last on its line - a . or / after it starts a new completion prefix.
Also give the bare forward-slash path (e.g. C:/path/to/handoff-xyz.md) for CLI launches: start pi with pi @C:/path/to/handoff-xyz.md. The shell strips its own quoting before pi parses @file args, so quote marks there break resolution.
Open the document with a handover preamble addressed to the next agent, worded to force an alignment stop before any work:
You are the incoming agent. Read this document and every artifact it references in full before doing anything else. Then reply with your understanding of four things: the goal, the current state, the next steps, and the risks. Wait for the user's confirmation before starting work.
Include a "suggested skills" section in the document, naming which skills the next agent should load (read each SKILL.md and follow it) and in what order.
Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.