allsource-debug
Skill4 starsChanged yesterdayApache-2.0View on GitHub
Debug AllSource-backed applications by inspecting projections, querying events, tracing replay, and diagnosing stale or corrupt state. Triggers on: "debug allsource", "inspect events", "why is projection wrong", "stale state", "missing events", "projection mismatch", "event replay", "debug entity". Use MCP tools directly — they read from the data directory without a running server: Every command opens the store read-only, so it is safe to run while the app is writing. Symptom: UI shows runsCount: 0 but you know there are runs. Steps:…
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- allsource-incident-statusSkill
- allsource-partnershipsSkill
- ritual-fullSkill
- ritualSkill
- semantic-isaSkill
- admin-healthSkill
- allsource-data-accessSkill
- allsource-incident-statusSkill
- allsource-mcp-setupSkill
- allsource-onboardSkill
- chronos-data-flow-embeddedSkill
- chronos-data-flowSkill
- chronos-durabilitySkill
- chronos-embedded-durabilitySkill
- chronos-releaseSkill
- fly-statusSkill
- mammoth-memorySkill
- ritual-fullSkill
- ritualSkill
- semantic-isaSkill
- seo-aeo-auditSkill
- allsource-customerSkill
- allsource-prime-memorySkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Use MCP tools directly — they read from the data directory without a running server:
- Distinctive: line 49
Every command opens the store read-only, so it is safe to run while the app is writing.
- Distinctive: line 72
Check if the events have the fields the projection expects:
- Distinctive: line 93
Check if events are actually persisted:
- Distinctive: line 97
Check WAL vs Parquet:
- Distinctive: line 101
Verify the entity has recent events:
- Distinctive: line 132
Start with explain_entity for the overview
- Distinctive: line 133
Use event_timeline for the detailed sequence
- Distinctive: line 134
Use analyze_changes with time bounds to focus on a specific period
- Distinctive: line 135
Use reconstruct_state to see the final folded state
- Distinctive: line 140
Use quick_stats to check durability status:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AllSource Debug
Debug AllSource-backed applications by inspecting projections, querying events, tracing replay, and diagnosing stale or corrupt state.
Triggers on: "debug allsource", "inspect events", "why is projection wrong", "stale state", "missing events", "projection mismatch", "event replay", "debug entity".
Tools Available
If allsource-mcp is configured (preferred)
Use MCP tools directly — they read from the data directory without a running server:
| Tool | Use When |
query_events | Find events for an entity or event type |
quick_stats | Get store overview (counts, types, date range) |
event_timeline | See chronological event sequence for an entity |
explain_entity | Get human-readable lifecycle summary |
reconstruct_state | Fold events to rebuild current state |
get_snapshot | Get projection/snapshot state |
analyze_changes | Compare state between two time points |
sample_events | Discover what event types exist |
If allsource-inspect CLI is available
# Which data directory? An app can keep several (per profile, per workspace)
allsource-inspect stores --root <app-support-dir>
# Find all events for an entity
allsource-inspect events --data-dir <path> --entity-id "workflow:abc-123" --format json
# Find events by type prefix, printing only the payload keys
allsource-inspect events --data-dir <path> --event-type-prefix "workflow_run." --keys --format json
# Current state of every run in one pass
allsource-inspect lifecycle --data-dir <path> --event-type-prefix "workflow_run." \
--states started,completed,failed --format json
# Storage summary
allsource-inspect summary --data-dir <path>
# Events still in the WAL
allsource-inspect wal --data-dir <path> --format jsonEvery command opens the store read-only, so it is safe to run while the app is writing.
Default data directory locations
| Platform | App | Path |
| macOS | Longhand | ~/Library/Application Support/Longhand/allsource/ |
| Linux | Longhand | ~/.local/share/longhand/allsource/ |
| Docker | Core | /app/data/ (mapped via volume) |
Debugging Workflows
1. Projection shows wrong count or missing data
Symptom: UI shows runsCount: 0 but you know there are runs.
Steps:
- Query raw events for the entity:
Use query_events with entity_id="<entity>" to see all events - Check if the events have the fields the projection expects:
Use event_timeline with entity_id="<entity>" to see event sequence - Compare projection state vs reconstructed state:
Use get_snapshot for the projection view Use reconstruct_state to fold events manually Compare the two — differences indicate projection bugs
Common causes:
- Event missing a field the projection indexes on (e.g.,
definition_id) - Projection filter doesn't match event type pattern
- Events ingested with wrong entity_id format
2. Stale projection state
Symptom: Projection shows old data, new events aren't reflected.
Steps:
- Check if events are actually persisted:
Use quick_stats to see total event count and latest timestamp - Check WAL vs Parquet:
Use quick_stats — if wal_entries > 0 and parquet is behind, events may be in WAL only - Verify the entity has recent events:
Use query_events with entity_id and since=<recent timestamp>
Common causes:
- Events in WAL but not yet flushed to Parquet
- Projection registered after events were ingested (missed replay)
- Application crash before WAL fsync
3. Duplicate or missing events in replay
Symptom: Event count doesn't match expected, or state has duplicates.
Steps:
- Get full event timeline:
Use event_timeline with entity_id — check for gaps in version numbers - Look for duplicates:
Use query_events with entity_id — check for duplicate timestamps or event types - Check version sequence:
- Versions should be monotonically increasing per entity
- Gaps indicate missed events
- Duplicate versions indicate replay issues
4. Understanding an entity's lifecycle
Steps:
- Start with explain_entity for the overview
- Use event_timeline for the detailed sequence
- Use analyze_changes with time bounds to focus on a specific period
- Use reconstruct_state to see the final folded state
5. Verifying data after restart
Steps:
- Use quick_stats to check durability status:
durable: truemeans all events are persistedwal_enabled: truewith entries means WAL has dataparquet_files > 0means long-term storage is working
- Query a known entity to verify data survived:
Use query_events with a known entity_id
Key Concepts
- Events are immutable — once ingested, they cannot be modified or deleted
- Projections are derived — they're computed from events and can be rebuilt
- WAL is the write path — events hit WAL first, then flush to Parquet
- Parquet is the read path — queries read from Parquet + in-memory DashMap
- Entity ID format — typically
type:uuid(e.g.,workflow:abc-123) - Event type format — dot-separated (e.g.,
workflow_run.started,workflow_run.completed) - System events — prefixed with
_system.(tenants, config, auth, schemas)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

