Use when an agent works inside a person's outline on their behalf, shaping it to their needs while they work - writing or tidying notes, adding properties, making views, boards and pages, welcome notes and briefings, publishing a page, writing live figures…
float-ritual-stack/ep0ch
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 17
- GitHub stars
- 0
- GitHub forks
- 0
Install with an AI assistant
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/float-ritual-stack/ep0ch.Loading the repository README…
Skills in this repository
Showing 17 of 17 collected skills.
Use when an agent needs to see or act in an ep0ch door (the BBS-style terminal client for an outline) — reading what the person sees, opening a note in front of them, editing, commenting, moving cards or pointing at a block — or when running a door of its…
Use when someone wants an ep0ch outline or door to do something new by itself - a button that arranges tiles, a script that computes a line, a rule that draws or files matching notes, a component, a palette (power bar) or completion source, a schedule that…
Use when changing the code of the ep0ch repository (outline-core, the outliner's host, Tree/Detail and CLI, the Claude mod, the door): before planning a feature, while building it, when testing it against a scratch host or in a real terminal pane, when…
Use when someone asks what's been happening, what's moving, or for recent activity, across their ep0ch outlines, one outline, or with their other connected tools; and when they ask to follow what came up further.
Use when acting as loki, the deployer and coordinator on float-2 - deploying merges (ep0ch install --apply, the publishers, the MCP gateway), allocating PROTOCOL numbers, running the half-hourly check-in, keeping the day's build log, answering request copies…
This skill should be used when the user asks to "create a roadmap item", "add this to the roadmap", "update PIE-...", "move this to Next", "rank the Next lane", "review the roadmap", "what should we work on next", "walk me through these blocks", "step through…
Use when someone wants notes from one ep0ch outline to show up in another (on this machine or another), when setting up, checking or fixing EchoNet - areas, subscriptions, node masks, the nodelist, netmail, a toss that copied nothing, an unreachable or…
Ask which skill or flow fits your situation. A router over the skills in this repo.
Implement a piece of work based on a spec or set of tickets.
Implement the result of /to-spec and /to-tickets in code.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews…
Diagnosis loop for bugs, failing or flaky tests, and performance regressions. Use when the user says "diagnose"/"debug this", reports something broken/throwing/failing/slow, or a test or CI run fails, before proposing any fix.
Use when an agent drafts or updates the morning daily brief — the one outline note per day (type::daily-brief) that answers "what did I do yesterday, what do I need to do today" and that the ep0ch door opens on (T, --screen brief, , and . for other days).…
Manage project documentation in Pi Outliner. Use before the first documentation write in a fresh workspace, and when creating, reorganizing, splitting, referencing, transcluding, or indexing project documentation with properties or virtual branches.
This skill should be used when a prompt, focused Outliner block, or outliner tool result contains a configured work marker such as "[work-id::PIE-XXX]", "[[PIE-XXX]]", or "[issue::PIE-XXX]", or when the user asks to "resolve PIE-XXX", "turn this placeholder…