Hk Local Run Spec

What it does

When your agent uses it

• The user wants to run a spec
• Do a smoke test
• : run this spec
• /hk-local-run-spec

Example prompts

• “run this spec”
• “test this spec”
• “odin plan”
• “/hk-local-run-spec”

Requirements

• Python 3
• Pre-approved tools (allowed-tools): Bash, Read

Workflow steps

5 steps, taken from the step headings in SKILL.md.

1. 1Detect environment
2. 2Resolve paths
3. 3Generate commands
4. 4Output
5. 5Post-run diagnostic hint

What it can do on your machine

Read from SKILL.md and the folder at commit 87305cd. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Bash
  • Read

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • git
  • python
  • claude

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • ODIN_ADMIN_PASSWORD

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hk Local Run Spec loads about 924 tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 271 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~77

When it runs · the whole SKILL.md, loaded when a task matches

~924

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:55

  that `temp_test_dir/` exists and has a `.env`:

• NoteMentions a .env fileSKILL.md:58

  ls "$WORK_DIR/.env" 2>/dev/null

• NoteMentions a .env fileSKILL.md:63

  temp_test_dir/ not found or missing .env.

• NoteMentions a .env fileSKILL.md:64

  est_dir && cp .env.example temp_test_dir/.env

• NoteMentions a .env fileSKILL.md:65

  Then edit temp_test_dir/.env with your ODIN_ADMIN_USER and ODIN_ADMIN_PASSWORD.

• NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

  allowed-tools: Bash, Read

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from deepklarity/harness-kit at commit 87305cd, republished under its MIT licence (© deepklarity). 271 words, ~924 tokens.

name

hk-local-run-spec

description

Plan and execute an odin spec. Handles working directory, auth, nested-session detection, and post-run diagnostics. Use whenever the user wants to run a spec, test a spec, or do a smoke test. Triggers on: 'run this spec', 'test this spec', 'odin plan', 'smoke test', or /hk-local-run-spec.

allowed-tools

Bash, Read

argument-hint

<spec_path> [--mock] [--quick] [--exec-only <task_id>]

/hk-local-run-spec ../sample_specs/poem_spec.md
/hk-local-run-spec ../sample_specs/poem_spec.md --quick
/hk-local-run-spec ../sample_specs/poem_spec.md --mock
/hk-local-run-spec --exec-only a1b2

# Claude Code sets this env var when running
echo "${CLAUDE_CODE_ENTRYPOINT:-not_set}"

REPO_ROOT=$(git rev-parse --show-toplevel)
WORK_DIR="$REPO_ROOT/odin/temp_test_dir"

ls "$WORK_DIR/.env" 2>/dev/null

temp_test_dir/ not found or missing .env.
Create it: cd odin && mkdir -p temp_test_dir && cp .env.example temp_test_dir/.env
Then edit temp_test_dir/.env with your ODIN_ADMIN_USER and ODIN_ADMIN_PASSWORD.

cd "$WORK_DIR" && odin plan <spec_path> --quiet

cd "$WORK_DIR" && odin specs
cd "$WORK_DIR" && odin status

cd "$WORK_DIR" && odin exec <task_id> [--mock]

## Spec Run Commands

Run these from a regular terminal (not inside Claude Code):

### 1. Plan
cd <WORK_DIR> && odin plan <spec_path> --auto

### 2. Review
cd <WORK_DIR> && odin specs
cd <WORK_DIR> && odin status

### 3. Execute (run for each task)
cd <WORK_DIR> && odin exec <task_id> [--mock]

### 4. Post-run diagnostic
cd <REPO_ROOT>/taskit/taskit-backend && python testing_tools/spec_trace.py <spec_id> --brief

After execution completes, check results with:
  /hk-local-diagnose spec <spec_id> --brief

© deepklarity, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/hk-local-run-spec of deepklarity/harness-kit.

Open the folder on GitHubat commit 87305cd