testdino-hq

Investigate Tool — Data skill for Claude Code

Data community

Investigate why a tool is not working as expected.

How to install Investigate Tool

Installs to ~/.claude/commands/testdino-hq-testdino-mcp-investigate-tool.md

Terminal

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/testdino-hq/testdino-mcp/HEAD/.claude/commands/investigate-tool.md -o ~/.claude/commands/testdino-hq-testdino-mcp-investigate-tool.md

Restart Claude Code, or start a new session, for it to be picked up.

What Investigate Tool does

Investigate why a tool is not working as expected. This command is for debugging tool behavior — wrong responses, auth failures, missing data, or unexpected errors.

**Input:** $ARGUMENTS — description of the problem (e.g., "list_testruns returns empty for valid projectId", "health tool says PAT is invalid but it works in curl")

Phase 1: Reproduce the Problem

Identify the tool — Which tool is affected?
Read the tool source — Read the handler file completely
**Trace the

Alternatives in Data

Bitbucket Data Center 71.9k ★
Financial Services — Reference agents, skills, and data connectors for the financial-services workflows we see most — investment ba 34.5k ★
Data Contract — This document defines which files belong to the system (auto-updatable) and which belong to the user (never to 32.5k ★