node-inspector

Render input widgets and edit node parameters in a properties panel.

1|Updated Jul 9, 2025
One-click install
npx skills add https://github.com/ultrafish22L/grpcSamples --skill node-inspector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspector
Source: https://github.com/ultrafish22L/grpcSamples/tree/main/octaneWebR/.openhands/skills/node-inspector
Command: npx skills add https://github.com/ultrafish22L/grpcSamples --skill node-inspector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NodeInspector provides a dedicated UI for viewing and editing node parameters via the properties panel, simplifying complex parameter editing and node-type interactions.

Core Features & Use Cases

  • Architecture overview of the NodeInspector component and its integration with the properties panel.
  • Node type dropdown support and parameter editing patterns for common node types.
  • How to extend the inspector with new features and actions.

Quick Start

Demonstrate NodeInspector on the currently selected node to edit its parameters and, when applicable, expose a node type dropdown.

Frequently Asked Questions about node-inspector

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

FAQPage Schema
How do I edit node parameters in a graph editor properties panel?

To edit node parameters in a properties panel, use a dedicated NodeInspector UI that renders appropriate input widgets for numbers, booleans, enums, and colors while handling optimistic updates.

How does a node inspector handle changing node types via a dropdown?

Changing node types via a dropdown triggers a node replacement event that preserves UI state, ensuring the properties panel continuously renders the correct input widgets for the newly selected node type.

What is the best way to build a UI for viewing and modifying graph editor node properties?

The best way to build a UI for viewing and modifying graph editor node properties is integrating a dedicated inspector component that exposes parameter editing patterns and handles optimistic updates for common node types.

Can I extend the node inspector component with new actions for the properties panel?

Yes, you can extend the node inspector component with new features and actions, allowing developers to add customized input widgets and parameter editing behaviors to the properties panel.

Why does the properties panel need to react to node replacement events?

The properties panel must react to node replacement events to preserve UI state when a node type changes via a dropdown, ensuring the displayed parameters update correctly without losing context.