Sigil: Signal Observer

SkillMonitoring & ops

Use when: deriving post-run behavior signals from a sigil invocation envelope and appending reusable observability telemetry.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Sigil: Signal Observer skill

What this skill tells your AI

The instructions your AI receives, as published by cyberalchemyai/arcanum in development/invoke-plan-successor-design-material-v1/materials/root-signal-observer/SKILL.md and read by ahel’s review.

  • a sigil execution has completed, blocked, or failed,
  • an invocation envelope exists or can be assembled safely,
  • the run produced meaningful user-facing output, decision, validation, or orchestration result,
  • the project has or wants a repository-local observability ledger,
  • reflection thresholds should be evaluated from real usage.
  • invocation envelope path, preferably matching framework/observability/templates/invocation-envelope.json,
  • optional telemetry ledger path,
  • optional hook operations ledger path,
  • visible execution summary,
  • changed artifact list,
  • validation results,
  • Quality Bar and Anti-Patterns for the invoked sigil, when available,
  • reflection state, when available.
  • envelope: .arcanum/observability/tmp/latest-invocation.json
  • ledger: .arcanum/observability/signals/sigil-invocations.jsonl
  • reflection state: .arcanum/observability/reflection-state.json

Use .arcanum/observability/hooks/hook-operations.jsonl for observer start, completion, skip, failure, and dedupe events. These rows must carry observe: false.

  • read or assemble a valid invocation envelope,
  • derive signals only from visible evidence,
  • append one valid JSON object per observed invocation,
  • preserve privacy and avoid sensitive raw content,
  • classify Quality Bar status and Anti-Pattern hits when evidence exists,
  • evaluate reflection trigger state,
  • avoid blocking or changing the primary task outcome.
  • rewriting the observed sigil during observation,
  • storing secrets or large raw conversation excerpts,
  • inventing quality status without evidence,
  • appending invalid JSONL,
  • treating observability failure as primary task failure unless observability was the requested task,
  • producing many telemetry rows for one invocation,
  • hiding severe workflow gaps behind a generic success note.
## Signal Observer Result

- Observed sigil: <name>
- Result: recorded | skipped | failed
- Ledger: <path>
- Signals: <counts by type>
- Quality Bar: pass | partial | fail | not_checked
- Anti-Pattern hits: <count and summary>
- Reflection trigger: none | manual | usage-threshold | output-threshold | gap-threshold | severe-gap
- Recommendation: none | targeted-update | reflect-now
- Validation: <checks performed>

Signals

GitHub stars
25
Forks
3
Last commit
Sep 2026

Others that do the same job

Advanced
Catalog kind
skill
Gateway key
signal-observer
Source
github.com/cyberalchemyai/arcanum