feed-health-monitor-auditor

Audit feed health monitoring for retry mechanisms, freshness checks, and escalation protocols.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BruceTyndall/socelle-global --skill feed-health-monitor-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feed-health-monitor-auditor
Source: https://github.com/BruceTyndall/socelle-global/tree/main/.agents/skills/feed-health-monitor-auditor
Command: npx skills add https://github.com/BruceTyndall/socelle-global --skill feed-health-monitor-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill addresses the critical need to ensure that feed processing systems are healthy, retrying failed operations, and maintaining data freshness. It helps prevent data staleness and system failures by auditing monitoring mechanisms.

Core Features & Use Cases

  • Audit Retry Logic: Verifies that mechanisms are in place to retry failed feed processing jobs.
  • Freshness Checks: Ensures that systems are actively monitoring and reporting on the last successful run time of feeds.
  • Failure Escalation: Audits the presence of alerts or escalation procedures for persistent feed failures.
  • Use Case: When deploying updates to the feed orchestration system or when reviewing the admin health dashboards, use this skill to proactively verify that the health monitoring components are correctly configured and functioning as expected.

Quick Start

Use the feed-health-monitor-auditor skill to audit feed health monitoring for retry and freshness checks.

Frequently Asked Questions about feed-health-monitor-auditor

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

FAQPage Schema
How do I audit feed health monitoring systems for retry logic and data freshness?

You can audit feed health monitoring by verifying the presence and correctness of retry mechanisms, checking telemetry for last_run_at timestamps, and validating data freshness checks. This skill systematically reviews feed orchestration systems and admin health dashboards to ensure operational reliability and prevent data staleness.

What is feed health auditing and when do I need it for feed orchestration services?

Feed health auditing is the verification of retry mechanisms, data freshness checks, and failure escalation protocols in feed processing systems. You need it when deploying updates to feed orchestration systems or reviewing admin health dashboards to proactively confirm that monitoring components are correctly configured and functioning.

How do I verify failure escalation protocols and error states in feed processing jobs?

You verify failure escalation by auditing feed monitoring systems for the presence of alerts or escalation procedures for persistent feed failures. This skill checks telemetry data for error states, retry policies, and last_run_at timestamps to confirm that operational reliability mechanisms are properly configured.

Can I use this auditing skill with my existing feed orchestration system and health dashboards?

Yes, this skill is applicable to feed orchestration services and administrative health dashboards. It requires no external dependencies and works by verifying telemetry for last_run_at, error states, and retry policies within your existing feed processing infrastructure to ensure monitoring components function as expected.

What's the best way to prevent data staleness and ensure system reliability in feed processing?

The best way to prevent data staleness is to audit feed health monitoring systems for retry mechanisms, freshness checks, and failure escalation protocols. This skill verifies that systems actively monitor last successful run times and report error states, ensuring operational reliability and preventing system failures.

Why does my feed health monitoring show stale data despite having retry logic configured?

Stale data can occur when retry mechanisms, freshness checks, or failure escalation protocols are incorrectly configured in feed processing systems. This skill audits telemetry for last_run_at timestamps and error states to identify whether monitoring components are properly tracking and reporting feed health.