How do I install the Observal Advanced skill?

Run npx skillmds@latest add observal/observal-advanced in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Observal Advanced safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Observal Advanced?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Observal Advanced free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Observal Advanced?

Observal (@observal) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Observal Advanced by observal — Agent Skill

Name: Observal Advanced
Author: Observal

Observal Advanced

Recovers Observal session ingestion, manages CLI upgrades, downgrades and rollback, and performs explicit local Agent fallback when the server is unavailable. Use when the user asks to reconcile missed sessions, repair CLI version state, or continue locally after a confirmed connection or configuration failure.

Observal 07bc44f 2 files · 5.0 KB Updated Sep 17, 2026

File contents

Recovering Observal

Execution contract

Execute commands with a 60 second timeout unless the operation documents a longer wait.
Use machine output by default: add --output json whenever supported. Parse list results from items and pagination fields.
Run --help before acting when a path or flag is uncertain.
Use dry run before reconciliation when scope or session volume is uncertain.
Supply documented force flags so version operations never prompt.
Verify cursor, outbox, installed version, checksum, and rollback state after recovery operations.
Fail openly. Never hide an unavailable server behind automatic local writes.
Never retry reconciliation, version changes, or fallback writes without checking resulting state.

Read Recovery workflows completely before executing.

Decision rules

Healthy telemetry does not need routine reconciliation.
Reconcile repairs missed local session delivery. It does not replace hook or extension installation.
Upgrade, downgrade, and rollback are distinct requests. Do not substitute one for another.
Local fallback is allowed only after the CLI explicitly reports Connection failed or Not configured, and only when the user still wants local files written.
Local fallback creates harness-native Agent files. It does not publish Registry state and must be reported as local-only.
Never invent telemetry environment variables or wrappers.

Completion

Report sessions discovered, queued, skipped, or failed for reconciliation; old and new versions for CLI changes; or exact local paths for fallback. Include unresolved warnings and the command needed once the server is reachable.

---name: observal-advanceddescription: Recovers Observal session ingestion, manages CLI upgrades, downgrades and rollback, and performs explicit local Agent fallback when the server is unavailable. Use when the user asks to reconcile missed sessions, repair CLI version state, or continue locally after a confirmed connection or configuration failure.---# Recovering Observal## Execution contract1. Execute commands with a 60 second timeout unless the operation documents a longer wait.2. **Use machine output by default:** add `--output json` whenever supported. Parse list results from `items` and pagination fields.3. Run `--help` before acting when a path or flag is uncertain.4. Use dry run before reconciliation when scope or session volume is uncertain.5. Supply documented force flags so version operations never prompt.6. Verify cursor, outbox, installed version, checksum, and rollback state after recovery operations.7. Fail openly. Never hide an unavailable server behind automatic local writes.8. Never retry reconciliation, version changes, or fallback writes without checking resulting state.Read [Recovery workflows](references/recovery-workflows.md) completely before executing.## Decision rules- Healthy telemetry does not need routine reconciliation.- Reconcile repairs missed local session delivery. It does not replace hook or extension installation.- Upgrade, downgrade, and rollback are distinct requests. Do not substitute one for another.- Local fallback is allowed only after the CLI explicitly reports `Connection failed` or `Not configured`, and only when the user still wants local files written.- Local fallback creates harness-native Agent files. It does not publish Registry state and must be reported as local-only.- Never invent telemetry environment variables or wrappers.## CompletionReport sessions discovered, queued, skipped, or failed for reconciliation; old and new versions for CLI changes; or exact local paths for fallback. Include unresolved warnings and the command needed once the server is reachable.

Frequently asked questions