Tool Library: Package and Reuse Your Automation Scripts
The Copy-Paste Problem
A Python script that cleans CSV files gets used in six different workflows. Each workflow has its own copy of the node configuration — script path, arguments, working directory, language setting. When the script changes, all six nodes need manual updates. Miss one, and that workflow silently runs the old version.
This is the copy-paste problem in workflow automation. The script itself is reusable, but the node configuration isn’t. Every workflow carries its own copy of the setup, and keeping them in sync is manual work that scales poorly.
NORA’s Tool Library solves this by packaging scripts as versioned, reusable tools that any workflow can reference.
How the Tool Library Works
Tools are stored locally at ~/.nora/tools/<toolId>/<version>/. Each tool is a self-contained package: the script, its configuration, and metadata about where it came from. Tools are versioned, so multiple versions can coexist without conflict.
Three Ways to Install a Tool
From a folder — Point NORA at a directory containing a script. NORA packages the contents into a tool with a version number.
From a selected node on the canvas — Right-click any configured node and save it as a tool. The node’s script, language, arguments, and working directory are all captured. This is the fastest path: configure a node once, package it, and reuse it everywhere.
From the library — Browse existing tools in the library and install them into the current workflow. The tool appears as a node on the canvas, pre-configured and ready to run.
Access the Tool Library at any time with Ctrl+Shift+L.
Version Management
Each tool supports multiple versions stored side by side. Install version 1.0 of a cleanup script in one workflow and version 2.0 in another — both coexist without interference.
Individual versions can be deleted without affecting other versions of the same tool. When a tool version is no longer needed, remove it from the library and any nodes still referencing it will flag the missing version.
Provenance Tracking
Every tool version records where it came from:
- createdAt — timestamp of when the tool version was created
- createdFrom — how it was created (from folder, from node, etc.)
- originalSourcePath — the filesystem path of the original script
This provenance trail answers the question “where did this tool come from?” months after it was packaged. No more mystery scripts with unclear origins living in a shared tools folder.
Sync Status and Sync from Source
NORA tracks whether a tool is still in sync with its original source file. If the original script has been modified since the tool was packaged, NORA flags the tool as out of sync.
Sync from source pulls the latest version of the original script back into the tool, creating a new version. This gives a clean upgrade path: the original script evolves in its own repo or directory, and the tool library stays current with a single click.
Bulk Update Across Workflows
When a tool is updated, NORA offers a “Update N nodes” action that propagates the change to every canvas node using that tool. Instead of hunting through six workflows to update six nodes manually, one action brings them all to the latest version.
This alone eliminates the most common source of stale configurations in multi-workflow setups.
Tool Discovery for Custom Script Agent
NORA’s Custom Script Agent — an AI-powered node that writes and runs scripts autonomously — can discover and use tools from the library at runtime.
The discovery system uses:
- Fuzzy search (Levenshtein distance) — finds tools even with approximate naming
- Partial matching — partial tool names or descriptions return relevant results
- Lazy resolution — tools are loaded only when the agent actually needs them, keeping memory usage low
- Session caching — tool lookups are cached within an execution session for speed
This means an AI agent node can search the library for “csv cleanup” and find the right tool without knowing its exact ID or version. The agent uses the tool’s configuration to run it correctly, including arguments and working directory.
What This Looks Like in Practice
- Write a Python script that validates JSON files against a schema
- Configure it as a node in one workflow — set the script path, arguments, language
- Right-click the node → Save as Tool → version 1.0
- In three other workflows, install the tool from the library → pre-configured nodes appear
- Later, update the original script to handle a new schema format
- Open the Tool Library → sync from source → version 1.1 created
- Click “Update 3 nodes” → all workflows now use version 1.1
No manual reconfiguration. No copy-paste. No stale versions.
Getting Started
NORA runs on Windows 10 and later. Download it from software.reibuys.com/nora and install. A paid license key is required — one-time purchase, no subscription, no recurring fees. 30-day money-back guarantee.