skills.rest
stevengonsalvez
stevengonsalvezCOMMUNITY
Explore all skills by this author →
GitHub

reflect-verify

Run static checks and smoke tests to verify Reflect system health.

2|1|Updated Jun 19, 2026
Search Tags:#tmux#health check#smoke test#CLAude#Reflect
One-click install
npx skills add https://github.com/stevengonsalvez/ainb-reflect-memory --skill reflect-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reflect-verify
Source: https://github.com/stevengonsalvez/ainb-reflect-memory/tree/main/.agents/skills/reflect-verify
Command: npx skills add https://github.com/stevengonsalvez/ainb-reflect-memory --skill reflect-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill unit verifies the end-to-end health of Reflect, identifying issues such as drain malfunction, ingest problems, statusline errors, and Claude/Codex harness smoke checks.

Core Features & Use Cases

  • End-to-End Health Verification: Static checks, isolated queue/drain smoke, live read-only health, and optional real Claude tmux smoke.
  • Use Case: Run this Skill when Reflect seems stuck, drain is not clearing pending reflections, ingest has gone quiet, statusline ERR needs proof, or a change needs tmux-backed validation.

Quick Start

Run the reflect-verify script to initiate a series of checks on Reflect.

Frequently Asked Questions about reflect-verify

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

FAQPage Schema
How do I run a health check on Reflect to diagnose drain and ingest issues?▼

To run a health check on Reflect, execute a verification script that performs static checks, isolated queue/drain smoke tests, and live read-only health monitoring to identify drain malfunctions and ingest problems.

Why does my Reflect statusline show ERR and how can I verify the problem?▼

A Reflect statusline ERR indicates potential system failures. You can verify the problem by running end-to-end health checks that test static configurations, drain functionality, and live read-only system status for proof of the error.

Can I use Claude tmux smoke tests to validate Reflect changes?▼

Yes, you can use optional real Claude tmux smoke tests to validate Reflect changes. This provides end-to-end functionality verification by testing the Claude harness within a tmux-backed environment.

Do I need access to Claude and Codex environments to verify Reflect health?▼

Yes, verifying Reflect health requires access to both Reflect and Claude/Codex environments to execute comprehensive end-to-end checks, including optional real Claude tmux smoke tests for harness validation.

What is the best way to troubleshoot a Reflect system that seems stuck?▼

The best way to troubleshoot a stuck Reflect system is running an end-to-end health verification that executes static checks, isolated queue/drain smoke tests, and live read-only monitoring to pinpoint drain or ingest failures.

Related Skills

Explore More Software Engineering Skills→
matthewdeavesmatthewdeaves

setup-machine

Register a new Classic Mac in the MCP server and verify FTP connectivity.

Community
Intermediate
KYRIE66nbKYRIE66nb

configure-telegram

Configure Telegram bot notifications for OMX session events and tasks.

Community
Intermediate
ajbareaajbarea

theoros

Run a repo REPL in a named tmux session with read-only spectator workflow.

Community
Intermediate
wangdaqian08wangdaqian08

prod-smoke-test

Run end-to-end production smoke tests for deployed Werewolf releases.

Community
Advanced