All authors
Claude Skills by Ellebam
github.com/Ellebam46 skills0 installs0 views
- BloomBloom: explain the work with an attractive, detailed, self-contained HTML visualization. Use when the operator asks for a visual, a page or a view that makes a complex subject easier to understand.Votes: 0GitHub stars: 2
- Browser LoginLog into an authorized HTTPS service with the session's op and complete a bounded browser task. Use for browser sign-in on macOS or Linux, including launcher workers. Handle inspected username, password and op-generated OTP stages. Stop for challenges or consent that need the operator.Votes: 0GitHub stars: 2
- Close OutClose-out: verify the task's vault maintenance, record the retro and tracker report, and remove its notes. Operator-invoked, before finalize cleanup. Not a merge or task close.Votes: 0GitHub stars: 2
- Cross Tool ReviewIndependent review by the other tool, automatically at spine steps 3 and 6 or explicitly for an ad-hoc review. Verify and prune the findings.Votes: 0GitHub stars: 2
- DummyExplain it plainly, one decision, plain terms, pros and cons, a recommendation, and the missing background. Invoke when the topic is not landing and the operator wants to understand it, not just get an answer.Votes: 0GitHub stars: 2
- Execute PlanContinue a spine plan automatically after its plan review through implementation, proof, independent testing, declared shipping, diff review and its fix pass. Report to the operator.Votes: 0GitHub stars: 2
- FinalizeFinalize: ship, merge, close the task and clean up, in that order. The last spine step requires passed review and green CI or a proven CI-less bootstrap exception. Operator-typed.Votes: 0GitHub stars: 2
- GroomKeep affected repository documentation and vault knowledge correct, short and in one place. Use in plots that require it during planned work, or when asked to maintain a named scope in freeform.Votes: 0GitHub stars: 2
- ImplementImplement: execute the plan, write code and tests, run the gates. Spine step 4, after the plan check passes, builds a planned task, or runs once as a scoped fix pass on a step 6 findings list. Not planning and not proving it works.Votes: 0GitHub stars: 2
- Leak CheckLeak check: before anything leaves for a customer, make sure it shows nothing of how we work. Invoke before any commit, push, pull request text, review comment, Jira or Confluence update, or message draft goes to a project we do not fully own, again after it changes, and whenever asked whether something is clean to send. Safe to repeat.Votes: 0GitHub stars: 2
- Local QaDoes it work? Run the acceptance commands, drive the change as its user, break your own work, and run the gates only this machine can run. Spine step 5, after implement and before the diff review, proves a change actually works. Not for writing code and not for reviewing a diff.Votes: 0GitHub stars: 2
- MergeMerge the PR after green checks or a proven, operator-authorized CI-less bootstrap exception, then update local main. The last gate before code lands on the default branch. Operator-typed. Idempotent.Votes: 0GitHub stars: 2
- Plot SessionLaunch a declared plot with fixed Slopmeister-owned configuration in a worktree or a directory session with vault access, then deliver the kickoff and start Claude Code or Codex in an Orca terminal.Votes: 0GitHub stars: 2
- PrunePrune: critically reassess whatever is on the table, a review's findings, a proposal, a plan, a diff, your own draft or gaps you are about to raise, for validity, overengineering and added complexity. Invoke after a review returns, before handing findings or gaps to the operator, to check your own or another agent's output, or whenever the operator asks. Read-only and safe to repeat.Votes: 0GitHub stars: 2
- RipeCheck if we fixed or built what we meant to, and whether more work is needed. Use before asking the operator, handing off, saying done, or starting extra work, and whenever someone asks for status. Read-only.Votes: 0GitHub stars: 2
- ShipShip: commit, push, and open or update the PR. Idempotent. Standing authority comes from the plot; denied delivery needs explicit operator instruction. Not the merge.Votes: 0GitHub stars: 2
- SlotSlot: allocate an isolated parallel session of a plot, a worktree with its own port set and resources that no other live slot collides with, then hand over to the launcher. Use the dispatcher worker-command rule for fresh workers, and when a task needs the project's declared resources.Votes: 0GitHub stars: 2
- SowSow: read the ticket and the code, set the scope, draft the plan and send the operator one message. Spine steps 1 and 2, before any source change.Votes: 0GitHub stars: 2
- Test GuideWrite runnable test scenarios for an observable change, including scripts and rendered instructions. Produce commands with expected results or product interactions for the operator or autonomous tester.Votes: 0GitHub stars: 2
- Update PrsCheck dependency bot pull requests, make bounded fixes, and prepare one issue for operator-dispatched validation.Votes: 0GitHub stars: 2
- Vault OptimizeAudit and debloat this vault, read-only by default. Broken links, orphans, tag and status drift, size, and session-memory-shaped content. Safe to run often, scoped or vault-wide.Votes: 0GitHub stars: 2
- Vault TodosRoll, clean up, and add tasks in this vault's To-Do files, on explicit operator request only.Votes: 0GitHub stars: 2
- WorkstationSet up this Mac or Linux machine, diagnose a failed launch, agent CLI, Orca, login or system permission, and keep Claude Code, Codex, Orca and the installed tools current. Use it whenever one of those fails, when the operator says onboard me or set up this machine, and after an update.Votes: 0GitHub stars: 2
- Example CheckRead the example application instructions and report the smallest useful check.Votes: 0GitHub stars: 2
- BloomBloom: explain the work with an attractive, detailed, self-contained HTML visualization. Use when the operator asks for a visual, a page or a view that makes a complex subject easier to understand.Votes: 0GitHub stars: 2
- Close OutClose-out: verify the task's vault maintenance, record the retro and tracker report, and remove its notes. Operator-invoked, before finalize cleanup. Not a merge or task close.Votes: 0GitHub stars: 2
- DummyExplain it plainly, one decision, plain terms, pros and cons, a recommendation, and the missing background. Invoke when the topic is not landing and the operator wants to understand it, not just get an answer.Votes: 0GitHub stars: 2
- Execute PlanContinue a spine plan automatically after its plan review through implementation, proof, independent testing, declared shipping, diff review and its fix pass. Report to the operator.Votes: 0GitHub stars: 2
- FinalizeFinalize: ship, merge, close the task and clean up, in that order. The last spine step requires passed review and green CI or a proven CI-less bootstrap exception. Operator-typed.Votes: 0GitHub stars: 2
- ImplementImplement: execute the plan, write code and tests, run the gates. Spine step 4, after the plan check passes, builds a planned task, or runs once as a scoped fix pass on a step 6 findings list. Not planning and not proving it works.Votes: 0GitHub stars: 2
- Leak CheckLeak check: before anything leaves for a customer, make sure it shows nothing of how we work. Invoke before any commit, push, pull request text, review comment, Jira or Confluence update, or message draft goes to a project we do not fully own, again after it changes, and whenever asked whether something is clean to send. Safe to repeat.Votes: 0GitHub stars: 2
- Local QaDoes it work? Run the acceptance commands, drive the change as its user, break your own work, and run the gates only this machine can run. Spine step 5, after implement and before the diff review, proves a change actually works. Not for writing code and not for reviewing a diff.Votes: 0GitHub stars: 2
- MergeMerge the PR after green checks or a proven, operator-authorized CI-less bootstrap exception, then update local main. The last gate before code lands on the default branch. Operator-typed. Idempotent.Votes: 0GitHub stars: 2
- PrunePrune: critically reassess whatever is on the table, a review's findings, a proposal, a plan, a diff, your own draft or gaps you are about to raise, for validity, overengineering and added complexity. Invoke after a review returns, before handing findings or gaps to the operator, to check your own or another agent's output, or whenever the operator asks. Read-only and safe to repeat.Votes: 0GitHub stars: 2
- RipeCheck if we fixed or built what we meant to, and whether more work is needed. Use before asking the operator, handing off, saying done, or starting extra work, and whenever someone asks for status. Read-only.Votes: 0GitHub stars: 2
- ShipShip: commit, push, and open or update the PR. Idempotent. Standing authority comes from the plot; denied delivery needs explicit operator instruction. Not the merge.Votes: 0GitHub stars: 2
- SlotSlot: allocate an isolated parallel session of a plot, a worktree with its own port set and resources that no other live slot collides with, then hand over to the launcher. Use the dispatcher worker-command rule for fresh workers, and when a task needs the project's declared resources.Votes: 0GitHub stars: 2
- SowSow: read the ticket and the code, set the scope, draft the plan and send the operator one message. Spine steps 1 and 2, before any source change.Votes: 0GitHub stars: 2
- Test GuideWrite runnable test scenarios for an observable change, including scripts and rendered instructions. Produce commands with expected results or product interactions for the operator or autonomous tester.Votes: 0GitHub stars: 2
- Vault TodosRoll, clean up, and add tasks in this vault's To-Do files, on explicit operator request only.Votes: 0GitHub stars: 2
- WorkstationSet up this Mac or Linux machine, diagnose a failed launch, agent CLI, Orca, login or system permission, and keep Claude Code, Codex, Orca and the installed tools current. Use it whenever one of those fails, when the operator says onboard me or set up this machine, and after an update.Votes: 0GitHub stars: 2
- Execute PlanContinue a spine plan automatically after its plan review through implementation, proof, independent testing, declared shipping, diff review and its fix pass. Report to the operator.Votes: 0GitHub stars: 2
- Vault TodosRoll, clean up, and add tasks in this vault's To-Do files, on explicit operator request only.Votes: 0GitHub stars: 2
- BlockyFixture skill with a declared per-tool difference.Votes: 0GitHub stars: 2
- GatedFixture skill that is operator-only.Votes: 0GitHub stars: 2
- PlainFixture skill with no declared difference.Votes: 0GitHub stars: 2