Signal Monitoring
CheckedContinuously monitors system logs and metrics, proactively alerting DevOps teams to potential issues and anomalies.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add guia-matthieu/clawfu-skills --skill signal-monitoring -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
guia-matthieu
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned guia-matthieu/clawfu-skills at 4108f5c010.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 4108f5c010
- Scanned
- 1 file, 365 lines
About this skill
What it does
The signal-monitoring skill allows AI agents to monitor various signals, including system metrics and application logs. It can identify anomalies, trigger alerts based on predefined thresholds, and provide summaries of observed trends. This facilitates proactive issue detection and improved operational efficiency.
When to use it
- Proactive System Health Checks: Regularly monitor CPU usage, memory consumption, or disk space across servers.
- Application Performance Monitoring: Track response times, error rates, and other key application metrics in real-time.
- Log Analysis for Security Threats: Scan logs for suspicious patterns indicative of potential security breaches.
- Automated Incident Response: Trigger automated actions (e.g., scaling resources) when specific signal thresholds are breached.
Key capabilities
- Signal ingestion from various sources
- Anomaly detection based on historical data
- Threshold-based alerting
- Trend summarization and reporting
Example prompts
- "Monitor CPU usage on server
web-01and alert me if it exceeds 80%." - "Analyze application logs for errors related to database connections in the last hour."
- "Show me a summary of network traffic trends over the past 24 hours."
Tips & gotchas
The skill requires access to relevant signal sources (e.g., system metrics endpoints, log files). Ensure proper authentication and authorization are configured for these sources before deployment.