agentleFS
tamesystemstamesystems/intent-engineering-skills/skills/investigate/SKILL.md

investigate

Skill0 starsChanged 40 days agoMITView on GitHub

Resolve a consequential uncertainty with discriminating evidence. Use for bugs, unfamiliar behavior, causal questions, architectural uncertainty, performance problems, competing explanations, or unknowns that could change a decision.

128 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pair-agent, plan-devex-review and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • seek888Skill

    pair-agent

    Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".

    Also in 10 projects that use this

  • seek888Skill

    plan-devex-review

    Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".

    Also in 13 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 7 projects that use this

  • ayudaySkill

    setup-deploy

    Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".

    Also in 14 projects that use this

  • ayudaySkill

    cso

    Chief Security Officer mode. Performs OWASP Top 10 audit, STRIDE threat modeling, attack surface analysis, auth flow verification, secret detection, dependency CVE scanning, supply chain risk assessment, and data classification review. Use when: "security audit", "threat model", "pentest review", "OWASP", "CSO review".

    Also in 17 projects that use this

  • ramybarsoumSkill

    document-release

    Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped.

    Also in 18 projects that use this

  • +1 more from seek888

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 115 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    State the uncertainty: Write the question and how its answer could change what happens next.

    line 12
  2. Distinctive:

    Establish the evidence already available: Avoid repeating prior work.

    line 13
  3. Distinctive:

    Seek discriminating evidence: Prefer cheap, high-information observations that make hypotheses diverge: reproduction, traces, logs, …

    line 15
  4. Distinctive:

    Stop at decision sufficiency: Do not seek certainty for its own sake.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 115 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Investigate

Reduce uncertainty enough to make the next decision well. The goal is not information collection; it is a justified belief update.

Work

  1. State the uncertainty. Write the question and how its answer could change what happens next. If it cannot affect a consequential decision, reconsider the investigation.
  2. Establish the evidence already available. Avoid repeating prior work.
  3. Maintain competing hypotheses. For causal questions, name plausible alternatives before committing to one. Include measurement or environment error when credible.
  4. Seek discriminating evidence. Prefer cheap, high-information observations that make hypotheses diverge: reproduction, traces, logs, profiling, history, controlled experiments, minimal prototypes, primary documentation, targeted tests. When a performance number will drive a decision, follow references/performance-evidence.md to prove the measured work happened and the comparison is valid.
  5. Update explicitly. Reject contradicted hypotheses, strengthen supported ones, and introduce new hypotheses when evidence requires it.
  6. Reproduce when useful. For defects, obtain a reliable reproduction when practical. For design uncertainty, prototype the smallest risky assumption rather than debating it abstractly.
  7. Stop at decision sufficiency. Do not seek certainty for its own sake.

Return

  • Question
  • Existing evidence
  • Hypotheses considered
  • Discriminating evidence gathered
  • Finding and confidence
  • Remaining uncertainty
  • Decision implications

Failure signals

Watch for confirmation bias, one-hypothesis debugging, evidence merely compatible with a favorite explanation, research that cannot change action, and fixing before understanding when the root cause matters.

Done when

The consequential uncertainty has been reduced enough that remaining uncertainty is unlikely to alter the next decision, or further investigation is demonstrably not worth its cost.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.