Ultrawork Data Access Patterns FAQs

Question 1

Does this skill work with all Ultrawork agent roles?

Accepted Answer

Yes, these patterns are required knowledge for all agent types in the ecosystem, including explorers, planners, workers, verifiers, and reviewers.

Question 2

When should I use the Read tool instead of a script?

Accepted Answer

The Read tool should be used for Markdown files like exploration docs or plans. JSON files should always be accessed via specialized scripts to maintain efficiency and handle errors.

Question 3

How do these patterns handle error states?

Accepted Answer

The provided scripts offer consistent validation for missing sessions, tasks, or fields, ensuring the agent receives clear error messages instead of trying to parse malformed data.

Question 4

Why use scripts instead of reading JSON files directly?

Accepted Answer

Using scripts allows for precise field-level extraction. This reduces token usage by up to 99.8% compared to reading an entire JSON structure, saving significant context space.

Question 5

What do the {SCRIPTS_PATH} and ${CLAUDE_SESSION_ID} placeholders mean?

Accepted Answer

These are text placeholders provided by your agent prompt that must be substituted with actual file paths and session IDs before executing commands.

Ultrawork Data Access Patterns

Key Features

Use Cases

Ultrawork Data Access Patterns

Key Features

Use Cases