Skip to main content
GitHub repository

senate

senate contains 6 collected skills from SebastianElvis, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
6
Stars
1
updated
2026-05-03
Forks
0
Occupation coverage
3 occupation categories · 100% classified
repository explorer

Skills in this repository

evals
data-scientists-152051

Evaluation harness for the senate skill. Runs fixture debates end-to-end, applies deterministic graders against the run-dir contract, and uses Claude CLI as an LLM judge for quality dimensions (verdict, agenda, notes, transcript). Use when the user wants to measure which models are reliable in which formats, benchmark a new CLI playbook, or verify a format file after changes.

2026-05-03
moderate-debate
software-developers

Drives a multi-agent debate from a planned agenda — builds prompts, dispatches each CLI turn into a standalone subagent, commits the shared transcript and context, handles budget/failure/checkpoint policy, and adapts the agenda mid-run when the situation diverges from the plan. Use this skill when senate has an `agenda.md` ready and needs the actual turns run, or when resuming a paused or stalled debate run.

2026-05-03
debate-agenda
project-management-specialists

Plans the agenda for a multi-agent debate — picks the format, picks the roster, sequences stages, resolves sub-debate composition, and asks the user for clarification when the request is ambiguous. Use this skill when the senate orchestrator needs an agenda before debating, when the user asks "which format should I use for X?" or "how should we structure this debate?", or when the user describes a multi-step decision (e.g., "draft an RFC, have it reviewed, then vote") that needs stages laid out.

2026-05-03
meeting-note
project-management-specialists

Consolidates a finished debate run into a single user-facing notes.md — reads the agenda, transcript, shared context, and per-stage verdicts (multi-stage), and writes the canonical user-facing summary that merges what was decided (verdict) with what happened (meeting notes). Use this skill when moderate-debate has finished a run and the user needs a clean summary of what happened, what was decided, and what to do next, or when the user asks for "the notes", "the summary", or "the verdict" of a past debate run.

2026-05-03
senate
software-developers

Top-level orchestrator for multi-agent debates between coding CLIs (codex, gemini, cursor, kimi, claude). Routes a request through three sub-skills — debate-agenda (plan), moderate-debate (run), meeting-note (consolidate) — and returns a single user-facing notes.md summary. Use this skill when the user wants a debate, second opinion, adversarial review, or cross-model agreement on a non-trivial question — even if they don't say "debate" — and especially when they say "debate", "parliament", "court", "peer-review", "red-team", "committee", "senate", "have X and Y argue", or "ask multiple models".

2026-05-03
invoke-agent
software-developers

Playbook for invoking non-interactive coding-agent CLIs (codex, gemini, cursor, kimi, claude) as subprocesses. Use this skill inside a moderate-debate per-turn subagent, or when any skill needs to shell out to another AI CLI with a prompt and capture the reply — covers install checks, exact non-interactive invocation, input/output conventions, budget flags, and known per-CLI quirks.

2026-05-02