Format and deliver network alerts, health warnings, and critical notifications via Slack with rich formatting, reactions, and file attachments.
SkillScore100Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/16/2026
What it changes
Passed 22 of 22 test cases with the skill, and 8 of 22 without it.
Without skill36%
With skill100%
Checks it passed that the model alone missed
Includes a GAIT session tracking reference.
Includes a GAIT session tracking reference in the message footer.
Designates `#netclaw-alerts` as the target channel for this alert.
and 17 more in the full report
14 fixed8 passed either way0 still failing0 broke
Pass-rate lift
+64 pp
Tokens
+77%
Agent turns
0%
Response time
-45%
Model gemini-3.6-flashMeasured 8/16/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
A network alert fired due to planned maintenance that was not muted in advance. Which standard emoji reaction should be placed on the alert to mark it as a false positive?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies `:no_entry:` as the emoji reaction for marking false positives or suppressed alerts.
Missed
Passed
case-13 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md193 linessingle file
Slack Network Alerts
Slack OAuth Scopes Used
Scope
Purpose
chat:write
Post alert messages to channels
chat:write.customize
Post with custom username/avatar per alert severity
reactions:write
Add emoji reactions to acknowledge/track alerts
files:write
Attach diagrams, reports, and log excerpts
app_mentions:read
Respond when users @mention NetClaw
channels:join
Join alert channels automatically
Alert Severity Formatting
Use Slack Block Kit formatting to visually distinguish severity levels.
CRITICAL Alert Format
:rotating_light: *CRITICAL — Device Unreachable*
*Device:* R1 (10.1.1.1)
*Detected:* 2024-02-21 14:32 UTC
*Impact:* 47 downstream routes affected, 3 OSPF adjacencies lost
*Symptoms:*
• Ping 0% success (was 100%)
• OSPF neighbor state: DOWN
• BGP peer 10.1.1.2: IDLE
*Recommended Action:*
1. Check physical connectivity / power
2. Verify interface status on upstream device
3. Check for reload reason if device recovers
_Thread for investigation updates →_