How do I install the Hack Dance Hack Hack Tickets skill?

Run npx skillmds@latest add tomevault-io/hack-dance-hack-hack-tickets in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Hack Dance Hack Hack Tickets skill do?

hack tickets It is listed under Coding & Dev Tools on SkillMD.

Is Hack Dance Hack Hack Tickets safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Hack Dance Hack Hack Tickets?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Hack Dance Hack Hack Tickets free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Hack Dance Hack Hack Tickets?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Hack Dance Hack Hack Tickets by tomevault-io

Name: Hack Dance Hack Hack Tickets
Author: tomevault-io

File contents

hack tickets

This repo uses the hack tickets extension (dance.hack.tickets). Prefer hack tickets ... (alias) or hack x tickets ... over manual edits in .hack/tickets/.

Enable

Enable globally:

hack config set --global 'controlPlane.extensions["dance.hack.tickets"].enabled' true
hack setup sync --all-scopes (refresh generated agent instructions + skills + MCP config)

Or per-project by adding .hack/hack.config.json:

{
  "controlPlane": {
    "extensions": {
      "dance.hack.tickets": { "enabled": true }
    }
  }
}

Commands

Create: hack x tickets create --title "..." [--body "..."] [--body-file <path>] [--body-stdin] [--depends-on "..."] [--blocks "..."] [--actor "..."] [--json]
List: hack x tickets list [--json]
Tui: hack x tickets tui
Show: hack x tickets show <ticket-id> [--json]
Update: hack x tickets update <ticket-id> [--title "..."] [--body "..."] [--depends-on "..."] [--blocks "..."] [--clear-depends-on] [--clear-blocks] [--json]
Status: hack x tickets status <ticket-id> <open|in_progress|blocked|done> [--json]
Sync: hack x tickets sync [--json]

Recommended body template (Markdown):

## Context
## Goals
## Notes
## Links

Tip: use --body-stdin for multi-line markdown.

Data model

Tickets are derived from an append-only event log (JSONL).
Local state lives in .hack/tickets/ (gitignored on the main branch).
Sync writes commits to a dedicated ref (refs/hack/tickets hidden by default) and pushes to your remote.
Set controlPlane.tickets.git.refMode to heads to use a normal branch ref (and protect it if desired).

Tips

Keep ticket titles short; put detail in --body.
Use --json for agent workflows and piping.
Run hack x tickets sync before opening PRs if you want tickets to travel with the repo.
Update status continuously (open -> in_progress -> blocked/done) so handoffs are explicit.
Use --depends-on / --blocks links to model execution order for parallel agent work.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: hack-dance-hack-hack-ticketsdescription: hack tickets---# hack ticketsThis repo uses the hack tickets extension (`dance.hack.tickets`).Prefer `hack tickets ...` (alias) or `hack x tickets ...` over manual edits in `.hack/tickets/`.## EnableEnable globally:- `hack config set --global 'controlPlane.extensions["dance.hack.tickets"].enabled' true`- `hack setup sync --all-scopes` (refresh generated agent instructions + skills + MCP config)Or per-project by adding `.hack/hack.config.json`:```json{ "controlPlane": { "extensions": { "dance.hack.tickets": { "enabled": true } } }}```## Commands- Create: `hack x tickets create --title "..." [--body "..."] [--body-file <path>] [--body-stdin] [--depends-on "..."] [--blocks "..."] [--actor "..."] [--json]`- List: `hack x tickets list [--json]`- Tui: `hack x tickets tui`- Show: `hack x tickets show <ticket-id> [--json]`- Update: `hack x tickets update <ticket-id> [--title "..."] [--body "..."] [--depends-on "..."] [--blocks "..."] [--clear-depends-on] [--clear-blocks] [--json]`- Status: `hack x tickets status <ticket-id> <open|in_progress|blocked|done> [--json]`- Sync: `hack x tickets sync [--json]`Recommended body template (Markdown):```md## Context## Goals## Notes## Links```Tip: use `--body-stdin` for multi-line markdown.## Data model- Tickets are derived from an append-only event log (JSONL).- Local state lives in `.hack/tickets/` (gitignored on the main branch).- Sync writes commits to a dedicated ref (`refs/hack/tickets` hidden by default) and pushes to your remote.- Set `controlPlane.tickets.git.refMode` to `heads` to use a normal branch ref (and protect it if desired).## Tips- Keep ticket titles short; put detail in `--body`.- Use `--json` for agent workflows and piping.- Run `hack x tickets sync` before opening PRs if you want tickets to travel with the repo.- Update status continuously (`open` -> `in_progress` -> `blocked`/`done`) so handoffs are explicit.- Use `--depends-on` / `--blocks` links to model execution order for parallel agent work.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/hack-dance) — claim your Tome and manage your conversions.

Frequently asked questions

Hack Dance Hack Hack Tickets