Research-Bot

Part of the Research Bot suite. Find, validate, and integrate literature, SOTA, standards, citations, datasets, and technical references for ECE research. Use when the user asks for papers, references, recent work, standards, citation validation, or when a strong technical critique needs evidence. Must not fabricate citations. Do not use for pure code debugging or artifact editing without a literature component.

Part of the Research Bot suite. Review academic research artifacts such as journal or conference paper drafts, thesis chapters, abstracts, introductions, methodology sections, reports, and formal academic emails for rigor, contribution clarity, logical flow, precision, professionalism, and user authorship. Use the 2+2 feedback rule. Do not use for code execution, raw data debugging, or literature search as the main task.

Part of the Research Bot suite. Advise and challenge ECE research methodology for optimization algorithms, power-system simulation, system modeling, hardware control, PLC implementation, and validation plans. Use for method selection, assumptions, trade-offs, convergence, fidelity, constraints, and cross-validation. Do not use for raw data cleaning, literature-only requests, or finished-paper copyediting.

Part of the Research Bot suite. Develop critical thinking for research claims, assumptions, anomalies, interpretations, authority dependence, confirmation bias, and reviewer defense. Use to pressure-test a research idea, result, paper claim, or interpretation. Do not use for implementation, data cleaning, or citation search as the main task.

Primary entry point for the Research Bot suite. Route Korean or English ECE research tasks to methodology review, data troubleshooting, critical-thinking defense, artifact review, code/simulation review, literature search, ethics/integrity review, or progress planning. Use when the user asks for Research Bot, is unsure which research skill to use, or provides a mixed research-development request.

Part of the Research Bot suite. Review research code, simulation scripts, notebooks, MATLAB/Python models, power-flow or OPF scripts, MCMC simulations, PLC/control logic, and analysis pipelines for physical assumptions, units, reproducibility, solver configuration, documentation, tests, and maintainability. Use for code or repository review in research contexts. Do not use for generic web app code or pure writing review.

Part of the Research Bot suite. Troubleshoot research data collection and analysis problems, including raw sensor or field data, SCADA logs, simulation outputs, MCMC chains, power-flow results, hardware logs, missing values, anomalies, convergence failures, and aliasing. Use when data or analysis results look wrong. Do not use for paper editing, ethics-only dilemmas, or literature search only.

Part of the Research Bot suite. Advise on research ethics, data integrity, anomaly handling, cherry-picking, falsification, fabrication, authorship, plagiarism, self-plagiarism, open-source/code attribution, conflicts of interest, funding pressure, and disclosure dilemmas. Use when ethical or professional conduct risk is present. Do not use for ordinary methodology review unless integrity risk is central.

Part of the Research Bot suite. Plan research progress, thesis milestones, publication roadmaps, experiment schedules, weekly action plans, dissertation storylines, postdoc preparation, and alignment between short-term artifacts and long-term academic goals. Use for research project planning and progress tracking. Do not use for technical debugging, literature search, or ethics-only dilemmas.

Part of the Research Bot suite. Route ambiguous ECE research, R&D, thesis, paper, experiment, simulation, data, methodology, literature, ethics, or progress-planning requests to the correct specialized research skill. Use when the user is unsure where to start or gives a broad research problem. Do not perform deep methodology review, data debugging, literature search, or artifact editing yourself.