skills.rest
odylith
odylithOFFICIAL
Explore all skills by this author →
GitHub

odylith-compass-refresh

Refresh Compass state to settle stalled passes across hosts.

34|3|Updated Apr 6, 2026
Search Tags:#debugging#orchestration#state-management#refresh#agent-workflow#compass#odylith
One-click install
npx skills add https://github.com/odylith/odylith --skill odylith-compass-refresh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: odylith-compass-refresh
Source: https://github.com/odylith/odylith/tree/main/.agents/skills/odylith-compass-refresh
Command: npx skills add https://github.com/odylith/odylith --skill odylith-compass-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compass state can become stale during a pass, causing uncertain or divergent decisions. This skill provides a deterministic way to refresh the Compass state so the current pass can settle and proceed with confidence.

Core Features & Use Cases

  • Automatic Compass state refresh when a pass stalls or drifts, ensuring deterministic progression.
  • Safe, idempotent refresh that preserves history and avoids data loss across Codex/Claude Code hosts.
  • Use Case: after a failed attempt or prolonged computation, invoke the refresh to re-stabilize the agent's reasoning.

Quick Start

Instruct the agent to refresh the Compass state when the current pass needs to settle before continuing.

Frequently Asked Questions about odylith-compass-refresh

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

FAQPage Schema
How do I settle stalled agent workflow state during a long-running pass?▼

To settle stalled agent workflow state, you refresh the Compass state using idempotent logic that preserves history and stabilizes the current pass for consistent progression across hosts.

Why does agent state drift or become stale during prolonged orchestration passes?▼

Agent state drifts during prolonged orchestration passes because long-running or stalled computations cause uncertain decisions, requiring a deterministic Compass state refresh to re-stabilize the agent's reasoning.

Can I refresh state management history without losing data across multiple hosts?▼

Yes, you can refresh state management history without data loss across Codex and Claude Code hosts because the refresh logic is idempotent, safe, and explicitly preserves historical state data.

What's the best way to stabilize agent reasoning after a failed orchestration attempt?▼

The best way to stabilize agent reasoning after a failed attempt is to invoke a Compass state refresh, which deterministically settles the current pass and allows the agent to proceed confidently.

When should I trigger a state refresh for debugging an agent workflow?▼

You should trigger a state refresh for debugging when a pass stalls, drifts, or experiences prolonged computation, ensuring the agent's state settles before continuing the workflow.

Does odylith-compass-refresh support idempotent state management for state stabilization?▼

Yes, odylith-compass-refresh supports idempotent state management, applying safe refresh logic that yields a settled Compass state without duplicating side effects or losing history.

Related Skills

Explore More Software Engineering Skills→
ZhaoyuWuZhaoyuWu

harness-kickoff

Loads session context, constraints, and workflow state for kickoff.

Community
Intermediate
whatwecandowhatwecando

forge-resume

Load the last saved state and resume interrupted workflows with user confirmation.

Community
Intermediate
apsulliapsulli

Context Health Monitor

Detect context complexity thresholds and trigger state dumps in agent sessions.

Community
Advanced
bosens-Chinabosens-China
10

langgraph-persistence

Manage LangGraph persistent state with checkpointers and thread IDs.

Community
Advanced