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/SURVEY_WRITING_GUIDE.md
View on GitHub# Survey Writing Guide — Industrial AI
This guide defines the writing philosophy for survey drafts produced by the `survey-draft` deliverable mode. Read this file during all survey phases (S1–S4).
## Why Industrial AI Surveys Are Different
Industrial AI surveys must evaluate work along dimensions that pure ML surveys can ignore:
- **Deployment realism**: algorithm performance alone is insufficient; real-world deployment evidence (pilot lines, factory trials, fleet rollouts) is a first-class evaluation axis.
- **Data scarcity and labeling cost**: most industrial datasets are small, imbalanced, or expensive to annotate. Surveys must surface how each method handles this.
- **Latency spectrum**: acceptable inference latency varies by orders of magnitude (PdM tolerates minutes; scheduling may need sub-second; real-time control needs milliseconds).
- **Sim-to-real gap**: many methods are validated only in simulation. The survey must explicitly flag sim-only vs. real-deployment evidence.
- **Safety and regulatory context**: industrial deployments often intersect with safety standards (IEC 61508, ISO 13849). Note when papers address or ignore these.
## Taxonomy Pattern Library
Use these recommended classification axes when building the survey outline (Phase S1). Combine two axes into a matrix when the literature is dense enough.
| Subdomain | Recommended axes | Example branches |
|-----------|-----------------|-----------------|
| Predictive Maintenance | Signal modality × Method family | Vibration / Acoustic / Current / Multi-modal × CNN / Transformer / Physics-informed / Hybrid |
| Intelligent Scheduling | Problem scale × Solving paradigm | Single-machine / Flexible job-shop / Distributed × Exact / Heuristic / Meta-heuristic / RL |
| Industrial Anomaly Detection | Supervision level × Industrial scenario | Supervised / Semi-supervised / Unsupervised / Self-supervised × Manufacturing / Energy / Process |
| Smart Manufacturing | Production stage × Technology stack | Design / Machining / Assembly / Inspection × Digital twin / Edge AI / Robotics / LLM-assisted |
| CPS and Edge AI | Deployment tier × Optimization target | Cloud / Edge / On-device × Latency / Energy / Accuracy / Privacy |
### Choosing Axes
1. Start with the two axes that produce the most even distribution of papers across cells.
2. If one axis produces a single dominant cell (>50% of papers), consider splitting that axis or switching to a different one.
3. Hybrid taxonomies (e.g., method-based at H2, application-based at H3) are acceptable when a single pair of axes cannot cover the literature.
## Comparison Table Conventions
Comparison tables are mandatory artifacts in survey drafts. Follow these rules:
### Per-H3 Tables (in evidence packs and body sections)
Every H3 subsection must include at least one comparison table with these columns:
| Column | Required | Description |
|--------|----------|-------------|
| Paper | Yes | First author + year |
| Method | Yes | Core technique or model name |
| Dataset | Yes | Benchmark or industrial dataset used |
| Key Metric | Yes | Primary evaluation metric |
| Result | Yes | Quantitative result on key metric |
| Deployment Evidence | Yes | None / Simulation / Pilot / Production |
### Cross-Cutting Table (in Comparative Analysis section)
The Comparative Analysis section (Phase S4) must include at least one cross-cutting table that compares methods across taxonomy branches. Additional columns:
| Column | Required | Description |
|--------|----------|-------------|
| Taxonomy Branch | Yes | Which H2 branch the method belongs to |
| Data Requirement | Recommended | Training data size or labeling need |
| Latency | Recommended | Inference time or real-time capability |
| Scalability | Recommended | Evidence of scaling to production |
## Writing Tone
- Analytical, not promotional. State what the evidence shows, not what "promises" a method holds.
- Use hedging language ("the results suggest", "under the reported conditions") when evidence is limited to a single study.
- Avoid generator-tone phrases: "In this section, we will discuss...", "It is worth noting that...", "Taken together..." (limit to ≤2 occurrences in the entire draft).
- Prefer active constructions: "Zhang et al. [12] propose..." over "A method was proposed by Zhang et al. [12]..."
## Literature Review Quality Standards
Survey papers must exemplify the highest literature review quality. These rules (cross-referenced from the `latex-paper-en` skill's LOGIC module) are especially critical in survey context:
### A1: Thematic Clustering (Mandatory)
Literature MUST be organized by research themes, methodology families, or application domains — never by chronological order or author enumeration. In survey context, the taxonomy axes (see Taxonomy Pattern Library above) define the thematic clusters.
**Anti-pattern**: "In 2018, Smith proposed X. In 2019, Jones introduced Y. In 2020, Wang designed Z."
**Correct pattern**: Group papers by method family (e.g., CNN-based → Transformer-based → Hybrid), then discuss each group's strengths and limitations.
### A2: Critical Analysis After Each Cluster (Mandatory)
Each H3 subsection (theme cluster) MUST end with a critical synthesis paragraph that:
- Summarizes shared strengths and limitations of methods in that cluster
- Identifies open problems within the cluster
- Provides a transition to the next cluster or section
### A3: Research Gap Derivation (Mandatory)
The final subsection of the literature review (or the Comparative Analysis section) MUST explicitly identify:
- Gaps in the current literature that remain unaddressed
- Under-explored combinations of methods and applications
- Missing evaluation dimensions (e.g., deployment evidence, latency, data efficiency)
### A4: Citation Density Funnel
Survey papers naturally follow a funnel pattern: broad introduction citations → focused per-cluster citations → specific technique deep-dives. Maintain this pattern within each H2 section.
> **Full reference**: See `../latex-paper-en/references/modules/LOGIC.md` for detailed detection heuristics and automated check patterns.
## Length Tiers
| Tier | Word range | Typical H2 sections | Typical H3 per H2 |
|------|-----------|---------------------|-------------------|
| Short | 3 000–5 000 | 3–4 | 2–3 |
| Standard | 5 000–10 000 | 4–6 | 3–5 |
| Comprehensive | 10 000–15 000 | 5–7 | 4–6 |
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 |