Skill Health

Monitor GitHub Actions skill fleet health and performance metrics.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/enuno/noesis-aeon --skill skill-health-enuno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Skill Health
Source: https://github.com/enuno/noesis-aeon/tree/main/skills/skill-health
Command: npx skills add https://github.com/enuno/noesis-aeon --skill skill-health-enuno

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides comprehensive observability for the health and performance of a fleet of GitHub Actions skills, enabling quick identification of issues and insights into fleet performance.

Core Features & Use Cases

  • Health Audits: Classify skill status (Healthy, Degraded, Critical) and file issues for new failures.
  • Analytics: Present a fleet-wide ranked view of skill performance, including success rates, failure rates, and anomaly flags.
  • Notification: Send alerts and notifications based on health state changes and anomalies.
  • Use Case: For an operations team managing a large number of GitHub Actions skills, this Skill helps ensure that the fleet is performing optimally and any issues are addressed promptly.

Quick Start

To view the health status of all skills, run the Skill Health skill with no arguments. For analytics, run with the 'analytics' or 'metrics' flag followed by a time window in hours.

Frequently Asked Questions about Skill Health

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

FAQPage Schema
How do I monitor GitHub Actions skill health across a large fleet?

To monitor GitHub Actions skill health across a fleet, you need a system that classifies skill status and tracks success rates. This Skill provides fleet-wide observability by classifying skills as Healthy, Degraded, or Critical and filing issues for new failures automatically.

How do I get analytics and metrics for a fleet of GitHub Actions skills?

To get analytics and metrics for GitHub Actions skills, run the Skill with the 'analytics' or 'metrics' flag followed by a time window in hours. It presents a ranked view of fleet performance, including success rates, failure rates, and anomaly flags.

Can I automatically file issues when GitHub Actions skills fail?

Yes, you can automatically file issues when GitHub Actions skills fail. During health audits, the Skill detects new failures and automatically files issues in your repository to ensure problems are addressed promptly.

How do I set up alerting for anomaly detection in GitHub Actions?

To set up alerting for anomaly detection in GitHub Actions, you need a tool that tracks health state changes. This Skill sends alerts and notifications based on detected anomalies and health state changes across your skill fleet.

Do I need GitHub API access to track skill performance and issues?

Yes, you need GitHub API access and local data storage to track skill performance and issues. The Skill requires these dependencies to monitor skill runs, analyze health states, and file issues for new failures.

What is the best way to classify degraded or critical GitHub Actions skills?

The best way to classify degraded or critical GitHub Actions skills is to perform a health audit. This Skill audits your fleet, categorizing each skill's health status and flagging anomalies to help operations teams identify issues quickly.