Agent skill

Hk Local Diagnose

by deepklarity in deepklarity/harness-kit

Run diagnostic scripts on tasks, specs, boards, or reflections.

MITAuto-check: notesDevelopment

Install Hk Local Diagnose

skills CLI

$ npx skills add deepklarity/harness-kit --skill hk-local-diagnose -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install deepklarity/harness-kit hk-local-diagnose --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/deepklarity/harness-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/hk-local-diagnose .claude/skills/hk-local-diagnose && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "hk-local-diagnose" agent skill from https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-local-diagnose into .claude/skills/hk-local-diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hk-local-diagnose", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-local-diagnose

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add deepklarity/harness-kit --skill hk-local-diagnose -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install deepklarity/harness-kit hk-local-diagnose --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/deepklarity/harness-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/hk-local-diagnose .agents/skills/hk-local-diagnose && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "hk-local-diagnose" agent skill from https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-local-diagnose into .agents/skills/hk-local-diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hk-local-diagnose", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add deepklarity/harness-kit --skill hk-local-diagnose -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install deepklarity/harness-kit hk-local-diagnose --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/deepklarity/harness-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/hk-local-diagnose .cursor/skills/hk-local-diagnose && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "hk-local-diagnose" agent skill from https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-local-diagnose into .cursor/skills/hk-local-diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hk-local-diagnose", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/deepklarity/harness-kit.git --path .claude/skills/hk-local-diagnose

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add deepklarity/harness-kit --skill hk-local-diagnose -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install deepklarity/harness-kit hk-local-diagnose --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/deepklarity/harness-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/hk-local-diagnose .gemini/skills/hk-local-diagnose && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "hk-local-diagnose" agent skill from https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-local-diagnose into .gemini/skills/hk-local-diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hk-local-diagnose", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install deepklarity/harness-kit hk-local-diagnose

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add deepklarity/harness-kit --skill hk-local-diagnose -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/deepklarity/harness-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/hk-local-diagnose .github/skills/hk-local-diagnose && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "hk-local-diagnose" agent skill from https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-local-diagnose into .github/skills/hk-local-diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hk-local-diagnose", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add deepklarity/harness-kit --skill hk-local-diagnose -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install deepklarity/harness-kit hk-local-diagnose --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/deepklarity/harness-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/hk-local-diagnose .opencode/skills/hk-local-diagnose && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "hk-local-diagnose" agent skill from https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/hk-local-diagnose into .opencode/skills/hk-local-diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hk-local-diagnose", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: hk-local-diagnose
GitHub stars: 100
Token cost: ~808 tokens
SKILL.md length: 245 words
Files: 1
Skills in repo: 18
Repo updated: Jul 15, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Run diagnostic scripts on tasks, specs, boards, or reflections.

Works in 3 steps: Resolve the repo root → Build and run the command → Display the output
The user wants to inspect
SKILL.md covers Usage, Arguments, Script mapping and Execution, plus 1 more section
Calls git and python

What it does

Hk Local Diagnose is an agent skill from deepklarity/harness-kit. Run diagnostic scripts on tasks, specs, boards, or reflections. Wraps testingtools/ with proper working directory and output mode selection. Use this skill whenever the user wants to inspect, debug, or check the state of a task, spec, board, or reflection — even if they don't say 'inspect' explicitly. Triggers on: 'why did task X fail', 'show me spec Y', 'what's on the board', 'check task', 'inspect', 'diagnose', or /hk-local-diagnose.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: A kit for building with AI agents and also the engineering patterns around it. The licence is MIT.

When your agent uses it

The user wants to inspect
Check the state of a task
Reflection — even if they dont say inspect explicitly
: why did task X fail

Example prompts

“t say”
“explicitly. Triggers on:”
“show me spec Y”
“/hk-local-diagnose”

Requirements

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

Workflow steps

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

Resolve the repo root
Build and run the command
Display the output

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
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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hk Local Diagnose loads about 808 tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 245 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~115
When it runs · the whole SKILL.md, loaded when a task matches: ~808

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

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

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). 245 words, ~808 tokens.

