check-sophia-progress

Monitor Sophia rollup worker status, daemon health, and journal lag.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/sancovp/doc-mirror --skill check-sophia-progress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-sophia-progress
Source: https://github.com/sancovp/doc-mirror/tree/main/skills/check-sophia-progress
Command: npx skills add https://github.com/sancovp/doc-mirror --skill check-sophia-progress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users monitor the live status and performance of the Sophia rollup and cohere worker, ensuring that the system is running smoothly and up-to-date.

Core Features & Use Cases

  • Status Check: Determine if the Sophia rollup daemon is running and if it is catching up with the latest journals.
  • Lag Monitoring: Measure how far behind the latest journal the Sophia worker is and identify any issues flagged by meta-Sophia.
  • Use Case: When checking for system stability, during rehydration or when a query result appears stale, or when users want to know the health of Sophia.

Quick Start

Execute the 'check-sophia-progress' command to get an immediate status update.

Frequently Asked Questions about check-sophia-progress

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

FAQPage Schema
How do I check if the Sophia rollup worker is running and catching up with journals?

To check Sophia rollup worker status, execute the command to assess daemon health and verify whether the worker is actively catching up with the latest journal updates for real-time operational insights.

What is the best way to measure system performance lag in a rollup worker?

Measuring rollup worker system performance lag involves utilizing system commands and graph queries to calculate how far behind the latest journal the worker is, identifying any flagged issues by meta-Sophia.

Why does my query result appear stale during system rehydration?

Your query result appears stale during system rehydration because the rollup worker may be lagging behind the latest journal. Checking journal coherency and daemon health helps identify this operational delay.

Can I assess journal coherency and daemon health without external dependencies?

Yes, you can assess journal coherency and daemon health without external dependencies. The monitoring process uses built-in system commands and graph queries to provide real-time operational insights into the rollup worker.

When should I perform a health assessment on a rollup worker?

You should perform a health assessment on a rollup worker when checking for system stability, during rehydration processes, when query results appear stale, or to monitor operational lag and accuracy.