How do I install the Aget Wind Down skill?

Run npx skillmds add majiayu000/aget-wind-down in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Aget Wind Down skill do?

End AGET session with state capture and sanity checks It is listed under Coding & Dev Tools on SkillMD.

Is Aget Wind Down safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aget Wind Down?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aget Wind Down free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aget Wind Down?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aget Wind Down by majiayu000 — Agent Skill

Name: Aget Wind Down
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

aget-wind-down

End an AGET agent session properly. This skill runs the wind-down protocol to capture session state, run sanity checks, and prepare handoff notes.

Instructions

When this skill is invoked:

Run the wind-down script:
```
python3 scripts/wind_down.py
```
The script will:
- Run sanity checks (housekeeping protocol)
- Capture session duration and activity
- Scan for pending work in planning/
- Generate session summary
- Suggest commit message if changes exist

If user provides notes, pass them to the script:

python3 scripts/wind_down.py --notes "User provided notes here"

Create session record file at sessions/SESSION_YYYY-MM-DD_descriptive_title.md:
- Use YAML frontmatter with Session Metadata Standard v1.0 fields (date, duration_minutes, objectives, outcomes)
- Include optional fields: learnings, commits, files_changed, pain_points, next_steps
- Add session body sections: Objectives, Deliverables, Outcomes, Lessons, Blockers, Files Changed
- Capture wind-down state in the file: sanity result, pending work, git diff stats
- Reference schema: .aget/schemas/session_metadata_v1.0.yaml
- Reference exemplar: sessions/SESSION_2025-12-03_kb_enhancement.md
If re-entrancy guard blocks (exit code 4), inform user:
- Wind-down was run recently (5-minute cooldown)
- Use --force to bypass if needed

Required Outputs

Every wind-down must produce:

Terminal summary (stdout) — sanity, changes, pending, suggested commit
Session record file — sessions/SESSION_YYYY-MM-DD_*.md (L004: process governance)

Output Format

Present the wind-down summary:

Wind Down Complete
- Session: [duration]
- Sanity: [healthy/warnings/errors]
- Pending: [N] items in planning/
- Changes: [staged/unstaged counts]
- Suggested commit: "[message]"

Error Handling

Exit code 0: Clean close, sanity healthy
Exit code 1: Close with warnings (report them)
Exit code 2: Close with errors (require acknowledgment)
Exit code 3: Configuration error
Exit code 4: Re-entrancy guard active

Options

--skip-sanity: Skip sanity check (not recommended)
--force: Bypass re-entrancy guard (L468)
--json: Machine-readable output

L004: Process Governance Gap (session file as required output)
L468: Re-entrancy Protection
L532: Skills vs Learnings Distinction
CAP-SESSION-003: Wind Down Protocol

---name: aget-wind-downdescription: End AGET session with state capture and sanity checks--- # aget-wind-down End an AGET agent session properly. This skill runs the wind-down protocol to capture session state, run sanity checks, and prepare handoff notes. ## Instructions When this skill is invoked: 1. Run the wind-down script: ```bash python3 scripts/wind_down.py ``` 2. The script will: - Run sanity checks (housekeeping protocol) - Capture session duration and activity - Scan for pending work in `planning/` - Generate session summary - Suggest commit message if changes exist 3. If user provides notes, pass them to the script: ```bash python3 scripts/wind_down.py --notes "User provided notes here" ``` 4. Create session record file at `sessions/SESSION_YYYY-MM-DD_descriptive_title.md`: - Use YAML frontmatter with Session Metadata Standard v1.0 fields (date, duration_minutes, objectives, outcomes) - Include optional fields: learnings, commits, files_changed, pain_points, next_steps - Add session body sections: Objectives, Deliverables, Outcomes, Lessons, Blockers, Files Changed - Capture wind-down state in the file: sanity result, pending work, git diff stats - Reference schema: `.aget/schemas/session_metadata_v1.0.yaml` - Reference exemplar: `sessions/SESSION_2025-12-03_kb_enhancement.md` 5. If re-entrancy guard blocks (exit code 4), inform user: - Wind-down was run recently (5-minute cooldown) - Use `--force` to bypass if needed ## Required Outputs Every wind-down must produce: 1. Terminal summary (stdout) — sanity, changes, pending, suggested commit 2. Session record file — `sessions/SESSION_YYYY-MM-DD_*.md` (L004: process governance) ## Output Format Present the wind-down summary: ``` Wind Down Complete - Session: [duration] - Sanity: [healthy/warnings/errors] - Pending: [N] items in planning/ - Changes: [staged/unstaged counts] - Suggested commit: "[message]" ``` ## Error Handling - Exit code 0: Clean close, sanity healthy - Exit code 1: Close with warnings (report them) - Exit code 2: Close with errors (require acknowledgment) - Exit code 3: Configuration error - Exit code 4: Re-entrancy guard active ## Options - `--skip-sanity`: Skip sanity check (not recommended) - `--force`: Bypass re-entrancy guard (L468) - `--json`: Machine-readable output ## Related - L004: Process Governance Gap (session file as required output) - L468: Re-entrancy Protection - L532: Skills vs Learnings Distinction - CAP-SESSION-003: Wind Down Protocol

Frequently asked questions