How do I install the Hack Tickets skill?

Run npx skillmds@latest add majiayu000/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.

Is Hack Tickets safe to use?

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

Which AI agents work with 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 Tickets free to use?

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

Who published Hack Tickets?

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

Hack Tickets by majiayu000 — Agent Skill

Name: Hack Tickets
Rating: 4.2 (5 reviews)
Author: majiayu000

Hack Tickets

Use the hack tickets extension (git-backed JSONL event log) to create/list/show/sync lightweight tickets. Trigger when asked to track work items, decisions, or bugs inside a repo without external issue trackers. Prefer `hack x tickets ...` commands; store lives on hidden ref `refs/hack/tickets` by default.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

hack tickets

This repo uses the hack tickets extension (dance.hack.tickets).

Enable

Enable globally:

hack config set --global 'controlPlane.extensions["dance.hack.tickets"].enabled' true

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.

---name: hack-ticketsdescription: Use the hack tickets extension (git-backed JSONL event log) to create/list/show/sync lightweight tickets. Trigger when asked to track work items, decisions, or bugs inside a repo without external issue trackers. Prefer `hack x tickets ...` commands; store lives on hidden ref `refs/hack/tickets` by default.--- # hack tickets This repo uses the hack tickets extension (`dance.hack.tickets`). ## Enable Enable globally: - `hack config set --global 'controlPlane.extensions["dance.hack.tickets"].enabled' true` 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.

Frequently asked questions