BC 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.
Workflow 1 adaptation for robotics and embodied AI.
As a process C 56/100 · Has gaps — References files that are not bundled: ../shared-references/reviewer-backends.md, ../../shared-references/output-versioning.md, ../../shared-references/output-manifest.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../shared-references/reviewer-backends.md - warning
missing-refreference to a missing file: ../../shared-references/output-versioning.md - warning
missing-refreference to a missing file: ../../shared-references/output-manifest.md - warning
missing-refreference to a missing file: ../../shared-references/output-language.md
Process rating: all ten parameters 56/100
- 0Tools and files. 4 referenced file(s) missing: ../shared-references/reviewer-backends.md, ../../shared-references/output-versioning.md, ../../shared-references/output-manifest.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 85Steps. 100 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3804 tokens
- 100Progress reporting. Reports progress
- low 13 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 452: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 100 items
- +3Output format is stated explicitly
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.