component-research-and-reporting - SKILL.md Agent Skill

name: component_research_and_reporting description: "Use when: Researching component markings online, interpreting datasheets, updating diagnosis results, and writing the final troubleshooting report. Combines research findings with measurement results into a final diagnosis and repair recommendation. Datenblatt-Recherche, Bauteil identifizieren, Abschlussbericht, Diagnose-Update, final report, repair recommendation, Reparaturempfehlung."

Grounds the diagnosis in verifiable component data: searches for datasheets, verifies pinouts and typical application schematics, reconciles research with prior measurements, and produces a final actionable report. - Component inventory with markings (from `board_image_intake` or equivalent) - Fault hypotheses with priority ranking (from `fault_hypothesis_engine` or equivalent) - Measurement results (from user-provided data or `multimeter_test_planner` execution) - Optional: Specific component markings to prioritize for research 1. Search for each unverified component marking using web search and datasheet sources. Run parallel searches for independent components. 2. Verify pinouts and typical application circuits — confirm that the assumed component function matches actual package behavior from the datasheet. 3. Update the diagnosis: for each prior hypothesis, determine if it is now Confirmed, Refuted, or Still Open based on research and measurement data. 4. Synthesize all evidence into a final ranked diagnosis with an explicit confidence percentage. 5. Create a simplified text-based functional sketch (ASCII block diagram) of the circuit with the suspected fault location marked. Create or update the following files in the `analysis/` folder (or path specified by the user):

06_research_findings.md

Per component researched, use this table:

Component	Marking	Identified As	Package Match	Datasheet Source	Confidence
U1	TP4056	Li-Ion charge IC (TPOWER/TOPPOWER)	SOT-23-8 ✓	lcsc.com / datasheet PDF	Confirmed
Q1	S8050	NPN BJT 25V/500mA (SANYO)	SOT-23 ✓	datasheet PDF	Confirmed
IC2	"A3C"	Unresolved — 3 candidates found	SOT-23-5	—	Unclear

Classification for each component:

Confirmed — full datasheet match: marking, package, and pinout all consistent
Probable — typical application match, no exact datasheet found for this specific marking
Unclear — marking unresolvable or multiple conflicting candidates — state this explicitly

07_diagnosis_update.md

Updated hypothesis status after research and measurements:

Hypothesis	Status	Evidence Basis	Updated Confidence
H1: Cold solder at J1	Confirmed	Measurement 1: 0.4V drop under load [Messung]	90%
H2: Degraded battery	Refuted	Cell voltage drop only 0.05V under load [Messung]	—
H3: SW1 contact fault	Still Open	Not yet measured	—

final_report.md

Structure:

Executive Summary (2–3 sentences: device description, reported fault, top probable cause)
Evidence Base (key observations, measurements, and research findings that form the diagnosis — each with source tag)
Most Probable Root Cause (with confidence %, e.g., "Cold solder joint at J1 pin 1 — 85% confidence")
Recommended Action (specific, actionable repair step, e.g., "Reflow solder joint at J1 pin 1 with fresh flux; test under load afterward")
Alternative Causes Still Open (secondary hypotheses not yet ruled out)
Limitations (what could not be determined without additional measurements or equipment)

circuit_map.md

Simplified ASCII block diagram showing the power path, signal path, and the suspected fault location marked with [?FAULT].

Example:

[Battery Cell]──[J1 connector ?FAULT]──[F1 fuse]──[U1 TP4056]──[Load / Motor]
                                                        │
                                                   [USB charge input]

- Never state component specifications that were not found in a datasheet — if a datasheet is not found, mark the identification as "Unverified" and state which sources were searched. - Always separate research results into Confirmed / Probable / Unclear — never present uncertain identifications as facts. - The final report must cite the evidence source for every diagnostic conclusion with source tags: [Image], [Measurement], [Research], [Domain Knowledge]. - If measurements contradict the initial hypotheses, update the diagnosis accordingly — do not force-fit evidence to a prior conclusion.