build-debug-tool
/build-debug-tool
Turn a repeated hunt through logs, JSON dumps or database rows into a permanent diagnostic tool, at the moment you notice the pain. Triggers on: 'build a debug tool', 'make this dump readable', 'I keep grepping for this', 'I keep typing this python -c', or /build-debug-tool. Test commands and test data belong to hk-testing-shortcuts.
- Author
- deepklarity ↗
- Repository
- harness-kit ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Turn a repeated hunt through logs, JSON dumps or database rows into a permanent diagnostic tool, at the moment you notice the pain. Triggers on: 'build a debug tool', 'make this dump readable', 'I keep grepping for this', 'I keep typing this python -c', or /build-debug-tool. Test commands and test data belong to hk-testing-shortcuts.
Triggers from the description
Original author description
Turn a repeated hunt through logs, JSON dumps or database rows into a permanent diagnostic tool, at the moment you notice the pain. Triggers on: 'build a debug tool', 'make this dump readable', 'I keep grepping for this', 'I keep typing this python -c', or /build-debug-tool. Test commands and test data belong to hk-testing-shortcuts.
How it works
- The tells
- Where the tool goes
- The bar
- Example
SKILL.md preview
---
name: build-debug-tool
description: "Turn a repeated hunt through logs, JSON dumps or database rows into a permanent diagnostic tool, at the moment you notice the pain. Triggers on: 'build a debug tool', 'make this dump readable', 'I keep grepping for this', 'I keep typing this python -c', or /build-debug-tool. Test commands and test data belong to hk-testing-shortcuts."
---
# build-debug-tool
Build the tool the moment you are reading more than the answer needs, retyping the same extraction, or chaining grep and python over JSON to answer a question you have asked before. A permanent, named tool; raw logs and ad-hoc scripts are the fallback for when the tool itself looks wrong, never the routine. Before this workspace's diagnostic scripts existed, one session spent an hour grepping escaped log lines and retyping the same ten-line python three times; the scripts then answered every question in seconds.
## The tells
Any one of these means stop and build:
- You typed nearly the same extraction twice (a grep chain, a `python -c` over JSON, a jq pipe).
- You are reading a wall of output to find one fact (a giant debug dump, an escaped multi-line error, a 300-line JSON).
- A check failed and the reason lives somewhere you cannot read with one command.
- You wrote a "temporary" script in the scratchpad that you would want again tomorrow.
## Where the tool goes
Look first at what exists: the workspace's diagnostic-scripts folder, its run/log command's help, and its repo-wide scripts folder (CLAUDE.md names each). Extend one of those when it already answers part of the question; a new mode or `--sections` entry on an existing script beats a new script.
1. **A service's own data** (its entities, records, jobs): a script in that service's diagnostic-scripts folder (CLAUDE.md), following the shared-helper pattern its neighbours use so it gets `--brief`, `--json`, `--full` and `--sections`. It reads the data directly (through the app's own data layer, or a direct query) rather than over the network when the network path needs auth the script can bypass. Add a row to the "when to reach for which script" table in the root `CLAUDE.md`.
2. **Orchestration runs and logs**: a flag on the workspace's run/log command or CLI. Log extraction is the right answer only when the fact cannot be made to land somewhere a script can read it (an error inside a rolled-back transaction never reaches the run's own record).
3. **Repo-wide checks and comparisons**: a script in the repo-wide scripts folder, the shape of the verify gate: one command, a one-line verdict, evidence attached on failure.
4. **Test commands, test IDs, how-do-I-test knowledge**: `hk-testing-shortcuts` owns it; call the Skill tool with `hk-testing-shortcuts` and stop here.
## The bar
- One command, one question answered, one screen of output.
- Works from the ID forms a person actually has (a task id or its board key, a spec id or its slug).
- Prints the denominator with the fact ("comments: (none)" beats empty output).
- A time budget where hanging is possible; on failure, print the evidence, not just the failure.
- Stays in the same change as the work that needed it, so it is committed together when the user commits. An uncommitted tool is a snippet.
Done when the tool answers the question that caused the pain in one command on the real case, and the chat reply gives that command line.
## Example
- Existing tools: list your testing-tools folder, your CLI's `--help`, and `scripts/`.
- A data script (records, boards, reports) lives in the diagnostic-scripts folder and reads through the app's own data layer; CLAUDE.md rules out curl and raw API calls.
- A CLI log tool is a flag on the existing log command.
- A repo-wide script has the shape of `scripts/verify.sh`.
Versions
The database has no other skills named build-debug-tool.
Database snapshot: 13.11.2026 · package version 42ecdaaaa263 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 98ci-crash-dump
Download and debug crash dumps from CI test failures in dotnet repositories. Use when a CI test crashed (not just failed), when the user wants to debug a crash dump from a PR or build, or when asked "debug dump", "download dump", "crash dump from CI", "test crashed", "analyze… - 100deepgram-debug-bundle
Collect Deepgram debug evidence for support and troubleshooting. Use when preparing support tickets, investigating issues, or collecting diagnostic information for Deepgram problems. Trigger: "deepgram debug", "deepgram support ticket", "collect deepgram logs", "deepgram… - 100deepgram-debug-bundle
Collect Deepgram debug evidence for support and troubleshooting. Use when preparing support tickets, investigating issues, or collecting diagnostic information for Deepgram problems. Trigger with phrases like "deepgram debug", "deepgram support", "collect deepgram logs",… - 100groq-debug-bundle
Collect Groq debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Groq problems. Trigger with phrases like "groq debug", "groq support bundle", "collect groq logs", "groq diagnostic". - 100groq-debug-bundle
Collect Groq debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Groq problems. Trigger with phrases like "groq debug", "groq support bundle", "collect groq logs", "groq diagnostic". - 95tarn-api-testing
Write, run, debug, and iterate on API tests using Tarn — a CLI-first API testing tool with .tarn.yaml files and structured JSON output. Use when: writing API tests, running tarn commands, debugging test failures, generating tests from OpenAPI specs or curl commands, setting up…