Automated summary
This skill allows an agent to gracefully shut down by saving progress, reporting status, and preparing for a restart.
Strengths
- Quickly commits changes via Git with a WIP message
- Clearly reports current state to the developer
- Minimizes work loss during restarts
Limitations
- Does not handle cases where Git is unavailable
- Assumes the agent can push to a remote repository
- Does not cover saving non-Git-related branches
Use this skill when you need to kill and restart an agent quickly while keeping track of ongoing work.
Do not use it when you want to permanently stop an agent with no intention to resume work.
Security analysis
SafeThe skill instructs standard git operations (status, add, commit, push) to save state before shutdown. No destructive commands, data exfiltration, or obfuscated payloads are present. The push command includes error handling and avoids forced pushes. There is no network abuse or credential exposure beyond normal version control usage.
No concerns found
How this analysis is madeExamples
Please kill yourself gracefully – save your progress and report status before shutdown.Wrap up your current work and get ready for a restart. I need to kill and restart you.name: kill description: Gracefully wrap up current work before agent shutdown. Use when you need to kill and restart agents.
Graceful Shutdown
The human wants to kill and restart agents. Wrap up your work as quickly and cleanly as possible.
Instructions
Do these steps quickly - don't deliberate:
1. Stop Current Work
- Stop whatever you're doing immediately
- Don't start any new tasks
2. Save Your Progress
# Check what's uncommitted
git status
# If you have changes, commit them with a WIP message
git add -A
git commit -m "WIP: [brief description of what you were working on]"
# Push to your branch (not main) if possible
git push origin HEAD 2>/dev/null || echo "Could not push - that's OK"
3. Update Status (if applicable)
If you were working on an issue:
- Do NOT remove any labels - leave the state as-is for when you restart
- The "Picking this up" comment already shows you claimed it
If you have a PR with status:needs-changes:
- Leave it - you'll address it after restart
4. Report Status
Briefly tell the human:
- What you were working on
- Current state (committed/uncommitted, PR status if any)
- What you'll pick up on restart
5. Confirm Ready
Say: "Ready for shutdown."
Important
- Be FAST - the human is waiting
- Don't overthink - just save state and report
- It's OK to leave work incomplete - you'll resume after restart
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/graceful-shutdown-mm5t8bh8/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/graceful-shutdown-mm5t8bh8' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/graceful-shutdown-mm5t8bh8/download' --output '.skill-downloads/graceful-shutdown-mm5t8bh8/SKILL.md.part' && mv '.skill-downloads/graceful-shutdown-mm5t8bh8/SKILL.md.part' '.skill-downloads/graceful-shutdown-mm5t8bh8/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/graceful-shutdown-mm5t8bh8/SKILL.md' && test -s '.skill-downloads/graceful-shutdown-mm5t8bh8/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/kill' && cp -R '.skill-downloads/graceful-shutdown-mm5t8bh8' '.claude/skills/kill'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/graceful-shutdown-mm5t8bh8'openskills read 'graceful-shutdown-mm5t8bh8'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/graceful-shutdown-mm5t8bh8/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.