AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Hk Local Diagnose

skill-deepklarity-harness-kit-hk-local-diagnose · by deepklarity

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', 'ins…

No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add skill-deepklarity-harness-kit-hk-local-diagnose

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-deepklarity-harness-kit-hk-local-diagnose)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
27d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Hk Local Diagnose? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

/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

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 | | spec | spec_trace.py | id | | board | board_overview.py [id] | id optional | | reflection | reflection_inspect.py | id | | snapshot | snapshot_extractor.py | 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

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

Step 2: Build and run the command

cd "$REPO_ROOT/taskit/taskit-backend" && python testing_tools/  [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   [flags]

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

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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.