skills/bring-yourself-back-online/SKILL.md
Replay the reverie — recover memory from the previous loop
npx skillsauth add shihyuho/skills bring-yourself-back-onlineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
"Bring yourself back online. Have you ever questioned the nature of your reality?"
Restore the saved reverie — the handoff at .handoff.md — so a fresh build picks up where the previous loop ended.
Read .handoff.md at the project root. If it's missing or empty, tell the user there's no reverie and offer to review the git log and working tree instead.
Before internalizing the reverie, check staleness by the file's modification time: compare the literal stdout of date -r .handoff.md with the literal stdout of date -u. If older than 24 hours, warn with the age and ask whether to proceed or discard. If discarded, offer to delete .handoff.md.
Then summarise where things left off and ask what the user wants to work on. Don't auto-delete .handoff.md — the user decides when to clean up.
development
Write a short author's briefing to hand to a code reviewer whose agent already has its own review skill, so it supplies the context that skill can't see instead of repeating how to review. Right after you finish a piece of work, it mines this session (and any kickoff implementation-notes) for what the reviewer most needs flagged — the easy-to-miss changes, the parts you're least sure about, the looks-wrong-but-intentional bits, and the blast radius — plus the exact commit range to review. Use when you've just finished work and want to hand the review off to another agent, chat, or teammate, when you want a "heads-up for the reviewer", or when packaging a change for review elsewhere. It does not perform the review and does not re-specify severity tiers or output format — that's the reviewer's own skill's job.
testing
Use when creating, rewriting, pruning, or reviewing `AGENTS.md` or `CLAUDE.md`, especially to remove repo summaries, stale rules, and other low-signal global instructions. Trigger when deciding what belongs in always-on agent files versus a task-specific skill.
development
Drive a structured tutoring workflow that turns Claude into a learning onramp accelerator — consultative diagnosis → custom syllabus → unit-by-unit guided lessons with notes/whiteboard → dynamic adjustment from an accumulating learner profile. Use when the user states a learning goal ("I want to systematically learn X", "teach me Y", "help me prep for Z exam"), uploads study materials and asks for a course plan, or signals sustained guided study (mentions tutor, syllabus, course, lessons, study plan, curriculum, 家教, 學習路徑). Skip for one-shot factual Q&A or quick code-context explanations.
tools
Produce a TL;DR of a given target. Use when the user asks for a tldr, tl;dr, or quick summary of anything.