All authors
Claude Skills by vraj-ai
github.com/vraj-ai19 skills0 installs62 views
- Council AdversaryTear down a converged item or whole deliverable as a read-only different-model judge, returning falsifiable findings and a blocking verdict. Use for optional hardened T0 review, optional T2 whole-deliverable review, and the mandatory final T3 code-level gate.Votes: 0GitHub stars: 4
- CouncilRun independent multi-model research, evidence-based debate, voting, and scoped T0/T1 reviews without rubber-stamping. Use when goals encounters a genuinely contested research item, Phase B needs backlog sanity checks, an item needs independent T0 reviewers, or a milestone needs one rotating integration reviewer.Votes: 0GitHub stars: 4
- GoalsDrive a plan document to verified completion through a resumable single-writer backlog, named Worker Role research and review, worktree-isolated parallel builds, milestone gates, and a final adversarial teardown. Use when the user invokes /goal, asks to execute an architecture plan autonomously, resumes a goal, or needs a large issue set delivered milestone by milestone.Votes: 0GitHub stars: 4
- ShipThe implementation skill — a spec, ticket, or raw task in; verified, pushed delivery out. Resumable backlog, worktree-parallel builds, gate-first TDD at real seams, lazy-senior-dev ladder, two-axis review, milestone gate, adversarial teardown. Merges implementation-tdd, ponytail's ladder and rubric, poteto-mode's craft rules, and code-review's axes. Use for /ship, "implement", "build", "fix", "ship this", "do #N", or any request with acceptance criteria. Never interviews: a task message alone...Votes: 0GitHub stars: 4
- Ai Subscription Unit EconomicsPricing, limits, and margin gates for a product whose cost of goods is model inference — compute cost per action, cost per active user, and the breakeven limit before choosing a price, then encode the resulting caps as testable invariants. Use when pricing an AI feature or subscription tier, setting rate/usage limits, evaluating whether a plan loses money on heavy users, or estimating the inference cost of a proposed feature.Votes: 0GitHub stars: 4
- GrillUser-invoked interview that stress-tests a plan and writes glossary, architecture, and ADRs into CONTEXT/. Use when the user runs /grill. Part of the grill → /issues → /ship → /snapshot chain.Votes: 0GitHub stars: 4
- Herdr OrchestratorInteractive Herdr setup and orchestration for a Grok pane coordinating Codex and three non-OpenCode Council agents.Votes: 0GitHub stars: 4
- IssuesUser-invoked. Sets up a project's tracker and CONTEXT/ once, then turns a grill into a spec and tracer-bullet tickets. Use when the user runs /issues. Part of the /grill → issues → /ship → /snapshot chain.Votes: 0GitHub stars: 4
- PonytailForces the laziest solution that actually works; use on coding tasks or when the user says ponytail, be lazy, simplest solution, YAGNI, do less, or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do not use for non-coding requests.Votes: 0GitHub stars: 4
- Pr ReviewGitHub Actions PR review bot with Greptile parity — confidence 0-5, risk gates, checks annotations, and fix loop. Install via setup-vskills.Votes: 0GitHub stars: 4
- Push HandoffCommit and push a verified handoff plus its artifacts, only under explicit authority, and prove the push happened by reading the remote SHA back. Use as the final delivery step after artifacts are ready, when the user asks to push work, or when a handoff needs to reach the remote. Refuses to claim success without remote proof and never force-pushes or commits secrets.Votes: 0GitHub stars: 4
- Setup ObsidianTurn a repo's docs folder into a retrieval graph — router, generated indexes, state file — and open it as an Obsidian vault.Votes: 0GitHub stars: 4
- Setup VskillsSets up this skills repo on a new machine — installs the skills with the vskills CLI, configures pstack model routing for any harness, ensures a verification skill, then regenerates the local-only context docs (CONTEXT.md, docs/) that are deliberately not published in the public repo.Votes: 0GitHub stars: 4
- SnapshotUser-invoked session close. Syncs CONTEXT/ and the issue tracker, writes a handoff, then commits and pushes under /snapshot authority. Use when the user runs /snapshot. Part of the /grill → /issues → /ship → snapshot chain.Votes: 0GitHub stars: 4
- AuditAudit a whole codebase rather than a single diff — establish the boundary and baseline, sweep layer by layer (entry points, domain, data, integrations, auth, tests, ops), check every stated invariant for a real enforcement point, a failing-on-violation test, and a production signal, rank findings by blast radius, and emit each as a ticket with a Verification-command. Use when asked to audit an app or codebase, assess a project's health, review before a launch, verify that a security/performan...Votes: 0GitHub stars: 4
- Delivery ConstraintsDeliver a ticket whose delivery path is decided by something other than the code — a token/spend cap, a live data migration, restricted git authority, an unwritable tracker, or a pipeline state that is lying about progress. Use when budget is capped, when a change touches production data or costs money to run, when push/PR authority is restricted, when tracker writes are unavailable and work must hand off through a file, or when a ticket has been retried with no new evidence and the tracker a...Votes: 0GitHub stars: 4
- Implementation TddStrict one-ticket TDD for implementation work — lock the Verification-command before editing, drive red-green at the highest meaningful seam production traffic actually uses, and prove the provider failure modes (duplicate and out-of-order delivery, replay, partial failure, forged payloads, wrong-tenant access) rather than assuming them. Use when implementing a Coding ticket, and whenever the change touches an external provider, a queue, a signed webhook, a billing or provisioning lifecycle, ...Votes: 0GitHub stars: 4
- Subagent DelegationFan work out to subagents safely — draw provably disjoint lanes, write the full lane brief, order dependent tickets into waves, and keep the parent as the sole gatekeeper that re-runs every gate and performs every commit and tracker write. Use when parallel or batch work is explicitly authorized, when an authorized ticket range has a dependency graph, when workers share one git checkout, or when any agent or human may be writing the same tree concurrently.Votes: 0GitHub stars: 4
- Test TpsUser-invoked benchmark for selected Pi provider/model. Measures TTFT, decode TPS, average TPS, latency, token usage, and aggregate percentiles. Use when user invokes test-tps.Votes: 0GitHub stars: 4