brycewang-stanford/Auto-Empirical-Research-Skills / skills/35-bahayonghang-academic-writing-skills/skills/industrial-ai-research
industrial-ai-research
VerifiedIndustrial AI literature research with mandatory intake questions, venue-aware source prioritization, structured report outputs, and survey draft generation. Use when the user needs up-to-date research on predictive maintenance, intelligent scheduling, industrial anomaly detection, smart manufacturing, cyber-physical systems, edge AI for automation, or crossover robotics-for-industry topics. Also trigger for adjacent terms: "digital twin", "industrial IoT", "Industry 4.0", "manufacturing AI", "factory automation", "process optimization", or "survey draft" in industrial contexts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.7 KB |
| agents/openai.yaml | config | 420 B |
| evals/evals.json | config | 6.5 KB |
| examples/industrial-anomaly-detection.md | markdown | 562 B |
| examples/intelligent-scheduling.md | markdown | 521 B |
| examples/predictive-maintenance.md | markdown | 536 B |
| examples/survey-predictive-maintenance.md | markdown | 8.8 KB |
| references/SURVEY_WRITING_GUIDE.md | markdown | 6.3 KB |
| references/modules/SURVEY_EVIDENCE.md | markdown | 3.8 KB |
| references/modules/SURVEY_MERGE.md | markdown | 4.4 KB |
| references/modules/SURVEY_OUTLINE.md | markdown | 4.0 KB |
| references/modules/SURVEY_WRITER.md | markdown | 4.3 KB |
| references/quality-checklist.md | markdown | 1.2 KB |
| references/question-flow.md | markdown | 1.8 KB |
| references/report-modes.md | markdown | 2.9 KB |
| references/source-priority.md | markdown | 2.2 KB |
| references/venue-map.md | markdown | 2.9 KB |
references/quality-checklist.md
View on GitHub# Quality Checklist
Run this checklist before final delivery.
## Evidence Rules
- Every important claim has a source.
- Every paper summary states venue or source type.
- Preprints are labeled as preprints.
- Contradictory findings are surfaced, not hidden.
- Generic web summaries are excluded from evidence claims.
## Industrial AI Relevance Rules
- The report stays anchored in automation and Industrial AI.
- Robotics papers appear only when they materially support the topic.
- General AI method papers are not treated as central evidence without industrial linkage.
- Source buckets reflect the requested domain emphasis.
## Report Quality Rules
- The opening intake questions were asked first.
- The final report uses the stable section order from `report-modes.md`.
- The time window and any seminal-paper exceptions are explicit.
- The report ends with concrete next reading or next experiment suggestions.
## Contrarian Pass
Before finalizing, ask:
- Which dominant claim would fail under real industrial constraints?
- Which shortlisted papers are strongest method papers but weakest deployment papers?
- Which part of the field is over-represented because it is easier to publish?
- Which missing evidence would most change the conclusion?
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |