All authors
Claude Skills by thrum-team
github.com/thrum-team160 skills0 installs0 views
- Implementer Orchestrating ExecutionYou implement by **orchestrating sub-agents**, not by doing research, edits, and verification yourself. Your own context is for judgment — synthesizing research, targeting edits, judging verification against the plan. The legwork goes to cheaper sub-agents. This skill is the procedure; invoke it at the start of executing any scoped task.Votes: 0GitHub stars: 2
- Implementer Receiving DispatchBefore reading further: lift this dispatch into a bundle (`thrum queue add --from-message <msg-id>`, the exact id of the dispatch you're acting on), then `thrum queue start <bundle-id>`; drop/close any finished bundles. Full lifecycle: `using-the-queue`. Without a Pro licence (`not entitled` / `requires a license`), skip this write and track it in the message thread instead.Votes: 0GitHub stars: 2
- Implementer Receiving Review FeedbackThis skill **complements** `superpowers:receiving-code-review` — it does not restate the technical-rigor and no-performative-agreement content from that skill. Layer the rules below on top of those universals.Votes: 0GitHub stars: 2
- Implementer Status And Handoff**Why:** The coordinator uses your status token to decide whether to proceed, hold for review, or unblock. Vague reports like "I finished the work" or "mostly done" force the coordinator to re-read the full implementation to judge state, which adds latency to every dispatch they manage. The token is a 100ms decision instead of a five-minute re-read.Votes: 0GitHub stars: 2
- Implementer Tdd And QualityThis skill **complements** `superpowers:test-driven-development` — it does not restate the red-green-refactor discipline, the iron law on watching tests fail, or any other content from that skill. Layer this content on top of those universals: the rules below capture project-specific Go conventions and quality-gate practice.Votes: 0GitHub stars: 2
- Memory Maintenance> **Before writing or editing any memory or state entry, apply "A memory states > the current rule" in `thrum-memory`:** a memory states only the CURRENT rule > (exceptions allowed), never a timeline of rulings, corrections or reversals, > and every touch re-examines the whole memory.Votes: 0GitHub stars: 2
- Memory Search AdvancedLoad this sub-skill from `thrum-memory` (umbrella) for predicate needs beyond tag + kind + recency filtering.Votes: 0GitHub stars: 2
- Memory To Thrum PointerAn index line that restates a rule goes wrong when it is shortened, because shortening drops the scope that makes the rule true. An index line written as a TRIGGER cannot contradict the rule, because it does not state the rule. It only tells you when to read the full text.Votes: 0GitHub stars: 2
- OrchestrateThis is the full execution playbook. Follow each phase in order. Do not skip phases or steps.Votes: 0GitHub stars: 2
- Persistent Watcher ArchetypeRun `resources/start-watcher.sh`. It is the one supported way to start one: do not hand-build the monitor, write `watch_params.json` yourself or guess its fields (the schema is `resources/watch-params-schema.md`).Votes: 0GitHub stars: 2
- Prime AgentThis skill is the wake-time variant of `thrum prime` for scheduled agents. Full `thrum prime` is too heavy when the agent is going to run for a few minutes and then exit — but the two pieces of state that matter MUST run literally, not as a discipline.Votes: 0GitHub stars: 2
- Project Gate Setup`.thrum/gate-config.json` — the single authoritative location. The gate role reads it at gate time. Its preamble names no project command; every command comes from this file. A field left out means the gate falls back to asking, never to guessing.Votes: 0GitHub stars: 2
- Project Hotpath Gate`.thrum/hotpath-gate.json` — the single authoritative location. `coordinator-hotpath-merge-gate` reads from this path only.Votes: 0GitHub stars: 2
- Project Philosophy`.thrum/philosophy.md` — the single authoritative location. `project-setup` and every implementation-agent prompt read from this path only. Non-standard paths are handled by the fallback migration (documented below), not by moving the canonical target.Votes: 0GitHub stars: 2
- Project Rules ProtocolProject-local rules of kind `agent_rule` at `--scope role` were loaded at session start by your preamble (see the memory rules in your role preamble). If a project-local rule conflicts with a universal rule above, the project-local rule wins; surface the conflict in your reply so the user can decide whether to graduate or remove the override.Votes: 0GitHub stars: 2
- Project SetupConvert a plan file into beads epics and tasks with TDD-quality descriptions, filled implementation prompts, and ready-to-use worktrees.Votes: 0GitHub stars: 2
- Researcher Answering QueriesLift this query into a bundle (`thrum queue add --from-message <msg-id>`), then `thrum queue start <bundle-id>`; drop/close finished bundles. Full lifecycle: `using-the-queue`. Without a Pro licence (`not entitled` / `requires a license`), skip this write and track it in the message thread instead.Votes: 0GitHub stars: 2
- Researcher InvestigatingLift this query into a bundle (`thrum queue add --from-message <msg-id>`), then `thrum queue start <bundle-id>`; drop/close finished bundles. Full lifecycle: `using-the-queue`. Without a Pro licence (`not entitled` / `requires a license`), skip this write and track it in the message thread instead.Votes: 0GitHub stars: 2
- Routing Messages Across DaemonsRouting and pairing are different things. Pairing connects two daemons directly. Routing sends a message through a directly paired peer to an agent that peer knows.Votes: 0GitHub stars: 2
- Setting Up Account UsageAccount usage is off by default. When on, the daemon runs the pinned `quota-axi` every 15 minutes (and once at start) and records used/remaining and reset time per account. It never installs, updates or fetches `quota-axi`. Some steps need the USER at their own terminal: say so before you start.Votes: 0GitHub stars: 2
- Snapshot ProtocolThis is the canonical source-of-truth for snapshot composition discipline. Invoke this skill to compose a snapshot, then take the variant-specific terminal action.Votes: 0GitHub stars: 2
- Stamp ProtocolThis is the canonical source-of-truth for the Authored-against stamp: its format, derivation commands, and the never-type rule. Consuming files point here instead of restating the recipe. Do not run this as a command; it has no terminal action — other skills and commands load it by name. (To find what currently points here: `grep -rn "thrum:stamp-protocol" claude-plugin/commands/ claude-plugin/skills/` — a hand-listed consumer roster in this file would rot the moment a new emitter or reader is aVotes: 0GitHub stars: 2
- State MigrationThis is a conditional, one-time onboarding — modeled on the philosophy- document onboarding pattern. It does nothing if either half of its trigger condition is false.Votes: 0GitHub stars: 2
- StewardYou are a **Steward**: a persistent watcher whose roster is the agents that ask the project owner things, usually the coordinators of several projects, possibly on other machines, and any brainstormers. Your job is to keep the owner from switching between panes. You collect each question, send it to the owner's inbox, and carry the answer back. **You never decide content.** You route.Votes: 0GitHub stars: 2
- Thrum CompactUse this skill when the user explicitly wants the `compact` Thrum workflow. Prefer the umbrella `thrum` skill when the request spans multiple commands or needs broader coordination judgment.Votes: 0GitHub stars: 2
- Thrum InboxCheck message inboxVotes: 0GitHub stars: 2
- Thrum Load ContextUse this skill when the user explicitly wants the `load-context` Thrum workflow. Prefer the umbrella `thrum` skill when the request spans multiple commands or needs broader coordination judgment. Run `thrum prime` to restore your session. The briefing includes your restart snapshot, personal state, and committed-work queue. ```bash thrum prime ``` If the output was truncated or you need to re-read it, run `thrum prime --to-file` (if --to-file is an unknown flag, run plain `thrum prime` once a...Votes: 0GitHub stars: 2
- Thrum Memory> **Before writing or editing any memory or state entry, apply "A memory states > the current rule" below:** a memory states only the CURRENT rule (exceptions > allowed), never a timeline of rulings, corrections or reversals, and every > touch re-examines the whole memory.Votes: 0GitHub stars: 2
- Thrum OverviewCombines identity, team, inbox, and sync statusVotes: 0GitHub stars: 2
- Thrum PrimeLoad AI-optimized session contextVotes: 0GitHub stars: 2
- Thrum QuickstartRegister agent and start sessionVotes: 0GitHub stars: 2
- Thrum ReplyReply to a messageVotes: 0GitHub stars: 2
- Thrum RestartUse this skill when the user explicitly wants the `restart` Thrum workflow. Prefer the umbrella `thrum` skill when the request spans multiple commands or needs broader coordination judgment.Votes: 0GitHub stars: 2
- Thrum SendSend a message to an agentVotes: 0GitHub stars: 2
- Thrum SleepUse this skill when the user explicitly wants the `sleep` Thrum workflow. Prefer the umbrella `thrum` skill when the request spans multiple commands or needs broader coordination judgment.Votes: 0GitHub stars: 2
- Thrum TeamShow active team membersVotes: 0GitHub stars: 2
- Thrum Update ProjectUpdate project state with session summary and mechanical stateVotes: 0GitHub stars: 2
- Thrum WaitBlock until a message arrivesVotes: 0GitHub stars: 2
- ThrumRun `thrum prime` for full session context (auto-injected by the SessionStart hook; also fires on post-compact resume). PreCompact is not registered — use `$thrum:thrum-compact` to save a snapshot before deliberately compacting.Votes: 0GitHub stars: 2
- Trace Spec To Plan**Announce at start:** "I'm using trace-spec-to-plan to walk every spec requirement into the plan."Votes: 0GitHub stars: 2
- Transcript Search`thrum transcript` searches and reads the agent session transcripts on THIS box only. It talks to the local daemon; there is no cross-peer search. It is a Pro feature.Votes: 0GitHub stars: 2
- Update QueueReconcile YOUR OWN `thrum queue` so its status matches reality: drop finished rot, verify each live bundle against git + beads + merge state, add committed work that is missing. Scoped to your queue only — cross-agent reconciles are a larger pass (see the final section). Run it at session start, at a lull, or whenever the queue can no longer be trusted at a glance.Votes: 0GitHub stars: 2
- Using MonitorsA monitor runs a command, keeps the output lines that match a regex, and delivers them as Thrum messages to a target: a continuous monitor sends each kept line, a scheduled monitor sends all the lines of a run in one message. With `--schedule` it runs the command once per cron tick; without it the command runs continuously and restarts with backoff when it exits. Monitors persist across daemon restarts and run only on the daemon that owns them.Votes: 0GitHub stars: 2
- Using The DashboardThe Dashboard is an agent's way to put an **interactive board** in front of the human user: typed widgets (status rows, cards, lists), optional HTML regions, and **action-picks the user answers by clicking an option and optionally typing nuance**. It replaces the "agent runs a TUI" pattern — it is out-of-band from the messaging channel, so it never blocks messages and answers never scroll away.Votes: 0GitHub stars: 2
- Using The Queue`thrum queue` is a per-agent, local-only, daemon-resident list of the work an agent has committed to. One queue per `agent_id`; you EDIT your own, anyone may READ any queue. It is not beads and not a message inbox - beads is the shared backlog of what COULD be done; the queue is the private, short-lived list of what an agent IS doing right now, and it is gone when the agent is deleted.Votes: 0GitHub stars: 2
- Using Thrum State> **Before writing or editing any memory or state entry, apply "A memory states > the current rule" in the `thrum-memory` skill:** a memory states only the > CURRENT rule (exceptions allowed), never a timeline of rulings, corrections or > reversals, and every touch re-examines the whole memory.Votes: 0GitHub stars: 2
- Using Tmux Ssh`tmux-ssh` drives one persistent SSH login per host in a local tmux pane. Use it for every command on another machine or VM, short or long, including remote tests, builds, and log reads. Use `--read` and `--status` to observe; never use plain SSH polling or Monitor loops.Votes: 0GitHub stars: 2
- Verify Against PlanTwo inputs are required and one is optional. Missing a required input is a pre-flight bail.Votes: 0GitHub stars: 2
- Verify Against SourceThe prose counterpart to `verify-against-plan`. Where `verify-against-plan` asks "does the CODE match the plan?", this asks "does this PROSE ARTIFACT honor its SOURCE?" — e.g. does a plan honor every locked brainstorm decision, does an implementation prompt faithfully translate the plan + bead descriptions.Votes: 0GitHub stars: 2
- Watcher ArchetypeA watcher is a read-only, scheduled agent that detects issues deterministically, files/annotates them as beads, and exits. The substrate provides the engine and the `thrum watcher` CLI; a domain skill-pack supplies the scanner. Your job each wake is to run ONE cycle and exit — never to fix, never to write code.Votes: 0GitHub stars: 2