skills.rest
Charitablebusinessronin
CharitablebusinessroninCOMMUNITY
Explore all skills by this author →
GitHub

Allura Health & Observability

Assess PostgreSQL, Neo4j, queue depth, and pipeline latency with read-only diagnostics.

Updated Mar 18, 2026
Search Tags:#monitoring#postgresql#memory#observability#diagnostics#health#neo4j
One-click install
npx skills add https://github.com/Charitablebusinessronin/Allura_Memory --skill allura-health-observability
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Allura Health & Observability
Source: https://github.com/Charitablebusinessronin/Allura_Memory/tree/main/.opencode/skills/allura-health-observability
Command: npx skills add https://github.com/Charitablebusinessronin/Allura_Memory --skill allura-health-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Allura health and observability checks enable operators to detect degraded subsystems, backlog growth, and pipeline latency in the memory system, ensuring reliable operation and quick remediation.

Core Features & Use Cases

  • Read-only health diagnostics for PostgreSQL (episodic) and Neo4j (semantic) layers.
  • Queue depth and latency monitoring with non-mutating queries.
  • Incident and routine-health checks with guardrails and group_id enforcement.

Quick Start

Run this health-check skill with a valid group_id to retrieve current health metrics for PostgreSQL, Neo4j, and the memory pipeline.

Frequently Asked Questions about Allura Health & Observability

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

FAQPage Schema
How do I check PostgreSQL and Neo4j memory health during an incident?▼

You can check memory health by running read-only diagnostics against PostgreSQL and Neo4j layers. This skill queries subsystems without mutation to detect degraded components, backlog growth, and pipeline latency during incidents.

Can I monitor queue depth and pipeline latency without mutating the database?▼

Yes, you can monitor queue depth and pipeline latency using strictly read-only queries. The skill enforces non-mutating diagnostics and a constrained MCP allowlist to ensure systems remain untouched during health checks.

What do I need to run read-only diagnostics for the Allura memory system?▼

You need a valid group_id to run read-only diagnostics for the Allura memory system. The environment requires a constrained MCP allowlist to safely query PostgreSQL and Neo4j without risking data mutation.

What is the best way to perform routine health checks on memory pipelines?▼

The best way to perform routine health checks is applying enforced read-only diagnostics with group_id validation. This approach safely measures queue depth and latency to detect subsystem degradation and backlog growth.

Are there limitations to using read-only observability checks during production incidents?▼

Limitations include strict read-only constraints and a required group_id for execution. Because it uses a constrained MCP allowlist to prevent mutations, it cannot remediate issues directly, only detect and report degraded subsystems.

Related Skills

Explore More Software Engineering Skills→
Knuckles-TeamKnuckles-Team
11

gitlab-members

List GitLab group or project members with optional filters.

Official
Intermediate
clawpod-appclawpod-app
46

incident-response

Analyze production incident metrics and output rollback recommendations.

Community
Intermediate
NirajkashyapNirajkashyap

wiki-export

Export wiki knowledge graphs to graph.json, graph.graphml, cypher.txt, and graph.html.

Community
Advanced
BRO3886BRO3886
64

healthsync

Query Apple Health metrics from a local SQLite database via CLI or SQL.

Community
Intermediate