sparshkesari/kane-hack-os
Participant skills for Kane CLI Hack Day: setup, teams, ideas, harness design, Kane run proof, help, demo, showcase and submission. Uses the event MCP server at https://www.kaneclihack.sh/mcp with a token from kanehack pair.
Use when a team wants its demo kit: the HTML deck (and optional PDF / video / cards) from its project story.
Use when a participant's environment might not be ready: Node, Git, Chrome, Kane CLI, Kane auth, the official Kane skill, this plugin, the Codex connection to the event server, or reaching the event API.
Use when a team wants launch copy (announcement, technical thread, README section, card briefs) backed by its verified evidence.
Use when a team is designing how Kane CLI will validate their project: which flows to test, which Kane commands, what evidence to keep, and how failures feed back.
Use when a participant is stuck: try first-line fixes, then open a mentor ticket and track it.
Use when a team wants to check or sharpen its project idea against the challenge criteria, or see whether similar opted-in ideas exist.
Use when a participant wants to get set up for Kane CLI Hack Day: link their registration, set profile and consent, and run the browser activation (they take the selfie themselves).
Use when a team wants to see what it has actually proven so far and turn it into honest milestones.
Use when a team wants to review and publish its public ship page at /ship/{team} after submitting.
Use when a team is ready to submit: run the preflight, fix what's missing, and finalize the official submission before the server lock.
Use when a participant wants to find a team, create one, join one with an invite code, or check their roster.
Use when a participant wants to validate a change with Kane CLI and record the result (with evidence) on the team's Proof tab.