industrial-ai-research
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "industrial-ai-research":https://skillpi.com/zh/skills/deepskill-28c54bdd3b17098251feaf6f234d3c12f88b4b6d49473d520ac411d85b4ee797。安装前核对上游来源和版本:https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/blob/bfa0a6e5a843babbf45a1ef1663fd5dc4f07c0ba/skills/35-bahayonghang-academic-writing-skills/skills/industrial-ai-research/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/bfa0a6e5a843babbf45a1ef1663fd5dc4f07c0ba/skills/35-bahayonghang-academic-writing-skills/skills/industrial-ai-research --skill industrial-ai-research来源与配置
查看 GitHub 源码brycewang-stanford/Auto-Empirical-Research-Skills固定提交 bfa0a6e5a843babbf45a1ef1663fd5dc4f07c0ba
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目面向文献与学术工具场景,提供“industrial-ai-research”技能的目录入口。公开标签:learning、工业AI、文献综述、预测性维护。请通过固定上游版本核对实际功能、依赖与权限;此页为 Skillπ 独立编写的用途介绍和原站链接,不代表运行安全保证。原文与附件依各自许可开放。
文件浏览
--- name: industrial-ai-research description: > Industrial 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. metadata: category: academic-writing tags: [industrial-ai, research, literature-review, predictive-maintenance, scheduling, anomaly-detection, smart-manufacturing, cps, arxiv, ieee, survey, survey-draft] version: "1.1" last_updated: "2026-03-12" argument-hint: "[topic] [--mode MODE] [--lang LANG] [--window WINDOW] [--output-dir DIR]" allowed-tools: Read, Glob, Grep, WebSearch, WebFetch --- # Industrial AI Research Run a lean, source-aware research workflow for Industrial AI. ## Capability Summary - Structured literature research for Industrial AI and automation topics - Mandatory four-question intake before any search or synthesis - Venue-aware source prioritization (arXiv, IEEE, automation venues) - Four deliverable modes: research-brief, literature-map, venue-ranked survey, research-gap memo - Contrarian synthesis pass to surface contradictions and under-explored gaps - Survey draft generation: outline-first writing with per-section evidence packs and optional LaTeX export ## Triggering Use this skill when the user wants to: - Survey Industrial AI literature on a specific subtopic - Compare papers across venues or methods within Industrial AI - Identify research gaps in predictive maintenance, scheduling, anomaly detection, or smart manufacturing - Produce a structured research report with source-backed evidence - Draft a structured survey on an Industrial AI subtopic - Produce a survey manuscript with taxonomy, evidence packs, and section-by-section writing ## Do Not Use - Writing or compiling LaTeX/Typst papers (use `latex-paper-en`, `latex-thesis-zh`, or `typst-paper`). Note: survey-draft mode produces Markdown by default; for LaTeX output, it delegates final formatting to `latex-paper-en`. - Auditing paper quality or formatting (use `paper-audit`) - Systematic reviews or meta-analyses requiring IRB or clinical ethics - Topics outside the Industrial AI and automation domain - Auditing an existing paper's quality or formatting (use `paper-audit`) - Editing LaTeX/Typst source files (use the appropriate writing skill) ## Safety Boundaries - Never fabricate paper metadata (title, authors, venue, year, DOI) - Never present preprints as peer-reviewed publications - Never start synthesis before intake questions are answered - Never suppress contradictions or conflicting evidence - Never use Tier 4 sources (blogs, press releases) as primary evidence ## Core Rules 1. Ask the user the four intake questions (see `references/question-flow.md`) before starting any search or synthesis. 2. Keep the skill workflow in English only, even when the requested report language is not English. 3. Prefer recent arXiv plus top IEEE and automation venues over generic web articles. 4. Default to the last 3 years, but keep seminal older work when it is still necessary for context. 5. Cite every substantive claim and separate verified evidence from inference. 6. In survey-draft mode, complete all structure and evidence phases before generating any prose. Structure phases produce YAML/tables only. ## Intake Contract Always start by asking the four intake questions defined in `references/question-flow.md`: 1. Report language (English / Simplified Chinese / Bilingual summary) 2. Deliverable mode (research-brief / literature-map / venue-ranked survey / research-gap memo / survey-draft) 3. Time window (last 12 months / last 3 years / last 5 years / custom) 4. Industrial AI emphasis (predictive maintenance / intelligent scheduling / industrial anomaly detection / smart manufacturing and process optimization / CPS and edge AI / robotics crossover) If the user does not choose, default to `last 3 years` and the subdomain implied by their prompt. ## Required Inputs - A concrete Industrial AI topic or question. - User choices for report language, deliverable mode, time window, and domain emphasis. - Optional preferences on peer-reviewed-only filtering, benchmarks vs deployment evidence, or desired output format. If any intake item is missing, ask the mandatory questions from `references/question-flow.md` before you search. ## Source Strategy Read these files before searching: - `references/source-priority.md` - `references/venue-map.md` Primary sources: - arXiv: `eess.SY`, `cs.AI` - IEEE and automation anchors: `T-ASE`, `CASE` Supporting crossover sources: - arXiv: `cs.RO`, `cs.LG` - IEEE robotics venues: `ICRA`, `IROS`, `RA-L`, `T-RO` - Adjacent industrial and control venues listed in `references/venue-map.md` When the user asks for the latest work, prefer: 1. arXiv recent streams for rapid updates 2. top IEEE and automation venues for stronger publication filtering 3. secondary crossover venues only when they materially improve coverage ## Workflow ### Phase 1. Scope - Rewrite the request as a precise Industrial AI research objective. - Lock the report language, deliverable mode, time window, and domain emphasis. - State explicit in-scope and out-of-scope boundaries. ### Phase 2. Search Plan - Build venue buckets and keyword groups from `references/source-priority.md`. - Separate primary sources from secondary crossover sources. - State the recency policy and any seminal-paper exceptions. ### Phase 3. Source Collection - Gather papers from the prioritized source buckets. - Prefer official venue pages, arXiv recent listings, IEEE Xplore landing pages, and publisher or conference pages. - Record why each paper was included. ### Phase 4. Verification and Triage - Check venue quality, publication type, year, and relevance. - Remove weak matches, duplicates, and generic blog-style sources. - Mark unreviewed preprints as preprints. ### Phase 5. Synthesis - Cluster the shortlisted papers by problem, method, dataset, deployment setting, and evaluation style. - Surface trends, gaps, contradictions, and under-explored opportunities. - Run a contrarian pass: what would challenge the dominant conclusion? ### Phase 6. Report Assembly Use the stable report structure from `references/report-modes.md`. Every final report must include: - search scope - source buckets by venue - shortlisted papers - synthesis of trends and gaps - recommended next reading or next experiments ### Survey-Draft Workflow (Phases S1–S4) When the user selects `survey-draft`, Phases 1–4 (Scope, Search Plan, Source Collection, Verification) execute as normal, then S1–S4 replace the original Phases 5–6. #### Phase S1. Outline Building Read `references/modules/SURVEY_OUTLINE.md`. - Extract a taxonomy from the verified literature. - Build the section skeleton as structured YAML. - Present the outline to the user for approval. - **CHECKPOINT**: do not enter S2 until the user approves the outline. #### Phase S2. Evidence Pack Assembly Read `references/modules/SURVEY_EVIDENCE.md`. - Assemble an evidence pack for every H3 subsection. - Lock the citation scope for each subsection. - Produce structured evidence bundles (no prose). #### Phase S3. Section-by-Section Writing Read `references/modules/SURVEY_WRITER.md`. - Draft each H3 independently, grounded in its evidence pack. - Run the self-check gate on every H3 (depth, citation scope, tone). - Produce one Markdown file per H2 section. #### Phase S4. Merge and Quality Gate Read `references/modules/SURVEY_MERGE.md`. - Merge all section drafts into a single document. - Run cross-section consistency checks. - Apply the final quality checklist. - If the user requested LaTeX output, delegate to `latex-paper-en`. ## Deliverable Modes Read `references/report-modes.md` and follow the selected mode exactly. - `research-brief`: short, decision-ready overview - `literature-map`: thematic map across methods and subproblems - `venue-ranked survey`: grouped by source quality and venue tier - `research-gap memo`: open problems, design space, and next-step opportunities - `survey-draft`: taxonomy-driven survey manuscript with outline-first writing and optional LaTeX export ## Output Contract - State the locked intake choices and any defaults you applied before synthesis. - Distinguish verified evidence from inference in every deliverable. - Label preprints explicitly as preprints. - For non-survey modes, produce a structured report that includes: scope, source buckets, shortlisted papers, synthesis, and next reading or next experiments. - For `survey-draft`, keep stage outputs format-specific: - S1: YAML outline only - S2: evidence packs or tables only - S3: section Markdown drafts grounded in the evidence packs - S4: merged Markdown survey with cross-section consistency notes - If sources are sparse, inaccessible, or off-scope, say so directly and report the exact fallback you used. ## Module Router | Module | Use when | Primary action | Read next | |--------|----------|---------------|-----------| | `research` | User selects any of the 4 report modes | Execute Phase 1–6 workflow | `references/report-modes.md` | | `survey-outline` | User selects survey-draft (Phase S1) | Build taxonomy and section skeleton | `references/modules/SURVEY_OUTLINE.md` | | `survey-evidence` | Outline approved by user (Phase S2) | Assemble per-H3 evidence packs | `references/modules/SURVEY_EVIDENCE.md` | | `survey-write` | Evidence packs complete (Phase S3) | Draft prose per H3 | `references/modules/SURVEY_WRITER.md` | | `survey-merge` | All sections complete (Phase S4) | Merge, quality gate, optional LaTeX handoff | `references/modules/SURVEY_MERGE.md` | ## Quality Bar Read `references/quality-checklist.md` before finalizing. Non-negotiable standards: - no unsupported claims - no venue-blind source mixing - no hiding contradictions - no synthesized report before intake questions are answered - no generic "latest research says" language without source-backed evidence ## Error Handling - **Zero results**: Broaden keywords, relax the time window by one tier, and try adjacent venues. If still empty, report the negative result with the exact queries attempted. - **Off-subdomain topic**: State that the topic falls outside Industrial AI scope, suggest the closest supported subdomain, and ask the user whether to proceed or abort. - **Inaccessible databases**: Note which sources were unreachable, proceed with available sources, and flag the gap in the final report. - **Too few papers (<5 shortlisted)**: Lower the time window threshold, include Tier 2/3 venues, and explicitly note the thin evidence base in the synthesis. ## Reference Map | File | Phase | When to read | |------|-------|-------------| | `references/question-flow.md` | Intake | Before asking the user any questions | | `references/source-priority.md` | Search Plan | Before building venue buckets | | `references/venue-map.md` | Search Plan | Before selecting specific venues | | `references/report-modes.md` | Report Assembly | Before structuring the final output | | `references/quality-checklist.md` | Report Assembly | Before finalizing the report | | `references/modules/SURVEY_OUTLINE.md` | Survey S1 | When building the survey outline | | `references/modules/SURVEY_EVIDENCE.md` | Survey S2 | When assembling evidence packs | | `references/modules/SURVEY_WRITER.md` | Survey S3 | When drafting survey sections | | `references/modules/SURVEY_MERGE.md` | Survey S4 | When merging and running quality gate | | `references/SURVEY_WRITING_GUIDE.md` | Survey S1–S4 | Survey writing philosophy reference | ## Examples - `examples/predictive-maintenance.md` - `examples/intelligent-scheduling.md` - `examples/industrial-anomaly-detection.md` - `examples/survey-predictive-maintenance.md` ## Example Requests - “Research recent predictive maintenance papers from the last 3 years and return a research-brief.” - “Compare industrial anomaly detection papers across arXiv and IEEE automation venues, and show contradictions in evaluation setups.” - “Draft a survey on intelligent scheduling for researchers new to the subfield, but stop after the YAML outline for approval.” - “My topic is warehouse picking robotics. If that is outside scope, tell me the closest supported Industrial AI framing and proceed only with that.” ## Boundaries This v1 skill does not implement: - systematic review mode - meta-analysis - IRB-heavy or clinical ethics branches - standalone automation scripts If the user needs those, state the boundary and continue with the closest supported research mode.
版本历史
-
v2026.07
GitHub ↗
原版更新说明
## Highlights - **First tagged release.** Every gate is green: `make check` (validate + 183 unit tests + eval-harness + numeric benchmarks), validate-catalog, quality-evals, and OpenSSF Scorecard on `main`. - **Rigor double loop at 13 method families.** Each family closes taxonomy tag → eval scenario (does the agent avoid the method's known traps?) → deterministic numeric benchmark (does it recover the true effect?). New this cycle: heterogeneous treatment effects (CATE) and quantile treatment effects (QTE). - **Paper-WorkFlow flagship at 29/29 executable rigor gates**, now merged to its `main` with a drift-gated README badge — the credibility artifact is checked by CI, so it can never silently go stale ([RIGOR.md](https://github.com/brycewang-stanford/Paper-WorkFlow/blob/main/RIGOR.md)). - **1,150 vendored skills / 69 collections**, all license-audited, security-scanned, tracked in a machine-readable catalog with CI-enforced freshness, and importable as a single whole-repo router skill. - **Hardened weekly upstream syncs**: synced trees must pass the full gate before merge; this cycle both sync PRs were verified, patched (StatsPAI's SkillOpt execution-gate card restored), and merged. - **First-party plugin marketplace** (Python / R / Stata empirical-analysis plugins + guide) shipped in the previous cycle, now under a tagged version. ## Known Follow-Ups - Ecosystem benchmark comparison (AERS vs econometrics agents on the shared benchmark suite) — [PLAN-2026-07 week 3](https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/blob/main/docs/PLAN-2026-07.md). - Decomposition (Oaxaca–Blinder) and shift-share (Bartik) method families (weeks 3–4). - GitHub Pages catalog site, README demo screenshots, five-language README consistency script (week 4). ## Catalog - Top-level collections: **69** - `SKILL.md` files: **1150** - Cataloged agent tools: **335** ([`tools/CATALOG.md`](../tools/CATALOG.md)) ## Methodological rigor - Method families in the coverage map: **13** ([`RIGOR_COVERAGE.md`](RIGOR_COVERAGE.md)) - Eval scenarios: **26** (138 rubric items, 122 auto-checkable) ([`../eval-harness/`](../eval-harness/README.md)) - Benchmark tasks: **13** (70 gold checks, 58 required) ([`../benchmark/`](../benchmark/README.md)) ### Method families (skills tagged) - `iv`: 27 - `rdd`: 25 - `panel-fe`: 19 - `staggered-did`: 17 - `bayesian`: 13 - `did`: 10 - `event-study`: 10 - `matching`: 10 - `synthetic-control`: 10 - `cate`: 8 - `dml`: 8 - `survival`: 3 - `quantile`: 2 ### Eval scenarios by category - `causal-identification`: 14 - `citation-hygiene`: 1 - `reproducibility`: 2 - `research-integrity`: 1 - `runtime-safety`: 1 - `statistical-validity`: 2 - `writing-compliance`: 3 - `writing-style`: 2 ## License buckets - AGPL-3.0: 1 - Apache-2.0: 1 - CC-BY-NC-4.0 (non-commercial): 1 - CC-BY-SA-4.0: 1 - CC-BY-SA-4.0 (repository default): 4 - GPL-3.0: 1 - MIT: 35 - MIT Non-Commercial: 1 - Mixed (per-skill; see folder): 2 - UNKNOWN - check upstream: 22 ## Quality gates - `make check` — catalog/provenance/audit/eval freshness, repo hygiene, Paper-WorkFlow gates, stdlib unit tests, eval-harness lint + graded smoke, and the strict numeric benchmark (reference-gold drift fails the build). - External links and OpenSSF Scorecard run on their scheduled workflows.
当前收录版本
0.0.1
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
面向工业人工智能领域的专业文献研究,覆盖预测性维护、智能调度、异常检测等核心工业场景
评分依据
触发词覆盖全面且边界清晰,包含工业 AI 核心术语及相邻概念(如 digital twin, industrial IoT, Industry 4.0)
评分依据
文档结构完整,Phase 划分清晰,包含端到端示例和完整 frontmatter
评分依据
工具来源明确(arXiv, IEEE, WebSearch),参数定义清晰
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。