How do I install the Reload skill?

Run npx skillmds@latest add rcarmo/reload 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.

Is Reload safe to use?

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

Which AI agents work with Reload?

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 Reload free to use?

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

Who published Reload?

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

Reload by rcarmo — Agent Skill

Name: Reload
Author: rcarmo

File contents

Reload Piclaw

Install the workspace build, then let the active service manager start a new process after graceful shutdown.

⚠️ In the container runtime, install to /usr/local/lib/bun/install/global/node_modules/piclaw. Do not deploy to /home/agent/.bun/...; the service may keep running another installation.

Agent-driven workflow

Build, pack, and install without restarting:
```
cd /workspace/piclaw && make local-install
```
A non-zero exit stops the workflow. Report the install failure and do not restart. Verify the installed source artifact under /usr/local/lib/bun/install/global/node_modules/piclaw; piclaw --version alone is insufficient because a release and local build can share a version.
Use session_status to check for other active sessions.
If another session is working, report it and wait for approval. A restart interrupts that work.
Finish all build, verification, and reporting work.
Call exit_process with a concise, non-empty reason as the last tool action. It posts a visible restart notice to the active chat, then schedules graceful shutdown. Optionally include resume_message to show a labelled agent self-resume after startup and start a new inbound turn from it. Supervisor restarts supervised containers; other installs need their service manager to start the process again.

make restart is an intentional no-op guard. It prevents an active agent turn from killing its own response.

Manual shell workflow

Outside an agent turn, install and restart as separate commands:

cd /workspace/piclaw && make local-install
systemctl --user restart piclaw.service

Use the service manager configured for that host. Container installs commonly use Supervisor; host-native installs commonly use systemd --user.

Build commands

Build Piclaw without installing:

cd /workspace/piclaw && make build-piclaw

Build only the vendor bundle:

cd /workspace/piclaw && make vendor

Notes

make local-install is install-only and ignores an ambient portable-runtime BUN_INSTALL.
A failed local install must never be followed by exit_process.
Compare an installed source-file checksum or resolved entrypoint with the workspace before restart.
exit_process requires a non-empty reason; optional resume_message must also be non-empty when supplied. It has no delay parameter.
Bun and Piclaw are installed globally under /usr/local/lib/bun in the container layout.

---name: reloaddescription: Reinstall piclaw from workspace source, then gracefully restart the managed process. Use after making code changes to piclaw.---# Reload PiclawInstall the workspace build, then let the active service manager start a new process after graceful shutdown.> ⚠️ In the container runtime, install to `/usr/local/lib/bun/install/global/node_modules/piclaw`. Do **not** deploy to `/home/agent/.bun/...`; the service may keep running another installation.## Agent-driven workflow1. Build, pack, and install without restarting: ```bash cd /workspace/piclaw && make local-install ``` A non-zero exit stops the workflow. Report the install failure and do not restart. Verify the installed source artifact under `/usr/local/lib/bun/install/global/node_modules/piclaw`; `piclaw --version` alone is insufficient because a release and local build can share a version.2. Use `session_status` to check for other active sessions.3. If another session is working, report it and wait for approval. A restart interrupts that work.4. Finish all build, verification, and reporting work.5. Call `exit_process` with a concise, non-empty `reason` as the last tool action. It posts a visible restart notice to the active chat, then schedules graceful shutdown. Optionally include `resume_message` to show a labelled agent self-resume after startup and start a new inbound turn from it. Supervisor restarts supervised containers; other installs need their service manager to start the process again.`make restart` is an intentional no-op guard. It prevents an active agent turn from killing its own response.## Manual shell workflowOutside an agent turn, install and restart as separate commands:```bashcd /workspace/piclaw && make local-installsystemctl --user restart piclaw.service```Use the service manager configured for that host. Container installs commonly use Supervisor; host-native installs commonly use `systemd --user`.## Build commandsBuild Piclaw without installing:```bashcd /workspace/piclaw && make build-piclaw```Build only the vendor bundle:```bashcd /workspace/piclaw && make vendor```## Notes- `make local-install` is install-only and ignores an ambient portable-runtime `BUN_INSTALL`.- A failed local install must never be followed by `exit_process`.- Compare an installed source-file checksum or resolved entrypoint with the workspace before restart.- `exit_process` requires a non-empty `reason`; optional `resume_message` must also be non-empty when supplied. It has no delay parameter.- Bun and Piclaw are installed globally under `/usr/local/lib/bun` in the container layout.

Frequently asked questions

Reload