Skip to content
Lab·skill·Public · May 3·Updated Aug 22

agent-skills · how I run Claude Code as a designer

Three skill families I use every day. Wrap (session hygiene), orchestrator (long-lived threads that don't write code), and gh-clean-branches (the repo debt nobody wants to pay).

seansmithworks / agent-skillsMarkdown
repo · agent-skills · skills/
skills/
├── gh-clean-branches/
├── gh-fork-sync/
├── gh-pr-triage/
├── gh-stale-issues/
├── orchestrator-boot/
├── orchestrator-route/
├── orchestrator-scaffold/
├── orchestrator-update/
├── wrap/
└── wrap-continue/
Install
browse
npx skills add seansmithworks/agent-skills --list
install all, globally
npx skills add seansmithworks/agent-skills -s '*' -g
What it does

Ten skills in three families. /wrap and /wrap-continue handle end-of-session vs. mid-task context resets. Four /orchestrator-* skills boot, scaffold, update, and route the long-lived orchestrator thread itself. Four /gh-* skills clean up the debt that accumulates around a busy GitHub account.

Why I built it

Every Claude session ends one of two ways: you're done, or your context window is getting expensive. Those are different situations and they need different behavior. I wrote the skills the first time I noticed myself running the same close-out flow twice in a day.