All authors

Claude Skills by chekiboy
github.com/chekiboy8 skills0 installs0 views
- JournalUse when session-end's steps reach the journal step, to write this session's journal entry and session report (`write-session-entry`), or when the user asks for a report or summary of a session (`write-session-report`). Writes them as JSON and saves them through whaat, which stores them in the identity's private folder with their tags and commits them.Votes: 0GitHub stars: 3
- Memory CurationUse when the shared memory store needs reviewing or cleaning up — the user asking to tidy, deduplicate or prune memories, a recalled memory that proved wrong or stale, two memories found saying the same thing, or an index grown so long that triggers stop being read. Not for saving a single new learning (memory). Writes the report through whaat, into this identity's private folder.Votes: 0GitHub stars: 3
- Memory MigrateUse when a whaat identity starts with little or no memory while an earlier one exists on this machine (a memory store, a personal memory dir, Claude Code's auto-memory or a subagent's memory), or when the user asks to bring, move or migrate existing memory into whaat. Copies only the groups the user picks; the sources are read, never changed.Votes: 0GitHub stars: 3
- Memory RecallUse before replying to each user message, and again right before a git push, a commit, opening an MR or a cloud call, to find the memories that apply and read them. The only way to read this identity's memory through whaat; a direct read of a memory file is declined with the command to use.Votes: 0GitHub stars: 3
- MemoryUse before saving, updating or deleting a memory — when a learning, a user correction or a project/repo fact should outlive the session, at task end when extracting learnings (`task-end`), when the user says "remember"/"jegyezd meg", when something about the user or about working together should be kept, or when you need another repo's memory. Saves through whaat into this identity's own memory. Takes the place of the built-in auto-memory.Votes: 0GitHub stars: 3
- Session EndUse when the user ends the working session — says "végeztünk", "we're done", "that's it for today" — or a decision page sends `/whaat:session-end steps=none confirmed=report-page`. Runs whaat's session-end steps in order, each through its own skill, then closes only when nothing is left open.Votes: 0GitHub stars: 3
- Skill ProposalsUse when work just replayed a procedure someone will run again — steps followed from a recipe memory, a script written for the task, a command chain that took several tries, a workaround for a gap in an existing skill — by calling this skill with args `note <skill name> — <the sign, in one sentence>`; and when session-end's steps reach the skill proposals (`session-end`) or the user asks whether something should become a skill, to propose and ask. Builds nothing without the user's yes.Votes: 0GitHub stars: 3
- Memory RecallUse before replying to each user message, and again right before a git push, a commit, opening an MR or a cloud call, to find the memories that apply and read them. The only way to read this identity's memory through whaat; a direct read of a memory file is declined with the command to use.Votes: 0GitHub stars: 3