robotics-agent-skills MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

ROS1 and ROS2 coverage, including launch files and package.xml
SOLID principles applied to robotics code
Common design patterns (State, Observer, Strategy) in ROS context
Testing scaffolds: pytest, rostest, gtest
Node lifecycle patterns (managed/unmanaged)
Cross-agent: works with any SKILL.md-compatible assistant

Démo en direct

Aperçu en pratique

robotics-agent-skill.replay ▶ prêt

0/0

Installer

Choisissez votre client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "robotics-agent-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/arpitg1304/robotics-agent-skills",
        "~/.claude/skills/robotics-agent-skills"
      ],
      "_inferred": true
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "robotics-agent-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/arpitg1304/robotics-agent-skills",
        "~/.claude/skills/robotics-agent-skills"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "robotics-agent-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/arpitg1304/robotics-agent-skills",
        "~/.claude/skills/robotics-agent-skills"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "robotics-agent-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/arpitg1304/robotics-agent-skills",
        "~/.claude/skills/robotics-agent-skills"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "robotics-agent-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/arpitg1304/robotics-agent-skills",
        "~/.claude/skills/robotics-agent-skills"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

{
  "context_servers": {
    "robotics-agent-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/arpitg1304/robotics-agent-skills",
          "~/.claude/skills/robotics-agent-skills"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add robotics-agent-skill -- git clone https://github.com/arpitg1304/robotics-agent-skills ~/.claude/skills/robotics-agent-skills

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : robotics-agent-skills

How to generate a production-ready ROS2 node from a spec

👤 Robotics engineers and students avoiding toy-example code ⏱ ~45 min intermediate

Quand l'utiliser : You're about to write a new node and want clean lifecycle + tests from the start.

Prérequis

Skill installed — git clone https://github.com/arpitg1304/robotics-agent-skills ~/.claude/skills/robotics-agent-skills
ROS2 Humble+ on PATH — Follow docs.ros.org install

Déroulement

Describe the node

Create a ROS2 Humble node that subscribes to /scan (LaserScan), filters obstacles, and publishes /cmd_vel using a state machine.✓ Copié

→ Node with clear class separation, lifecycle hooks, param declarations
Ask for tests

Write pytest unit tests for the filter logic and a launch_test for the integration.✓ Copié

→ Tests runnable via colcon test
Package

Produce package.xml and CMakeLists.txt with correct dependencies.✓ Copié

→ colcon build succeeds

Résultat : A ROS2 package that passes colcon build + test with meaningful coverage.

Pièges

Claude mixes ROS1 and ROS2 APIs — State version explicitly in the prompt every time — 'ROS2 Humble'
Node lacks shutdown handling — Ask for on_shutdown hooks and SIGTERM cleanup specifically

Migrate a ROS1 package to ROS2

👤 Teams on end-of-life ROS1 Noetic ⏱ ~120 min advanced

Quand l'utiliser : You need to port a working ROS1 package and want more than a mechanical search-replace.

Déroulement

Audit the ROS1 package

Read this package and list every API we need to remap for ROS2 (params, timers, services, actions).✓ Copié

→ Per-file remap table
Generate ROS2 equivalents

Produce the ROS2 versions of each file, preserving behavior. Flag anything without a 1:1 mapping.✓ Copié

→ New files + flagged items for human review

Résultat : A ROS2 branch of the package that compiles and passes smoke tests.

Pièges

callback_groups and executors missing — Ask Claude to add a MultiThreadedExecutor and assign callback groups based on the old threading model

Add tests to a legacy ROS node without rewriting it

👤 Engineers inheriting an untested node ⏱ ~60 min intermediate

Quand l'utiliser : The node works in the field and you want a safety net before refactoring.

Déroulement

Identify seams

Look at this node and find the seams where we could inject fakes without changing production behavior.✓ Copié

→ Specific lines/functions to seam
Generate tests at seams

Write pytest tests using those seams. Don't change the node.✓ Copié

→ Tests that run in isolation and pass

Résultat : A characterization test suite that catches regressions.

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

robotics-agent-skill + claude-code-owasp-skill

Security-review ROS networking (rosbridge, Zenoh) using OWASP guidance

Robotics skill produced a rosbridge integration — run OWASP skill against the WebSocket layer.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler
ROS2 node generation	-	New node from scratch
ROS1-to-ROS2 migration	-	Noetic → Humble/Jazzy
Launch file authoring	-	Multi-node orchestration
Test scaffolds	-	Coverage work
SOLID + design patterns	-	Code review and refactor

Coût et limites

Coût d'exécution

Quota d'API: None
Tokens par appel: Varies
Monétaire: Free
Astuce: Keep prompts focused on one node at a time; full-package generation balloons tokens fast.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials

Sortie de données : No outbound calls from the skill itself

Robotics code can move physical hardware. Always run Claude-generated nodes in sim first.

Dépannage

Erreurs courantes et correctifs

Generated package fails colcon build with include errors

Claude often forgets to add ament_target_dependencies. Ask to regenerate CMakeLists.txt explicitly.

Vérifier : colcon build --packages-select <pkg>

Tests pass in isolation, fail when run together

Shared ROS context. Ask for per-test rclpy.init() and shutdown().

Vérifier : colcon test

Alternatives

robotics-agent-skills vs autres

Alternative	Quand l'utiliser	Compromis
ROS2 official docs	You want canonical patterns not LLM-derived	No codegen, slower

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills