メニュー
This skill provides guidance for ultrawork agents on using SCRIPTS_PATH and accessing session data via scripts. Required knowledge for all ultrawork agents (explorer, planner, worker, verifier, reviewer, scope-analyzer).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Event-driven coordination for teamwork orchestrators. Replaces polling-based monitoring loop with TeammateIdle and TaskCompleted hooks.
Hybrid task decomposition strategy for teamwork projects. Covers plan-based and semantic decomposition, granularity rules, role assignment, dependency management, and complexity assessment.
Reset and clean up teamwork project state. Use when project is stuck, failed, or needs a fresh start. Uses native TeamDelete API for cleanup.
8-phase task execution lifecycle for teamwork workers using native Claude Code APIs. Covers task discovery, claiming, structured description parsing, TDD workflow, implementation, verification, selective commit, and completion reporting.
Architecture design review skill for reviewer agents. Component boundaries, separation of concerns, modularity, and design pattern validation. Use during PLANNING phase to validate design decisions and VERIFICATION to ensure adherence.
API design, database operations, error handling, and backend architecture patterns. Use when creating APIs, database schemas, or server-side logic.
| name | scripts-path-usage |
| description | This skill provides guidance for ultrawork agents on using SCRIPTS_PATH and accessing session data via scripts. Required knowledge for all ultrawork agents (explorer, planner, worker, verifier, reviewer, scope-analyzer). |
| user-invocable | false |
SCRIPTS_PATH is the expanded absolute path of ${CLAUDE_PLUGIN_ROOT}/src/scripts.
Your prompt includes it like this:
SCRIPTS_PATH: /Users/name/.claude/plugins/cache/ultrawork/0.25.0/src/scripts
Use this path to call Bun scripts.
CRITICAL: {SCRIPTS_PATH} and ${CLAUDE_SESSION_ID} are TEXT PLACEHOLDERS, not bash environment variables!
These placeholders appear in this documentation to show WHERE to substitute values. You MUST replace them with actual values from your prompt before running commands.
Your prompt provides actual values:
SCRIPTS_PATH: /Users/mnthe/.claude/plugins/cache/hardworker-marketplace/ultrawork/0.26.1/src/scripts
CLAUDE_SESSION_ID: 76dfec2a-4187-48eb-8073-9435f4386466
Use the literal values in bash commands:
✅ CORRECT:
bun "/Users/mnthe/.claude/plugins/cache/hardworker-marketplace/ultrawork/0.26.1/src/scripts/session-get.js" --session 76dfec2a-4187-48eb-8073-9435f4386466
❌ WRONG - Don't use placeholder syntax in actual commands:
# This will NOT work - {SCRIPTS_PATH} is not a bash variable!
bun "{SCRIPTS_PATH}/session-get.js" --session ${CLAUDE_SESSION_ID}
❌ WRONG - These are not shell environment variables:
# These variables don't exist in the shell environment
echo $SCRIPTS_PATH # Empty or undefined
echo $CLAUDE_SESSION_ID # Empty or undefined
{SCRIPTS_PATH}) = documentation convention showing "substitute here"$SCRIPTS_PATH) = shell environment variable (NOT available to agents)When you see {SCRIPTS_PATH} in this documentation → Replace with the actual path from your prompt
session-get.js, task-get.js for JSON access--field for efficiency - session-get.js --field phase returns only what you need| Data | Access Method |
|---|---|
| session.json | bun "{SCRIPTS_PATH}/session-get.js" --session $${CLAUDE_SESSION_ID} |
| tasks/*.json | bun "{SCRIPTS_PATH}/task-get.js" --session $${CLAUDE_SESSION_ID} --id 1 |
| exploration/*.md | Read("~/.claude/ultrawork/sessions/$${CLAUDE_SESSION_ID}/exploration/overview.md") |