observability-setup

Create a repository-local observability package with JSON config and reflection files.

20|3|Updated May 14, 2026
One-click install
npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill observability-setup-cyberalchemyai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-setup
Source: https://github.com/cyberAlchemyAI/Arcanum/tree/main/.claude/skills/observability-setup
Command: npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill observability-setup-cyberalchemyai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Observability Setup provides a deterministic, portable telemetry package to store sigil usage telemetry and reflection data in the consuming repository, avoiding centralized telemetry ownership.

Core Features & Use Cases

  • Creates the standard repository observability structure at .arcanum/observability with folders for signals, indexes, and reflections.
  • Generates a config.json and reflection-state.json that define storage model, paths, and thresholds to govern telemetry and reflection.
  • Enables per-sigil and per-capability indexing alongside a central ledger, with optional hooks and reflections folders for long-running runs.

Quick Start

Run the observability setup to scaffold the standard repo-local telemetry package.

Frequently Asked Questions about observability-setup

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

FAQPage Schema
How do I set up repository-local observability for sigil telemetry?

Repository-local observability means provisioning a deterministic telemetry package within your repository to store sigil usage data, avoiding centralized telemetry ownership. It uses a central ledger with per-sigil indexes to capture run history.

What configuration files are needed to enable sigil telemetry and reflection?

Run the observability setup to scaffold the standard repo-local telemetry package, which creates the .arcanum/observability directory structure. This generates required JSON config and reflection files, alongside folders for signals, indexes, and reflections.

Can I store telemetry data directly inside my own repository instead of a centralized service?

This approach provisions a deterministic, repo-local observability package, avoiding centralized telemetry ownership. It creates .arcanum/observability with folders for signals, indexes, and reflections, keeping all telemetry data local to the consuming repository.

How does per-sigil indexing work with a central telemetry ledger?

Yes, the setup provides optional hooks and a reflections folder within the .arcanum/observability package. These are designed to capture and store reflection state alongside run history for long-running sigil operations.