AD rdk-x5-tros
使用 RDK X5 上的 TogetheROS.Bot (tros.b) Humble 框架：启动 43 个预装 ROS2 算法包、管理 ROS2 话题/节点/服务、构建摄像头+AI+输出（Web/语音/HDMI）集成 pipeline、创建自定义 ROS2 工作空间。Use when the user mentions ROS2, TROS, ros2 launch, topic/node/service, or wants to build an integrated multi-component pipeline combining camera + AI + any output (集成/pipeline/全链路). Also use when user combines camera + AI + display/audio in one request. Do NOT use for camera-only hardware setup (use rdk-x5-camera), /app demo scripts (use rdk-x5-app), standalone AI inference without ROS2 (use rdk-x5-ai-detect), GPIO/I2C hardware (use rdk-x5-gpio), or system management (use rdk-x5-system).
As a process D 41/100 · Unfinished process — weak spots: steps, result and completion, inputs and preconditions
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 41/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 754 tokens
- 100Running it twice. No mutating operations
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
- +5Description has no quoted example phrases that should trigger the skill
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 628: enough signal without eating the budget
- +4Structure: 18 headings
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.