Alarm
Skill CloudChef/atlasclaw-providers/providers/SmartCMP-Provider/skills/alarm
atlasclaw-providers are the integration with enterprise systems through skills and webhook.
npx -y skills add CloudChef/atlasclaw-providers --skill alarmAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Alarm and resource health skill. List and analyze alerts, collect component-model-driven resource monitoring evidence for LLM health analysis, and perform alert status operations.
SKILL.md
14.9 KB, as published. Nobody here has run it
alarm
Alarm and resource-health workflow for triggered alert retrieval, rule-aware alert analysis, component-model-driven resource health evidence, and status operations.
Purpose
Provide alarm-management capabilities:
- List triggered alerts with machine-readable metadata
- Resolve one exact resource and distinguish current firing/muted alerts from currently resolved alerts triggered within the configured lookback for comprehensive resource analysis
- Analyze one alert with normalized facts, datasource-enriched resource context, assessment, and remediation guidance
- Analyze one resource independently of alerts by handing component-specific monitoring evidence to the LLM
- Perform validated status operations (
mute,resolve,reopen)
Scripts
| Script | Description | Location |
|---|---|---|
list_alerts.py | Query the CMP comprehensive-search mapping /alarm-alert?query for both general and exact-resource listing, then emit ##ALARM_META_START## metadata | scripts/ |
analyze_alert.py | Fetch alert + rule context, enrich related resources via datasource list_resource.py, and emit ##ALARM_ANALYSIS_START## output | scripts/ |
analyze_resource_health.py | Resolve one resource, load its component monitoring model, query scoped Prometheus series, and emit ##RESOURCE_HEALTH_CONTEXT_START## evidence for LLM analysis | scripts/ |
operate_alert.py | Call /alarm-alert/operation for validated status changes | scripts/ |
Workflow
See references/WORKFLOW.md for the supported workflow.
Resource Enrichment
During alert analysis, this skill should silently reuse the datasource skill's
shared ../datasource/scripts/list_resource.py flow when the alert exposes
entityInstanceId or nodeInstanceId.
- Resolve related SmartCMP resources before finalizing the analysis narrative.
- Merge normalized
type + propertiesresource facts into the alert analysis payload. - If resource lookup is unavailable, continue the alert analysis with core alert and policy facts, and treat resource enrichment as best-effort context.
Resource Health Analysis
Resource health analysis is independent of alert analysis:
- Resolve the resource through datasource resource helpers and use its normalized
componentType. - Load the effective monitoring model for that component; never substitute a generic VM metric list.
- Query only PromQL that can be scoped to the resolved resource through model-declared labels and exporter identity.
- Emit descriptive statistics and monitoring coverage, but leave
healthy,abnormal, orindeterminatejudgment to the AtlasClaw LLM. - The final LLM response must include status, confidence, principal findings, metric evidence, missing evidence, and recommended actions.
- Treat disabled, unavailable, or missing monitoring as an evidence gap rather than proof that the resource is healthy or unhealthy.
- Do not read active alerts or alarm-policy thresholds for the resource-health conclusion.
Resource Alert Evidence
Resource alert evidence complements, but never changes, the independent health contract above.
- Call
smartcmp_list_alertswith the same exact resource target used by the other comprehensive analysis tools. current_and_recentqueries currentALERT_FIRINGandALERT_MUTEDalerts without a trigger-time limit, then queries alerts whose current status isALERT_RESOLVEDand whosetriggerAtis within the last seven days. SmartCMP does not expose aresolveAtrange in this search contract, so this must not be described as “resolved during the last seven days.”- Resolve the target to SmartCMP
Resource.id, pass it through the exacttargetEntityIdquery parameter, and verify the same field in every returned alert. - Do not use the resource name,
nodeInstanceId, orentityInstanceIdas resource-association evidence. - Read
##RESOURCE_ALERT_COVERAGE_START##before concluding that no alert was observed.partialorindeterminateassociation means the alert dimension is unknown. - If the same alert is observed as current and resolved across the two requests, preserve both observations and treat the lifecycle race as
partialevidence. - Absence of a matched alert is not monitoring-health evidence and must not be used to upgrade an
indeterminatehealth conclusion.