lerobot-env-setup

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

• high Tool Misuse · line 68
  Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
  Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
• high Tool Misuse · line 84
  Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
  Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
• medium Rogue Agent · line 3
  Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
  Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
• medium Privilege Escalation · line 77
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 78
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 84
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
• medium Privilege Escalation · line 80
  Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
  Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.