Skip to content
Back to skills

Superharness

ASecurity

Multi-agent task coordination via the shux CLI. Use when the user asks about task status, wants to see the task contract, wants to delegate/dispatch work to an agent, wants to check tool health, or wants to close a completed task. Routes to /shux-contract (show tasks + next-task suggestion), /shux-status (health dashboard), /shux-delegate (create + enqueue a task), /shux-doctor (prerequisite check), /shux-close (close a report_ready/review_passed task), and /shux-help (full CLI command refere...

  • 5 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 19, 2026
ai-agents

Works with

  • cli

Security analysis

A100/100

Scanned September 19, 2026

npx -y skills add artificemachine/superharness --skill superharness --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Superharness?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Superharness
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/artificemachine-superharness/badge)](https://www.skillsdirectory.com/skills/artificemachine-superharness)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: superharness
description: >
  Multi-agent task coordination via the shux CLI. Use when the user asks about task
  status, wants to see the task contract, wants to delegate/dispatch work to an agent,
  wants to check tool health, or wants to close a completed task. Routes to
  /shux-contract (show tasks + next-task suggestion), /shux-status (health dashboard),
  /shux-delegate (create + enqueue a task), /shux-doctor (prerequisite check),
  /shux-close (close a report_ready/review_passed task), and /shux-help (full CLI
  command reference). For anything else, /shux <args> runs the CLI directly.
---

## When to use which command

| User intent | Command |
|---|---|
| "what tasks are open", "show contract" | `/shux-contract` |
| "is the watcher running", "health check", "any issues" | `/shux-status` |
| "dispatch this task", "delegate <id>" | `/shux-delegate <id>` |
| "check prerequisites", "is superharness set up right" | `/shux-doctor` |
| "close task <id>", "mark done" | `/shux-close <id>` (only if status is report_ready or review_passed) |
| "what shux commands exist", "help", "usage" | `/shux-help` |
| anything else shux-related | `/shux <subcommand> [args]` |

## Rules

- After `/shux-contract`, ask which task to enqueue — never enqueue without being asked.
- Before `/shux-close`, confirm the task's status is `report_ready` or `review_passed`.
- When a problem surfaces (task stuck, discussion stalled), state what you observe, check whether auto-mode (watcher/reconciler) would resolve it, and only then propose a `/shux-*` action.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…