nav2-params-structure

Organize ROS 2 Nav2 parameter files with double-namespace YAML patterns.

18|2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/wimblerobotics/ros2-copilot-skills --skill nav2-params-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nav2-params-structure
Source: https://github.com/wimblerobotics/ros2-copilot-skills/tree/main/nav2-params-structure
Command: npx skills add https://github.com/wimblerobotics/ros2-copilot-skills --skill nav2-params-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structure Nav2 YAML parameter files to organize navigation.yaml, understand the double-namespace pattern, and set ROS 2 parameters across nodes.

Core Features & Use Cases

  • Clarifies the double-namespace parameter pattern used by Nav2 nodes.
  • Demonstrates how to organize top-level and nested ros__parameters for multiple nodes (controller_server, planner_server, costmaps, etc.).
  • Shows best practices for having consistent parameter declarations, overrides, and YAML formatting that loads correctly in ROS 2.

Quick Start

Organize your Nav2 YAML parameters across nodes by applying the double-namespace pattern and mapping parameters to the appropriate Nav2 components.

Frequently Asked Questions about nav2-params-structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure Nav2 parameters in a ROS 2 YAML file?

Structure Nav2 parameters in a ROS 2 YAML file by declaring ros__parameters under top-level node names and using nested YAML mappings for component-specific configurations like controllers and costmaps.

What is the double-namespace pattern in Nav2 configuration?

The double-namespace pattern in Nav2 configuration maps parameters to specific servers and their internal plugins, ensuring global and local parameter propagation loads correctly across multiple Nav2 nodes.

How do I set ros__parameters for multiple Nav2 nodes like planner_server and controller_server?

Set ros__parameters for multiple Nav2 nodes by creating top-level YAML keys for each node, such as planner_server and controller_server, then nesting their specific parameters and plugin namespaces underneath.

Why are my Nav2 YAML parameter overrides not loading correctly in ROS 2?

Nav2 YAML parameter overrides fail to load correctly in ROS 2 when the YAML formatting lacks proper ros__parameters declarations or misconfigures the nested double-namespace structure required by Nav2 nodes.

Can I organize costmap parameters across different Nav2 nodes using one YAML file?

Yes, you can organize costmap parameters across different Nav2 nodes using one YAML file by correctly applying the double-namespace pattern and nested ros__parameters structure for each node.