Investigate

Find the root cause of an error, failing test, regression, slowdown or unexpected behavior before fixing it. Use for 'why is this failing', 'debug this', 'investigate', 'this broke after the upgrade' or 'figure out what's wrong'.

9 starsFinance & Crypto Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add borkweb/skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add borkweb/skills --skill investigate
Manual install
git clone --depth 1 https://github.com/borkweb/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/gstack/investigate ~/.claude/skills/investigate

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Investigate

Establish causal evidence before fixing a bug. For diagnosis-only requests, report the cause and correction without editing source.

## Start with the symptom

Read the error, failing test, issue or observed behavior. Establish expected versus actual behavior and reproduce the failure in the relevant environment. Inspect the implicated code, callers and data. Reuse a supplied verified root cause rather than repeating discovery.

Use quick mode for a direct, verifiable cause. If its first hypothesis fails, broaden the investigation. For performance, environment, regression, intermittent, order-dependent or concurrency problems read only the corresponding section of [specialized.md](specialized.md).

Outside quick mode, build the reproduction loop before forming any hypothesis: one command, already run, that goes red on the reported symptom (not a nearby failure), gives the same verdict on every run (for a flaky bug, a pinned reproduction rate high enough to debug against) and finishes in seconds where the system allows. Then shrink it until every remaining input, step and setting is needed to stay red. When no such command can be built, report what you tried and ask for environment access, a captured artifact or permission to add temporary instrumentation.

## Investigate
Read the full skill on GitHub

Details

Skill name
investigate
Repository
borkweb/skills
Path
skills/gstack/investigate/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Investigate skill do?

Find the root cause of an error, failing test, regression, slowdown or unexpected behavior before fixing it. Use for 'why is this failing', 'debug this', 'investigate', 'this broke after the upgrade' or 'figure out what's wrong'.

How do I install the Investigate skill?

Claude Code plugin: /plugin marketplace add borkweb/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Investigate popular?

It lives in borkweb/skills, which has 9 GitHub stars and 0 forks.

Related skills

Prototype

9

borkweb/skills

Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".

Frontend & DesignIn 1 list

Agents Md Lint

9

borkweb/skills

Audit and trim AI agent instruction files (AGENTS.md, CLAUDE.md, CONVENTIONS.md, .cursorrules, etc.) by testing which facts an AI agent can discover from code alone. Use when asked to lint, audit, optimize, prune, or trim any agent instruction file in a repository. Removes redundant documentation that wastes context tokens. Supports a dry-run mode that reports findings without modifying files.

AI, LLMs & Agents

Auto Scope

9

borkweb/skills

Scopes a coding task before implementation — names the handful of files actually relevant (read/edit these), the areas to leave alone, and any open scope questions, so work doesn't start by reading the whole repo. Fires proactively at the start of substantive, multi-file, or unfamiliar-area work; stays silent on single-file edits, one-line fixes, questions, and continued work in an area already scoped this session. Use when beginning a feature, bug fix, or refactor that could plausibly touch several files or an area not yet seen this session.

Software Development

Alpha Vantage

9

huytran1120/vietnam-agentic-skills

Access 20+ years of global financial data: equities, options, forex, crypto, commodities, economic indicators, and 50+ technical indicators.

Finance & Crypto

Metric Definition Reviewer

9

shisuidata/ss-data-skills

Use when reviewing or defining a business metric, KPI, or analytics indicator. Checks business intent, population, event definition, time window, grain, filters, edge cases, status lifecycle, consistency, and questions that must be confirmed. 中文触发词:指标口径、口径审查、指标定义、分子分母。

Finance & Crypto

Quote Builder

6

MarcoZorn/agencykit

Build a line-item client quote with payment terms and a revision policy, run an internal margin check, and warn when gross margin drops below 40 percent before you send it.

Finance & Crypto

Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.