Individual skill
solidping-monitoring
Use when the user asks about uptime, whether a site or service is down, why a check is failing, incidents or status pages, or wants to add or change monitoring (HTTP, TCP, DNS, SSL expiry, databases, queues, heartbeats) through the SolidPing MCP server.
plugins/fclairamb/solidping-plugin/skills/solidping-monitoring/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,531
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,104 bytes
Read excerpt
# Uptime monitoring with SolidPing
The `solidping` MCP server exposes one SolidPing organization: its checks, results, incidents,
status pages. The user signed in with OAuth; the server applies their role.
## Reading
1. Start with `list_checks` (filter by label or status when the user names one), then `get_check`.
2. For "why is it failing", call `diagnose_check`, then `list_results` for the recent history.
Report what changed (status code, latency, error text, which region), with timestamps.
3. For outages, `list_incidents` and `get_incident`. Give start, end or "ongoing", and duration.
## Creating or changing checks
