aboylabs/ai-agent-skills / skills/devops/api-monitoring-bots
api-monitoring-bots
UnverifiedBuild monitoring bots that poll APIs and send notifications on state changes (new listings, price alerts, status updates)
Security report
UnverifiedStatic analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.
- Commit
a0c9d49124849ba3de5d87b197c675c0176d7d04- Content hash
388b03b3e98b3c09bef0e02d1a974810e2e469bf6fbdc29188ec10d4fa5a6ec7- Scanned
- 2026-11-17
- Scanner version
- skillxone-scan-1.0.0
- Policy version
- 0.1-draft
- Decision
- 1 open medium finding to review.
- Verification expires
- Not applicable
Findings (1 medium, 4 low)
The skill sets something to run automatically later (scheduled task, login item or shell start-up file).
sudo systemctl enable api-monitorSuggested fix: Do not install persistent jobs or edit shell start-up files. Tell the user what to add if they want it.
The skill sends data to a chat webhook, which accepts arbitrary data.
url = f"https://api.telegram.org/bot{TELEGRAM_BOT_TOKEN}/sendMessage"Suggested fix: Make sure only the intended message is sent and that the user knows about it.
A command runs with administrator privileges.
sudo nano /etc/systemd/system/api-monitor.serviceSuggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.
A command runs with administrator privileges.
sudo systemctl daemon-reloadSuggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.
A command runs with administrator privileges.
sudo journalctl -u api-monitor -fSuggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.
Checks run
- prompt-injection
- dangerous-commands
- credentials
- network
- file-access
- integrity
Checks skipped
- dependencies: No dependency manifest in the skill directory.
- gitleaks: gitleaks is not installed on this host.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |