Skip to content
Agentmart
Submit a tool

investigating

Use when researching questions, diagnosing root causes without fixing them, or gathering evidence.

Skill by wayne930242

IndexedMIT★ 2
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/wayne930242-investigating

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when researching questions, diagnosing root causes without fixing them, or gathering evidence.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/investigating

What's inside

Skill name
investigating
Description
Use when researching questions, diagnosing root causes without fixing them, or gathering evidence.
License
MIT
Instructions
19 lines in SKILL.md · view on GitHub

Files (3)

  • SKILL.md
  • diagnose.md · playbooks/
  • research.md · playbooks/

SKILL.md (first lines)

# Investigating

Run the loop in [../anchorloop/SKILL.md](../anchorloop/SKILL.md). The anchor is the exact question and its completion boundary: answered, or the missing evidence named precisely.

1. Gather evidence through the playbook below that fits the question.
2. Cross-check material claims and resolve source conflicts.
3. Grade each material claim by its strongest evidence: asserted, cited
   (`file:line` or primary source), reasoned (the failure path walked and shown
   not to reach), executed (a script or test against the real code), or
   reproduced (observed in the running system). A claim with no evidence is
   `unknown`.
4. Report the reasoning chain with each material claim's source and grade beside it.

## Playbooks

- [research](playbooks/research.md): how something works, what is true, or why it was built this way.
- [diagnose](playbooks/diagnose.md): why a running system misbehaves, when the deliverable is a diagnosis rather than a fix.

From wayne930242/aaaav, MIT.

More from wayne930242/aaaav

Signals

Stars
2
Forks
1
Open issues
0
Last commit (this folder)
Oct 21, 2026 (8 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from wayne930242

Cite this page

investigating skill. Agent Mart. https://agentmart.dev/skills/wayne930242-investigating (last updated 2026-10-24)