跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
硬件与物联网

idea-discovery-robot

Workflow 1 adaptation for robotics and embodied AI. Orchestrates robotics-aware literature survey, idea generation, novelty check, and critical review to go from a broad robotics direction to benchmark-grounded, simulation-first ideas. Use when user says \"robotics idea discovery\", \"机器人找idea\", \"embodied AI idea\", \"机器人方向探索\", \"sim2real 选题\", or wants ideas for manipulation, locomotion, navigation, drones, humanoids, or general robot learning.

wanshuiyin · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill idea-discovery-robot

技能说明


name: idea-discovery-robot description: "Workflow 1 adaptation for robotics and embodied AI. Orchestrates robotics-aware literature survey, idea generation, novelty check, and critical review to go from a broad robotics direction to benchmark-grounded, simulation-first ideas. Use when user says "robotics idea discovery", "机器人找idea", "embodied AI idea", "机器人方向探索", "sim2real 选题", or wants ideas for manipulation, locomotion, navigation, drones, humanoids, or general robot learning." argument-hint: "[robotics-direction]" allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, Skill, mcp__codex__codex, mcp__codex__codex-reply

Robotics Idea Discovery Pipeline

Orchestrate a robotics-specific idea discovery workflow for: $ARGUMENTS

Overview

This skill chains four sub-skills into a single automated pipeline:

/research-lit → /idea-creator (robotics framing) → /novelty-check → /research-review
  (survey)              (filter + pilot plan)         (verify novel)    (critical feedback)

But every phase must be grounded in robotics-specific constraints:

  • Embodiment: arm, mobile manipulator, drone, humanoid, quadruped, autonomous car, etc.
  • Task family: grasping, insertion, locomotion, navigation, manipulation, rearrangement, multi-step planning
  • Observation + action interface: RGB/RGB-D/tactile/language; torque/velocity/waypoints/end-effector actions
  • Simulator / benchmark availability: simulation-first by default
  • Real robot constraints: hardware availability, reset cost, safety, operator time
  • Evaluation quality: success rate plus failure cases, safety violations, intervention count, latency, sample efficiency
  • Sim2real story: whether the idea can stay in sim, needs offline logs, or truly requires hardware

The goal is not to produce flashy demos. The goal is to produce ideas that are:

  • benchmarkable
  • falsifiable
  • feasible with available robotics infrastructure
  • interesting even if the answer is negative

Constants

  • MAX_PILOT_IDEAS = 3 — Validate at most 3 top ideas deeply
  • PILOT_MODE = sim-first — Prefer simulation or offline-log pilots before any hardware execution
  • REAL_ROBOT_PILOTS = explicit approval only — Never assume physical robot access or approval
  • AUTO_PROCEED = true — If user does not respond at checkpoints, proceed with the best sim-first option
  • REVIEWER_MODEL = gpt-6-astra — External reviewer model via Codex MCP
  • TARGET_VENUES = CoRL, RSS, ICRA, IROS, RA-L — Default novelty and reviewer framing

Override inline, e.g. /idea-discovery-robot "bimanual manipulation" — only sim ideas, no real robot or /idea-discovery-robot "drone navigation" — focus on CoRL/RSS, 2 pilot ideas max

Execution Rule

Follow the phases in order. Do not stop after a checkpoint unless:

  • the user explicitly says to stop, or
  • the user asks to change scope and re-run an earlier phase

If AUTO_PROCEED=true and the user does not respond, continue immediately to the next phase using the strongest sim-first, benchmark-grounded option.

Phase 0: Frame the Robotics Problem

Before generating ideas, extract or infer this Robotics Problem Frame from $ARGUMENTS and local project context:

  • Embodiment
  • Task family
  • Environment type: tabletop, warehouse, home, outdoor, aerial, driving, legged terrain
  • Observation modalities
  • Action interface / controller abstraction
  • Learning regime: RL, imitation, behavior cloning, world model, planning, VLA/VLM, classical robotics, hybrid
  • Available assets: simulator, benchmark suite, teleop data, offline logs, existing codebase, real hardware
  • Compute budget
  • Safety constraints
  • Desired contribution type: method, benchmark, diagnosis, systems, sim2real, data curation

If some fields are missing, make explicit assumptions and default to:

  • simulation-first
  • public benchmark preferred
  • no real robot execution

Write this frame into working notes before moving on. Every later decision should reference it.

Phase 1: Robotics Literature Survey

Invoke:

/research-lit "$ARGUMENTS — focus venues: CoRL, RSS, ICRA, IROS, RA-L, TRO, Science Robotics"

Then reorganize the findings using a robotics lens instead of a generic ML lens.

Build a Robotics Landscape Matrix

For each relevant paper, classify:

AxisExamples
Embodimentsingle-arm, mobile manipulator, humanoid, drone, quadruped
Taskpick-place, insertion, navigation, locomotion, long-horizon rearrangement
Learning setupRL, BC, IL, offline RL, world model, planning, diffusion policy
ObservationRGB, RGB-D, proprioception, tactile, language
Action abstractiontorque, joint velocity, end-effector delta pose, waypoint planner
Eval regimepure sim, sim+real, real-only, offline benchmark
BenchmarkManiSkill, RLBench, Isaac Lab, Habitat, Meta-World, CALVIN, LIBERO, custom
Metricssuccess rate, collision rate, intervention count, path length, latency, energy
Main bottlenecksample inefficiency, brittleness, reset cost, perception drift, sim2real gap

Search Priorities

When refining the survey, prioritize:

  • recent work from CoRL, RSS, ICRA, IROS, RA-L
  • recent arXiv papers from the last 6-12 months
  • benchmark papers and follow-up reproductions
  • negative-result or diagnosis papers if they reveal system bottlenecks

What to Look For

Do not stop at "who got the best success rate." Explicitly identify:

  • recurring failure modes papers do not fix
  • benchmarks that are saturated or misleading
  • places where embodiment changes invalidate prior conclusions
  • methods that only work with privileged observations
  • ideas whose reported gains come from reset engineering, reward shaping, or hidden infrastructure
  • task families where evaluation quality is weak even if performance numbers look high

Checkpoint: Present the

阅读完整来源 ↗