Download SKILL.mdSave it as .claude/skills/hk-local-diagnose/SKILL.md (or your agent's skills folder).

name: hk-local-diagnose
description: Run diagnostic scripts on tasks, specs, boards, or reflections. Wraps testing_tools/ with proper working directory and output mode selection. Use this skill whenever the user wants to inspect, debug, or check the state of a task, spec, board, or reflection — even if they don't say 'inspect' explicitly. Triggers on: 'why did task X fail', 'show me spec Y', 'what's on the board', 'check task', 'inspect', 'diagnose', or /hk-local-diagnose.
allowed-tools: Bash, Read
argument-hint: <type> <id> [--brief | --full | --json] [--sections a,b]

/hk-local-diagnose — Diagnostic Script Runner

Run the right diagnostic script with the right flags, from the right directory. No more remembering paths or cd-ing around.

Usage

/hk-local-diagnose task 42
/hk-local-diagnose task 42 --brief
/hk-local-diagnose spec 15 --json --sections tasks,problems
/hk-local-diagnose board
/hk-local-diagnose board 3
/hk-local-diagnose reflection 8 --full
/hk-local-diagnose snapshot sp25 ../../tests/e2e_snapshots/smoke

Arguments

Parse $ARGUMENTS to extract:

type (required): task, spec, board, reflection, or snapshot
id (required for all except board): the numeric ID or spec prefix
flags (optional): --brief, --full, --json, --slim, --sections <list>

If no flags are provided, default to --brief — this is the token-efficient choice for LLM consumption. The user can always ask for --full if they need more.

Script mapping

Type	Script	Required args
`task`	`task_inspect.py <id>`	id
`spec`	`spec_trace.py <id>`	id
`board`	`board_overview.py [id]`	id optional
`reflection`	`reflection_inspect.py <id>`	id
`snapshot`	`snapshot_extractor.py <id> <output_dir>`	id + output_dir

Execution

All scripts run from the taskit/taskit-backend/ directory. The working directory for execution is always:

REPO_ROOT/taskit/taskit-backend/

Where REPO_ROOT is the git repository root (find it with git rev-parse --show-toplevel).

Step 1: Resolve the repo root

bash

REPO_ROOT=$(git rev-parse --show-toplevel)

Step 2: Build and run the command

bash

cd "$REPO_ROOT/taskit/taskit-backend" && python testing_tools/<script> <id> [flags]

Pass through any --brief, --full, --json, --slim, or --sections flags directly to the script.

Step 3: Display the output

Print the script output directly. Do not summarize or interpret — the scripts already produce well-structured output with problem detection built in.

If the script exits with a non-zero code, show the error and suggest:

Check that the ID exists: "Is task/spec/board {id} a valid ID?"
Check that the Django app is set up: "Is the taskit-backend database accessible?"

Error handling

If $ARGUMENTS is empty or missing the type, print usage help:

Usage: /hk-local-diagnose <type> <id> [flags]

Types: task, spec, board, reflection, snapshot
Flags: --brief (default), --full, --json, --slim, --sections <list>

Examples:
  /hk-local-diagnose task 42
  /hk-local-diagnose spec 15 --json --sections tasks,problems
  /hk-local-diagnose board

Files

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

Open the folder on GitHubat commit 87305cd

Compare with similar skills

Hk Local Diagnose next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Hk Local Diagnose compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Hk Local Diagnose this skilldeepklarity/harness-kit	100	—	~808	Automated safety check: Notes	MIT	2 mo ago
Vercel Composition Patternssupabase/supabase	111k	58 repos	~726	Automated safety check: Pass	MIT	yesterday
Finishing a Development Branchobra/superpowers	297k	5 repos	~1.9k	Automated safety check: Pass	MIT	yesterday
Typescript Advanced Typesrolling-scopes/rsschool-app	10k	25 repos	~4.2k	Automated safety check: Pass	MPL-2.0	7 days ago
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	today
Code Review ChecklistshareAI-lab/learn-claude-code	78k	4 repos	~1.1k	Automated safety check: Pass	MIT	12 days ago

Similar skills

Vercel Composition Patterns
supabase/supabase
Official
React composition patterns that scale. An agent skill from supabase/supabase.
111k GitHub starsUsed in 58 repos~726 tokens
DevelopmentAuto-check passed
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
297k GitHub starsUsed in 5 repos~1.9k tokens
DevelopmentAuto-check passed
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
10k GitHub starsUsed in 25 repos~4.2k tokens
DevelopmentAuto-check passed
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
69k GitHub starsUsed in 3 repos~4.2k tokens
DevelopmentAuto-check passed
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
78k GitHub starsUsed in 4 repos~1.1k tokens
DevelopmentAuto-check passed
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
32k GitHub starsUsed in 4 repos~3.3k tokens
DevelopmentAuto-check passed

Questions about Hk Local Diagnose

What does Hk Local Diagnose do?

Run diagnostic scripts on tasks, specs, boards, or reflections. Hk Local Diagnose is an agent skill from deepklarity/harness-kit. Run diagnostic scripts on tasks, specs, boards, or reflections.

When should I use Hk Local Diagnose?

Hk Local Diagnose fits situations like: the user wants to inspect; check the state of a task; reflection — even if they dont say inspect explicitly; : why did task X fail.

How do I install Hk Local Diagnose in Claude Code?

Run `npx skills add deepklarity/harness-kit --skill hk-local-diagnose -a claude-code`. Or copy the skill folder (.claude/skills/hk-local-diagnose in deepklarity/harness-kit) into .claude/skills/hk-local-diagnose in your project. Claude Code loads it when a task matches its description.

How do I install Hk Local Diagnose in Codex?

Run `npx skills add deepklarity/harness-kit --skill hk-local-diagnose -a codex`. Or copy the skill folder (.claude/skills/hk-local-diagnose in deepklarity/harness-kit) into .agents/skills/hk-local-diagnose in your project. Codex loads it when a task matches its description.

Can I use Hk Local Diagnose in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deepklarity/harness-kit --skill hk-local-diagnose -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hk-local-diagnose, .gemini/skills/hk-local-diagnose, .github/skills/hk-local-diagnose and .opencode/skills/hk-local-diagnose in your project.

What does Hk Local Diagnose need to run?

Going by SKILL.md and its folder, Hk Local Diagnose needs the command-line tools its instructions call (git and python). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash, Read.

Does Hk Local Diagnose access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Hk Local Diagnose safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Hk Local Diagnose use?

Hk Local Diagnose is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hk Local Diagnose use?

About 808 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Hk Local Diagnose?

Skills that share tags, products or a category with Hk Local Diagnose: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hk Local Diagnose?

deepklarity (a GitHub organization) maintains it in deepklarity/harness-kit, which has 100 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on July 15, 2026.

Source: deepklarity/harness-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Hk Local Diagnose

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

/hk-local-diagnose — Diagnostic Script Runner

Usage

Arguments

Script mapping

Execution

Step 1: Resolve the repo root

Step 2: Build and run the command

Step 3: Display the output

Error handling

Files

Compare with similar skills

Similar skills

More from deepklarity/harness-kit

Related

Questions about Hk Local Diagnose