hack-kit

Plugin hack-kit from marketplace borah-skills in abhinavborah/borah-skills. Commands read from the repo's manifest — 12 days ago.

Skills (11)

• contract-check

  Turn the organizer's rules (problem statement, AGENTS.md, README, judging criteria, submission rules) into a numbered contract of MUST and SHOULD items, flag contradictions and typos between sources, and recheck it before submission. Use at the start of a hackathon or contest and again before submit

• demo-pitch

  Prepare a hackathon demo, pitch and submission. Picks the one flow to show, cuts scope to it, writes a timed demo script with a fallback, drafts submission text, and sets a rehearsal checklist. Use in the last third of a hackathon, or when asked for a pitch, demo script or submission. Includes a UI

• eval-harness

  Set up honest evaluation before tuning anything. Makes a deterministic dev and holdout split of labeled data, adds a scorer, and guards production code from reading gold labels or sample answers. Use when a project has labeled examples and a score to report, before the first tuning round. Not for un

• okf-docs

  Write, update and validate the docs/ folder as an OKF v0.2 bundle (concept files with frontmatter, index.md, log.md). Use when adding or editing any file under docs/, syncing indexes and logs, or checking bundle conformance. Not for session handoffs (use session-handoff).

• orchestrate

  Split work into independent packets, get approval, then dispatch in-process subagents with disjoint file ownership and collect their reports from files. Two modes, worktree per packet or one shared tree. Use when a task has two or more parts that can run in parallel and touch different files. Not fo

• project-log

  Log decisions, findings, changes and rejected approaches as shared project history in docs/journal/. Use when the user says to record, log, note or write down a decision or the reason for something, and right after a decision is made, research or a spike finishes, direction changes, or an approach i

• research

  Dated, sourced research using the best available tools (firecrawl, exa, alphaxiv, last30days, context7, web search). Tests which tools work first, tells the user, falls back when one fails, and saves a note to docs/research/. Use for library or stack choices, best-practice checks, prior art and anyt

• scaffold

  Opt-in setup of a hackathon project. Creates the git repo, a docs/ OKF bundle, optional CLAUDE.md or AGENTS.md, a researched stack, an optional GitHub repo, and optional ghost mode. Runs only when the user types /hack-kit:scaffold, and asks before creating anything.

• session-handoff

  Write a timestamped handoff file in docs/handoffs/ (session) or docs/subagent-handoffs/ (one subagent) so the next agent continues without this conversation. Use when the user asks for a handoff, when context is nearly full, or when orchestrate dispatches a subagent. Not for chat summaries or compac

• spec-interview

  Turn a vague idea into a testable spec by interviewing the user, or stress-test an existing plan before building. Use at the start of a project or feature, when requirements are unclear,. Writes docs/specs/<name>.md. Not for looking up facts (use research) or trying a design in code.

• submit-pack

  Package a hackathon or contest submission. Shows time left to the deadline, runs a clean-clone check, builds the code archive with excludes, collects agent transcripts from every project folder of the repo and its worktrees, scans the bundle for secrets and junk, and lists the exact artifacts to upl

Subagents (3)

• packet-worker-shared

  Does one orchestrate packet in the shared working tree, stays inside the files it owns, never runs git write commands, and reports to a file. Use only when dispatched by the orchestrate skill in shared mode with a brief.

• packet-worker

  Does one orchestrate packet in its own git worktree, stays inside the files it owns, commits, and reports to a file. Use only when dispatched by the orchestrate skill in worktree mode with a brief.

• reviewer

  Independent, adversarial, read-only reviewer. Finds defects, rule violations and gaps in a diff, a branch, a plan or a set of files, and writes severity-tagged findings to a file. Use from orchestrate after a wave, or whenever a second opinion unanchored on the author's reasoning is needed.

Similar plugins