docwriter-data-access

Extracts targeted data from .docwriter JSON databases by domain and outputs JSON to stdout, summaries to stderr.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/skurekjakub/docwriter-agent --skill docwriter-data-access
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docwriter-data-access
Source: https://github.com/skurekjakub/docwriter-agent/tree/main/.github/skills/docwriter-data-access
Command: npx skills add https://github.com/skurekjakub/docwriter-agent --skill docwriter-data-access

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large .docwriter/ JSON databases waste context when loaded in full. Use the query scripts below to retrieve only the matching entries, dramatically reducing context consumption.

Core Features & Use Cases

  • Targeted query scripts that operate on invariant-inventory.json, doc-index.json, task-graph.json, and code-analysis.json.
  • Outputs structured JSON to stdout and summary information to stderr for easy piping
  • Supports single-invariant lookups, domain-filtered lists, cross-reference lookups, and stats-only queries without loading entire files.

Quick Start

Run a targeted query against the relevant .docwriter JSON file to retrieve only the necessary entries.

Frequently Asked Questions about docwriter-data-access

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

FAQPage Schema
How do I query large JSON databases without wasting context window space?

To query large JSON databases without wasting context, use targeted scripts that retrieve only matching entries instead of loading entire files. This approach pulls specific data from large .docwriter JSON files, dramatically reducing context consumption.

What is the best way to filter docwriter JSON data by domain?

The best way to filter docwriter JSON data by domain is using targeted query scripts. They operate on invariant-inventory.json, doc-index.json, task-graph.json, and code-analysis.json to return domain-filtered lists without loading full files.

Can I pipe JSON query outputs while suppressing summary logs?

Yes, you can pipe JSON query outputs safely because the scripts output structured JSON to stdout and summary information to stderr. This enables safe piping with 2>/dev/null to suppress logs while keeping data intact.

How do I retrieve a single invariant from an invariant-inventory.json file?

Retrieve a single invariant from invariant-inventory.json by running a targeted single-invariant lookup query. This fetches only the necessary matching entry, minimizing context load instead of parsing the entire database.

Does this query tool support stats-only queries for code analysis data?

Yes, this query tool supports stats-only queries for code-analysis.json. It retrieves statistics without loading entire files, allowing you to extract analytical data while significantly reducing context consumption.

What are the limitations of using CLI scripts for cross-reference lookups in JSON?

CLI scripts for cross-reference lookups in JSON are limited to operating specifically on invariant-inventory.json, doc-index.json, task-graph.json, and code-analysis.json files, requiring structured .docwriter formats to function correctly.