scripts-path-usage

Invoke Bun scripts via SCRIPTS_PATH to access session data.

4|Updated Jan 8, 2026

Search Tags:#Bun #workflows #script-execution #session-get #SCRIPTS_PATH #ultrawork

Ready to run

npx skills add https://github.com/mnthe/hardworker-marketplace --skill scripts-path-usage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scripts-path-usage
Source: https://github.com/mnthe/hardworker-marketplace/tree/main/plugins/ultrawork/skills/scripts-path-usage
Command: npx skills add https://github.com/mnthe/hardworker-marketplace --skill scripts-path-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides guidance for ultrawork agents on using SCRIPTS_PATH and accessing session data via scripts. This ensures deterministic script execution across session workflows.

Core Features & Use Cases

SCRIPTS_PATH guidance: Defines the absolute path to the src/scripts folder enabling agents to invoke Bun scripts during tasks.
Placeholder handling: clarifies how to substitute the {SCRIPTS_PATH} placeholder vs shell variables to avoid errors.
Practical examples: demonstrates calling session-get.js and task-get.js with a valid session ID in typical ultrawork sessions.

Quick Start

Run a Bun script from the SCRIPTS_PATH to access session data. Example: bun "<SCRIPTS_PATH>/session-get.js" --session <CLAUDE_SESSION_ID>

Frequently Asked Questions about scripts-path-usage

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

FAQPage Schema

How do I execute Bun scripts from a custom path in ultrawork session workflows?▼

To execute Bun scripts from a custom path, substitute the {SCRIPTS_PATH} placeholder with the absolute path to your src/scripts folder, then invoke the script using a valid CLAUDE_SESSION_ID.

What is the SCRIPTS_PATH placeholder used for in Bun-based session workflows?▼

The SCRIPTS_PATH placeholder defines the absolute path to the src/scripts folder, enabling ultrawork agents to deterministically locate and invoke Bun scripts to access session data.

Why does my session-get.js script fail when using shell variables instead of the actual path?▼

Your session-get.js script fails because you must substitute the {SCRIPTS_PATH} placeholder with the actual absolute path rather than relying on shell variables, ensuring deterministic script execution.

Do I need a valid session ID to run Bun scripts for ultrawork tasks?▼

Yes, you need a valid CLAUDE_SESSION_ID to run Bun scripts like session-get.js. This ID allows explorer, planner, and worker agents to correctly access and retrieve session data.

Can I use SCRIPTS_PATH to run scripts across different ultrawork agent roles?▼

Yes, SCRIPTS_PATH enables deterministic script execution across all ultrawork roles including explorer, planner, worker, verifier, reviewer, and scope-analyzer by providing a consistent absolute path.