data-access-patterns

Access session JSON via scripts and read Markdown content directly.

4|Updated Jan 8, 2026

Search Tags:#automation #JSON #Markdown #token-efficiency #data-access #session-data #ultrawork

Ready to run

npx skills add https://github.com/mnthe/hardworker-marketplace --skill data-access-patterns

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill helps ultrawork agents access session data efficiently by routing JSON data through scripted queries while reading Markdown content directly, reducing token usage and speeding decision making.

Core Features & Use Cases

Scripted JSON access: Retrieve session.json, context.json, and task data via dedicated scripts to minimize token overhead.
Markdown reads for exploration context: Read exploration notes and docs directly when needed.
Pattern-based access: Provides reusable patterns for checking phase, listing open tasks, and reading task details across session lifecycles.

Quick Start

Run a sample sequence: bun "{SCRIPTS_PATH}/session-get.js" --session ${CLAUDE_SESSION_ID} --field phase bun "{SCRIPTS_PATH}/task-list.js" --session ${CLAUDE_SESSION_ID} --status open bun "{SCRIPTS_PATH}/evidence-query.js" --session ${CLAUDE_SESSION_ID} --type test_result --last 5

Frequently Asked Questions about data-access-patterns

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

FAQPage Schema

How do I reduce token usage when accessing JSON session data in automated workflows?▼

To reduce token usage during JSON session data access, route queries through dedicated scripts to retrieve specific fields, minimizing token overhead and speeding decision making. This pattern enforces scripted queries for JSON formats while reading Markdown content directly.

What is the best way to list open tasks from a session context efficiently?▼

The best way to list open tasks efficiently is using pattern-based access scripts that query task data directly. By executing a task-list script with status parameters, you retrieve targeted task details without loading entire context files into the prompt.

Can I use Markdown reads for exploration context alongside scripted JSON queries?▼

Yes, you can use Markdown reads for exploration context alongside scripted JSON queries. This approach reads exploration notes and docs directly when needed, while routing structured session and task data through specialized scripts to optimize token efficiency.

How do I check the current phase of a session without loading the entire context file?▼

To check the current session phase without loading the entire context file, execute a dedicated session-get script targeting the phase field. This retrieves only the required phase data, drastically cutting token consumption during planning and execution workflows.

Does this data access pattern require specific dependencies to run task listing scripts?▼

No specific dependencies are required to run these data access scripts. The skill operates independently using bundled scripts and references, allowing you to query session, context, and task data directly within your automation environment.

Why should I use specialized scripts instead of direct file reads for context data?▼

You should use specialized scripts instead of direct file reads for context data to enforce token-efficient patterns. Scripted queries extract only necessary fields from JSON structures, preventing token bloat from loading entire files and improving AI prompt efficiency.