Kibana Connectors
aspectrr/deer
Create and manage Kibana connectors for Slack, PagerDuty, Jira, webhooks, and more via REST API or Terraform.
Work on Supercheck HTTP, ping, or DNS monitors, regional scheduling and aggregation, alert state/history, incidents, or email, Slack, PagerDuty, and webhook notifications.
Install Supercheck Monitoring Alerts
$ npx skills add supercheck-io/supercheck --skill supercheck-monitoring-alerts -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install supercheck-io/supercheck supercheck-monitoring-alerts --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/supercheck-io/supercheck.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/monitoring-alerts .claude/skills/supercheck-monitoring-alerts && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "supercheck-monitoring-alerts" agent skill from https://github.com/supercheck-io/supercheck/tree/main/.agents/skills/monitoring-alerts into .claude/skills/supercheck-monitoring-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "supercheck-monitoring-alerts", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/supercheck-io/supercheck/tree/main/.agents/skills/monitoring-alertsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add supercheck-io/supercheck --skill supercheck-monitoring-alerts -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install supercheck-io/supercheck supercheck-monitoring-alerts --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/supercheck-io/supercheck.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/monitoring-alerts .agents/skills/supercheck-monitoring-alerts && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "supercheck-monitoring-alerts" agent skill from https://github.com/supercheck-io/supercheck/tree/main/.agents/skills/monitoring-alerts into .agents/skills/supercheck-monitoring-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "supercheck-monitoring-alerts", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add supercheck-io/supercheck --skill supercheck-monitoring-alerts -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install supercheck-io/supercheck supercheck-monitoring-alerts --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/supercheck-io/supercheck.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/monitoring-alerts .cursor/skills/supercheck-monitoring-alerts && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "supercheck-monitoring-alerts" agent skill from https://github.com/supercheck-io/supercheck/tree/main/.agents/skills/monitoring-alerts into .cursor/skills/supercheck-monitoring-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "supercheck-monitoring-alerts", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/supercheck-io/supercheck.git --path .agents/skills/monitoring-alerts--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add supercheck-io/supercheck --skill supercheck-monitoring-alerts -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install supercheck-io/supercheck supercheck-monitoring-alerts --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/supercheck-io/supercheck.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/monitoring-alerts .gemini/skills/supercheck-monitoring-alerts && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "supercheck-monitoring-alerts" agent skill from https://github.com/supercheck-io/supercheck/tree/main/.agents/skills/monitoring-alerts into .gemini/skills/supercheck-monitoring-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "supercheck-monitoring-alerts", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install supercheck-io/supercheck supercheck-monitoring-alertsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add supercheck-io/supercheck --skill supercheck-monitoring-alerts -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/supercheck-io/supercheck.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/monitoring-alerts .github/skills/supercheck-monitoring-alerts && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "supercheck-monitoring-alerts" agent skill from https://github.com/supercheck-io/supercheck/tree/main/.agents/skills/monitoring-alerts into .github/skills/supercheck-monitoring-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "supercheck-monitoring-alerts", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add supercheck-io/supercheck --skill supercheck-monitoring-alerts -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install supercheck-io/supercheck supercheck-monitoring-alerts --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/supercheck-io/supercheck.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/monitoring-alerts .opencode/skills/supercheck-monitoring-alerts && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "supercheck-monitoring-alerts" agent skill from https://github.com/supercheck-io/supercheck/tree/main/.agents/skills/monitoring-alerts into .opencode/skills/supercheck-monitoring-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "supercheck-monitoring-alerts", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
supercheck-monitoring-alerts- GitHub stars
- 215
- Token cost
- ~855 tokens
- SKILL.md length
- 346 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Work on Supercheck HTTP, ping, or DNS monitors, regional scheduling and aggregation, alert state/history, incidents, or email, Slack, PagerDuty, and webhook notifications.
- Tasks that involve Monitoring and alerting
- SKILL.md covers Monitor definition and execution, Aggregation, Alert state and history and Notification providers, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Webhooks
What it does
Supercheck Monitoring Alerts is an agent skill from supercheck-io/supercheck. Work on Supercheck HTTP, ping, or DNS monitors, regional scheduling and aggregation, alert state/history, incidents, or email, Slack, PagerDuty, and webhook notifications.
Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Monitoring and alerting and Webhooks. It works with PagerDuty and Slack. The repository describes itself as: Open-Source Testing, Monitoring, and AI SRE — as Code. The licence is AGPL-3.0.
When your agent uses it
- Tasks that involve Monitoring and alerting
- Tasks that involve Webhooks
Example prompts
- “/supercheck-monitoring-alerts”
What it can do on your machine
Read from SKILL.md and the folder at commit b08ab53. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are mermaid).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Supercheck Monitoring Alerts loads about 855 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 346 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from supercheck-io/supercheck at commit b08ab53, republished under its AGPL-3.0 licence (© supercheck-io). 346 words, ~855 tokens.
Download SKILL.mdSave it as
.claude/skills/supercheck-monitoring-alerts/SKILL.md (or your agent's skills folder).- name
- supercheck-monitoring-alerts
- description
- Work on Supercheck HTTP, ping, or DNS monitors, regional scheduling and aggregation, alert state/history, incidents, or email, Slack, PagerDuty, and webhook notifications.
Supercheck monitoring and alerts
flowchart LR
SCHED[Distributed monitor scheduler] --> Q[Regional queues]
Q --> CHECK[HTTP, ping, or DNS execution]
CHECK --> AGG[Regional aggregation]
AGG --> STATE{Alert state machine}
STATE --> HIST[Alert history]
STATE --> NOTIFY[Notification providers]Monitor definition and execution
- Monitor definitions are tenant-owned configuration; executions and regional results are immutable observations.
- Preserve URL/host, method/type, headers/body, timeout, expected response/assertions, interval, retry, enabled state, locations, and notification relationships across schema, APIs, UI, scheduler, queue, and worker.
- Monitor destinations are untrusted. Apply input validation and SSRF-safe resolution at configuration time and again at execution, including redirects and DNS changes.
- Scheduling is safe across multiple app replicas using the current distributed coordination mechanism. Restarts or overlapping scheduler ticks must not duplicate dispatch.
- Location selection maps deterministically to worker queues and rejects unknown/unavailable locations deliberately.
Aggregation
- A regional result and aggregate monitor state are separate. Never infer global health from one region.
- Define how missing, late, timed-out, and conflicting regional results affect aggregate status; preserve that rule across dashboards, APIs, and alert evaluation.
- Use consistent units and boundaries for latency, uptime, thresholds, and time windows.
- Store enough immutable evidence to explain why an alert transitioned without retaining secrets or unrestricted response bodies.
Alert state and history
- Model transitions explicitly using the current states and consecutive-failure/recovery policy.
- Persist transition history before or atomically with outbound notification scheduling.
- Deduplicate repeated failing observations while preserving meaningful reminders/escalations configured by the product.
- Recovery closes/resolves the active condition once and sends at most the intended recovery notifications.
- Acknowledgement or manual state changes require permission, tenant scope, audit events, and race-safe updates.
Notification providers
- Provider definitions are scoped to their owning tenant and secrets remain encrypted/redacted.
- Render messages from bounded, escaped data. Do not leak headers, variables, tokens, raw response bodies, or internal errors.
- Email, Slack, PagerDuty, and webhook delivery use bounded timeouts and retries only when safe.
- Webhook destinations use SSRF protection. Inbound callbacks verify signatures when applicable.
- Record delivery outcome and safe provider diagnostics without blocking the monitor’s terminal persistence indefinitely.
Verify
- Unit-test threshold boundaries, state transitions, deduplication, recovery, and partial/missing region behavior.
- Integration-test scheduler ownership, queue routing, worker output, and provider retry/idempotency.
- Test cross-tenant provider/monitor access and secret redaction.
- Use disposable provider endpoints and clean them up; live delivery acceptance remains separate from automated tests.
© supercheck-io, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/monitoring-alerts of supercheck-io/supercheck.
Open the folder on GitHubat commit b08ab53
Compare with similar skills
Supercheck Monitoring Alerts next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Supercheck Monitoring Alerts this skillsupercheck-io/supercheck | 215 | — | ~855 | Automated safety check: Pass | AGPL-3.0 | |
| Kibana Connectorsaspectrr/deer | 405 | — | ~2k | Automated safety check: Pass | MIT | |
| Cx Observability Setupcoralogix/cx-cli | 121 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Tool ConnectorZhixiangLuo/10xProductivity | 479 | — | ~925 | Automated safety check: Pass | MIT | |
| Alerting Irmgrafana/skills | 282 | 1 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Oncall Irmgrafana/skills | 282 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Cx Observability Setup
coralogix/cx-cli
A skill your agent uses when the user asks to "set up monitoring", "configure observability", "onboard new service", "create saved view", "set up notifications", "configure webhook", "set up Slack…
Tool Connector
ZhixiangLuo/10xProductivity
Connect any tool you use at work to your agent — including internal company tools, custom-built systems, deployment portals, incident trackers, internal knowledge bases, HR systems, and commercial…
- Official
Alerting Irm
grafana/skills
Configure Grafana Alerting, Incident Response Management (IRM), and SLOs end-to-end — provisions Grafana-managed and data-source-managed alert rules, contact points (Slack/PagerDuty/email/webhook)…
- Official
Oncall Irm
grafana/skills
Route alerts, run on-call rotations, and drive incidents in Grafana IRM / OnCall — integrations (Alertmanager / Grafana Alerting / generic webhook / PagerDuty), Jinja2 routing + grouping templates…
Sentry Alert Tuner
LeoYeAI/openclaw-master-skills
Reduce Sentry alert fatigue by surgically tuning issue grouping, fingerprint rules, severity mapping, sample rates, before-send filters, sourcemap pipelines, and release-health gates.
More from supercheck-io/supercheck
All 12 skills in this repoSupercheck Security Auth
supercheck-io/supercheck
Work on Supercheck authentication, RBAC, tenant isolation, sessions, API and trigger keys, invitations, project membership, project variables, OAuth, super-admin behavior, SSRF, or…
Supercheck Architecture
supercheck-io/supercheck
Work on Supercheck system architecture, Next.js routes and actions, React data hooks, Drizzle schemas and migrations, app-worker boundaries, or cross-package contracts.
Supercheck Code Review
supercheck-io/supercheck
Review Supercheck staged, unstaged, commit, branch, or pull-request changes for correctness, regressions, security, tenancy, architecture, tests, docs, licensing, and commit/merge/release readiness.
Supercheck Data Storage
supercheck-io/supercheck
Work on Supercheck PostgreSQL data, S3 or MinIO artifacts, signed URLs and asset proxying, retention cleanup, dashboard/report queries, exports, or audit logging.
Supercheck Execution Engine
supercheck-io/supercheck
Work on Supercheck BullMQ queues, schedulers, capacity management, Playwright or k6 execution, monitors, dynamic locations, cancellation, Redis, Kubernetes Jobs, gVisor, or app-worker execution…
Supercheck Feature Implementation
supercheck-io/supercheck
Implement a new or changed Supercheck feature end to end across schema, auth/RBAC, services, routes/actions, UI, queues/workers, CLI/recorder, tests, docs, and deployment contracts.
Related
Categories
Questions about Supercheck Monitoring Alerts
What does Supercheck Monitoring Alerts do?
Work on Supercheck HTTP, ping, or DNS monitors, regional scheduling and aggregation, alert state/history, incidents, or email, Slack, PagerDuty, and webhook notifications. Supercheck Monitoring Alerts is an agent skill from supercheck-io/supercheck. Work on Supercheck HTTP, ping, or DNS monitors, regional scheduling and aggregation, alert state/history, incidents, or email, Slack, PagerDuty, and webhook notifications.
When should I use Supercheck Monitoring Alerts?
Supercheck Monitoring Alerts fits situations like: tasks that involve Monitoring and alerting; tasks that involve Webhooks.
How do I install Supercheck Monitoring Alerts in Claude Code?
Run `npx skills add supercheck-io/supercheck --skill supercheck-monitoring-alerts -a claude-code`. Or copy the skill folder (.agents/skills/monitoring-alerts in supercheck-io/supercheck) into .claude/skills/supercheck-monitoring-alerts in your project. Claude Code loads it when a task matches its description.
How do I install Supercheck Monitoring Alerts in Codex?
Run `npx skills add supercheck-io/supercheck --skill supercheck-monitoring-alerts -a codex`. Or copy the skill folder (.agents/skills/monitoring-alerts in supercheck-io/supercheck) into .agents/skills/supercheck-monitoring-alerts in your project. Codex loads it when a task matches its description.
Can I use Supercheck Monitoring Alerts in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add supercheck-io/supercheck --skill supercheck-monitoring-alerts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/supercheck-monitoring-alerts, .gemini/skills/supercheck-monitoring-alerts, .github/skills/supercheck-monitoring-alerts and .opencode/skills/supercheck-monitoring-alerts in your project.
What does Supercheck Monitoring Alerts need to run?
SKILL.md names no scripts, command-line tools or credentials: Supercheck Monitoring Alerts is instructions for the agent only.
Does Supercheck Monitoring Alerts access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Supercheck Monitoring Alerts safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Supercheck Monitoring Alerts use?
Supercheck Monitoring Alerts is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Supercheck Monitoring Alerts use?
About 855 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Supercheck Monitoring Alerts?
Skills that share tags, products or a category with Supercheck Monitoring Alerts: Kibana Connectors (aspectrr/deer, 405 stars), Cx Observability Setup (coralogix/cx-cli, 121 stars), Tool Connector (ZhixiangLuo/10xProductivity, 479 stars) and Alerting Irm (grafana/skills, 282 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Supercheck Monitoring Alerts?
supercheck-io (a GitHub organization) maintains it in supercheck-io/supercheck, which has 215 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 9, 2026.
Source: supercheck-io/supercheck on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.