ros2-engineering-skills
Reduces ROS 2 onboarding time and deployment errors by providing structured guidance on production concerns—QoS tuning, real-time constraints, and control st…
Agent skill for production-grade ROS 2 development. Progressive-disclosure SKILL.md covering workspace, nodes, executors, QoS, ros2_control, Nav2, MoveIt 2, real-time, and deployment. Works with Claude Code, Codex, Cursor, Gemini CLI.
- Ask Claude to generate a ROS 2 workspace configuration for a multi-node robotics application.
- Generate production-ready QoS settings and executor patterns for real-time robot control systems.
- Find best practices for deploying Nav2 and MoveIt 2 stacks in manufacturing environments.
Reduces ROS 2 onboarding time and deployment errors by providing structured guidance on production concerns—QoS tuning, real-time constraints, and control stack integration—that informal docs often skip.
Robotics engineering teams building autonomous systems or industrial robots using ROS 2 in resource-constrained or safety-critical environments.
https://github.com/dbwls99706/ros2-engineering-skills
By dbwls99706
How to Get It
claude plugins install dbwls99706/ros2-engineering-skills
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Generate a ROS 2 workspace configuration for a multi-node robotics application
Trust Signals Auto-scanned
Community Pulse Quiet
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 198 GitHub stars; contributors unknown; last commit 0d ago; license Apache-2.0.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 198 GitHub stars; contributors unknown; last commit 0d ago; license Apache-2.0.