Menu
Read subjects from an EventSourcingDB instance. Use when the user wants to list, browse, or discover which subjects exist in the event store.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | read-subjects |
| description | Read subjects from an EventSourcingDB instance. Use when the user wants to list, browse, or discover which subjects exist in the event store. |
| allowed-tools | Bash, Read, AskUserQuestion |
List subjects that have received events in an EventSourcingDB instance.
First read ${CLAUDE_PLUGIN_ROOT}/shared/common.md. It explains how to determine the base URL and API token, how to handle NDJSON responses, and which conventions apply. Follow it throughout this skill.
This endpoint returns NDJSON:
curl -s --no-buffer -X POST \
-H "authorization: Bearer ${ESDB_API_TOKEN}" \
-H "content-type: application/json" \
-d '<REQUEST_BODY>' \
"${ESDB_URL:-http://localhost:3000}/api/v1/read-subjects" \
| grep -v '"type":"heartbeat"'
{
"baseSubject": "/"
}
curl -s --no-buffer -X POST \
-H "authorization: Bearer ${ESDB_API_TOKEN}" \
-H "content-type: application/json" \
-d '{"baseSubject": "/"}' \
"${ESDB_URL:-http://localhost:3000}/api/v1/read-subjects" \
| grep -v '"type":"heartbeat"'
NDJSON stream with one line per subject:
{"type":"subject","payload":{"subject":"/books/42"}}
Read details about a single event type from an EventSourcingDB instance. Use when the user wants to inspect a specific event type, check if it has a schema, or see its details.
Read all event types from an EventSourcingDB instance. Use when the user wants to list or discover all event types that exist in the event store.
Register a JSON Schema for an event type on an EventSourcingDB instance. Use when the user wants to add validation, define a schema, or enforce structure for an event type.
Run an EventQL query against an EventSourcingDB instance. Use when the user wants to query, filter, aggregate, or analyze events using the EventQL query language.
Write events to an EventSourcingDB instance. Use when the user wants to store, append, or publish events, optionally with preconditions such as optimistic locking or subject constraints.
Observe events in real time from an EventSourcingDB instance. Use when the user wants to watch, monitor, or stream live events as they are written.