javascript-runtime

JavaScript Runtime

Use this skill when the task is better solved by executing short, deterministic JavaScript inside OpenAva's built-in JavaScript runtime instead of reasoning everything manually. You can either pass inline code directly or run a single workspace script through script_path, and both entry modes share the same minimal CommonJS shape with require, module.exports, exports, __filename, __dirname, and a minimal process. When later steps need to keep variables, helper functions, or intermediate state, reuse the same session_id.

Typical fits:

• JSON reshaping, filtering, grouping, sorting, aggregation
• String parsing, normalization, templating, and report generation
• Small deterministic calculations with multiple intermediate steps
• Calling one or more read-only tools from JavaScript and combining the results
• Running a small reusable workspace script file without introducing a separate sub-agent
• Producing stable structured output that should be derived from code, not guesswork

Avoid using this skill when:

• A direct tool call already solves the task cleanly
• The transformation is trivial enough to do in plain reasoning
• The task needs browser DOM APIs or a web page context
• The task requires complex, long-running, open-ended state management better handled by a dedicated sub-agent or another mechanism

Runtime Model

The javascript_execute tool runs code inside Apple system JavaScriptCore.

Important runtime rules:

• Provide exactly one of code or script_path
• script_path must point to a single file inside the active workspace
• Your code is executed as the body of an async function
• Use return for the final result
• You may use await
• Input data is exposed as openava.input
• You may provide session_id to reuse the same persistent JavaScript context
• Shared cross-call state is available through openava.session
• Tool calls are available through await openava.tools.call(functionName, args)
• console.log/info/warn/error are captured and returned in the tool result
• code and script_path share the same minimal CommonJS surface: require, module.exports, exports, __filename, __dirname
• Both entry modes also expose a minimal process object with argv, cwd(), env, platform, and versions
• A built-in path module is available through require("path") or require("node:path")
• When using inline code, relative require() resolves from the active workspace root
• Do not assume ESM import, package resolution, built-in Node modules, timers, Buffer, child_process, or other Node standard libraries are available