Sigil: Observability Setup
SkillMonitoring & opsUse when: installing or verifying the standard observability package in a repository so sigils can append post-run JSON telemetry, reflection state, and dedicated governance ledgers.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Sigil: Observability Setup skill
What this skill tells your AI
The instructions your AI receives, as published by cyberalchemyai/arcanum in formulae/observability-setup/SKILL.md and read by ahel’s review.
- repository root path,
- preferred storage model:
central,per-sigil, orhybrid, - whether existing files should be repaired,
- existing observability folder path, if non-standard.
.arcanum/observability/
- create or verify the standard observability package path,
- preserve existing telemetry by default,
- produce valid JSON config and reflection-state files,
- create an append-only JSONL ledger path,
- create the dedicated home for the append-only subagent dispatch YAML ledger,
- state the selected storage model,
- avoid requiring a specific application framework or agent runtime.
- overwriting existing telemetry ledgers,
- storing telemetry inside the Arcanum repository when observing a different consuming repository,
- creating full duplicate per-sigil ledgers instead of rebuildable central-ledger indexes,
- treating setup as reflection,
- adding runtime-specific dependencies to the portable package contract.
## Observability Setup Result
- Repository: <path>
- Package path: <path>
- Storage model: central-ledger-reference-indexes
- Files created: <paths>
- Files preserved: <paths>
- Validation: <checks performed>
- Next step: <how sigils should append invocation telemetry>
Signals
- GitHub stars
- 25
- Forks
- 3
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
observability-setup- Source
- github.com/cyberalchemyai/arcanum