field failure investigator
- Repo stars 1
- Author repo claude-skills
- Domain
- Writing
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @00PrabalK00 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Field Failure Investigator
## Overview
Structure post-failure analysis from field symptoms, logs, operator notes, and hardware context.
## Core Workflow
1. Gather the smallest high-signal evidence set: failing outputs, logs, configs, recent changes, and relevant runtime context.
2. Inspect the implementation and surrounding setup to isolate the narrowest plausible failure surface.
3. Rank likely causes, rule out weak explanations, and identify the most actionable next fix or experiment.
4. Validate the explanation with the smallest reliable check the repo or environment supports.
## Deliver
- A concise diagnosis with the most likely root cause or bounded uncertainty.
- The highest-signal evidence and suspect files, configs, or systems involved.
- The smallest safe fix path or next experiment to run.
## Guardrails
- Do not claim a root cause without evidence that explains the observed behavior.
- Separate symptoms from likely causes and call out uncertainty explicitly.
- Prefer the smallest reproducible scope before escalating to broad changes.
- Avoid commands that actuate hardware, move robots, or change live controller state unless explicitly requested.
Sections and files
Listed in source order.
sections -> Overview → Core Workflow → Deliver → Guardrails
terms -> Structure post-failure analysis from field symptoms, logs, operator notes, and hardware context. · 1. Gather the smallest high-signal evidence set: failing outputs, logs, configs, recent changes, and relevant runtime context. · - A concise diagnosis with the most likely root cause or bounded uncertainty. · - Do not claim a root cause without evidence that explains the observed behavior.
files/cmd -> no explicit files or commands
body sha256 -> ae9428e32829
Core Workflow
Gather the smallest high-signal evidence set: failing outputs, logs, configs, recent changes, and relevant runtime context. Inspect the implementation and surrounding setup to isolate the narrowest plausible failure surface. Rank likely causes, rule out weak explanations, and identify the most actionable next fix or experiment. Validate the explanation with the smallest reliable check the repo or environment supports.
Deliver
A concise diagnosis with the most likely root cause or bounded uncertainty. The highest-signal evidence and suspect files, configs, or systems involved. The smallest safe fix path or next experiment to run.
Guardrails
Do not claim a root cause without evidence that explains the observed behavior. Separate symptoms from likely causes and call out uncertainty explicitly. Prefer the smallest reproducible scope before escalating to broad changes. Avoid commands that actuate hardware, move robots, or change live controller state unless explicitly requested.