robotics-autonomous-systems-engineering
v0.1.1Robotics & autonomous-systems engineering team — agents (robotics-architect-lead, ros-motion-planning-engineer, perception-and-autonomy-engineer) across the three engines of a robot program: system architecture (ROS 2 computation graph & DDS, compute/sensor selection, the real-time vs non-real-time split, safety architecture, sim-to-real), the motion stack (ROS 2 nodes/topics/actions, MoveIt/Nav2 planning, kinematics, PID/MPC control, coordinate frames/TF), and perception & autonomy (sensor fusion, SLAM, EKF state estimation, localization, behavior-tree/state-machine autonomy). Ships skills, a decision-tree knowledge bank (Mermaid trees + a dated 2026 reference), best-practices, templates, commands. Engineering decision-support, not functional-safety certification advice: safety-standard pointers (ISO 10218/13849), DDS/distro landscape, and sensor/compute specifics carry a retrieval date + verify-at-use; no PII. Requires ravenclaude-core@>=0.7.0.
By Matt CorbettLicense: MIT7 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 4 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install robotics-autonomous-systems-engineering for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install robotics-autonomous-systems-engineering@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mcorbett51090/RavenClaudeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/robotics-autonomous-systems-engineering/.
Plugin files
├── .claude-plugin/plugin.json├── skills/motion-planning-and-control/SKILL.md├── skills/perception-and-state-estimation/SKILL.md├── skills/ros2-architecture-and-dds/SKILL.md└── skills/sim-to-real-and-safety/SKILL.md
Included Skills4
Build the motion stack: Nav2 for mobile-base navigation vs MoveIt for manipulator planning, kinematics and the TF tree (REP 105), trajectory generation inside velocity/acceleration/jerk limits, ROS 2 actions for long-running motion, and control loops (PID vs MPC). Trust the frames before the planner. Safety-bearing limits are verify-at-use.
Build the perception stack: sensor fusion of complementary modalities (lidar/camera/IMU/odometry/GPS), SLAM vs known-map localization, EKF/UKF/particle-filter state estimation, object detection with propagated uncertainty, and behavior-tree / state-machine autonomy that fails safe. Time sync and frames come before the fusion math. Benchmark accuracy is verify-at-use.
Design the ROS 2 computation graph: nodes and their boundaries, topics/services/actions, the RMW/DDS layer and per-topic QoS, executors & callback groups, node composition, and the real-time vs non-real-time split. QoS and the real-time boundary are architecture decisions, not runtime flags. Distro/DDS specifics are verify-at-use.
Cross the sim-to-real gap and build the safety architecture: simulate every behavior before actuating, measure and close the reality gap (dynamics, sensor noise, latency, domain randomization), and make safety a system property — monitored safe state, bounded actuation, degraded modes, and a risk assessment. Functional-safety standard pointers (ISO 10218 / ISO 13849 / ISO 12100) are verify-at-use.
Plugin manifests1
{
"name": "robotics-autonomous-systems-engineering",
"version": "0.1.1",
"description": "Robotics & autonomous-systems engineering team — agents (robotics-architect-lead, ros-motion-planning-engineer, perception-and-autonomy-engineer) across the three engines of a robot program: system architecture (ROS 2 computation graph & DDS, compute/sensor selection, the real-time vs non-real-time split, safety architecture, sim-to-real), the motion stack (ROS 2 nodes/topics/actions, MoveIt/Nav2 planning, kinematics, PID/MPC control, coordinate frames/TF), and perception & autonomy (sensor fusion, SLAM, EKF state estimation, localization, behavior-tree/state-machine autonomy). Ships skills, a decision-tree knowledge bank (Mermaid trees + a dated 2026 reference), best-practices, templates, commands. Engineering decision-support, not functional-safety certification advice: safety-standard pointers (ISO 10218/13849), DDS/distro landscape, and sensor/compute specifics carry a retrieval date + verify-at-use; no PII. Requires ravenclaude-core@>=0.7.0.",
"author": {
"name": "Matt Corbett"
},
"homepage": "https://github.com/mcorbett51090/RavenClaude",
"license": "MIT",
"keywords": [
"robotics",
"ros2",
"autonomous-systems",
"motion-planning",
"nav2",
"moveit",
"perception",
"slam",
"sensor-fusion",
"state-estimation",
"dds",
"real-time",
"sim-to-real",
"functional-safety",
"behavior-trees"
],
"requires": {
"plugins": [
"ravenclaude-core@>=0.7.0"
]
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[robotics-autonomous-systems-engineering on Agent Plugins Marketplace](https://pluginsmp.com/plugins/robotics-autonomous-systems-engineering)