Node Metadata

This guide explains how to access and manage metadata for nodes within a skill. It is intended for users working on skills who need to understand and adjust node-specific metadata to improve clarity and functionality.

Prerequisites

Familiarity with skills and their components.
A skill with nodes that have run at least once.

Accessing Node Metadata

Select the Desired Node:
- Click on the node you wish to inspect.
- Metadata options will appear on the right-hand side as icons.

Metadata Properties Overview

1. Source Code Icon

Appearance: Code with a box around it.
Function: Displays the source code that ran when the skill executed this node.
Actions:
- Click the icon to reveal the source code.
- Use the "Copy" action to copy the code to clipboard.
Note: Source code is only displayed if the skill has run.

2. Node Notes

Function: View or add notes describing the node's purpose and functionality.
Actions:
- Click the "View Node Notes" icon to display or collapse the notes section.
- Notes remain expanded when navigating between nodes, ensuring continuity.
Best Practice: Use notes to explain the node's intent, making the skill easier to understand for collaborators.

3. Node Name

Location: Top-left corner of the node, next to the activation toggle.
Default Name: Matches the name of the component it originated from.
Editing Rules:
- Use only lowercase letters, numbers, and underscores.
- Avoid starting names with a number or using symbols (except underscores).
Difference from Component Name:
- Node names are editable; component names (visible in the right-hand corner) are not.

Additional Notes or Best Practices

Ensure all nodes have meaningful names and notes to simplify future edits and collaborations.
Follow naming conventions strictly to avoid errors or conflicts during execution.

Conclusion

By understanding and managing node metadata—source code, notes, and names—you can create more transparent and functional skills. Use the available metadata properties to document and clarify each node's role, ensuring efficient collaboration and troubleshooting.