Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
Queries all configured services for health status — uptime, restarts, errors, resources.
Install Vibe Service Health Dashboard
$ npx skills add ash1794/vibe-engineering --skill vibe-service-health-dashboard -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ash1794/vibe-engineering vibe-service-health-dashboard --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/ash1794/vibe-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-service-health-dashboard .claude/skills/vibe-service-health-dashboard && 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 "vibe-service-health-dashboard" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-service-health-dashboard into .claude/skills/vibe-service-health-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-service-health-dashboard", 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/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-service-health-dashboardType 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 ash1794/vibe-engineering --skill vibe-service-health-dashboard -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ash1794/vibe-engineering vibe-service-health-dashboard --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-service-health-dashboard .agents/skills/vibe-service-health-dashboard && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibe-service-health-dashboard" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-service-health-dashboard into .agents/skills/vibe-service-health-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-service-health-dashboard", 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 ash1794/vibe-engineering --skill vibe-service-health-dashboard -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ash1794/vibe-engineering vibe-service-health-dashboard --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-service-health-dashboard .cursor/skills/vibe-service-health-dashboard && 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 "vibe-service-health-dashboard" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-service-health-dashboard into .cursor/skills/vibe-service-health-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-service-health-dashboard", 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/ash1794/vibe-engineering.git --path plugins/vibe-engineering/skills/vibe-service-health-dashboard--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 ash1794/vibe-engineering --skill vibe-service-health-dashboard -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ash1794/vibe-engineering vibe-service-health-dashboard --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-service-health-dashboard .gemini/skills/vibe-service-health-dashboard && 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 "vibe-service-health-dashboard" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-service-health-dashboard into .gemini/skills/vibe-service-health-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-service-health-dashboard", 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 ash1794/vibe-engineering vibe-service-health-dashboardInstalls 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 ash1794/vibe-engineering --skill vibe-service-health-dashboard -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-service-health-dashboard .github/skills/vibe-service-health-dashboard && 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 "vibe-service-health-dashboard" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-service-health-dashboard into .github/skills/vibe-service-health-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-service-health-dashboard", 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 ash1794/vibe-engineering --skill vibe-service-health-dashboard -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ash1794/vibe-engineering vibe-service-health-dashboard --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-service-health-dashboard .opencode/skills/vibe-service-health-dashboard && 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 "vibe-service-health-dashboard" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-service-health-dashboard into .opencode/skills/vibe-service-health-dashboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-service-health-dashboard", 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
vibe-service-health-dashboard- GitHub stars
- 163
- Token cost
- ~486 tokens
- SKILL.md length
- 199 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
Queries all configured services for health status — uptime, restarts, errors, resources.
- Works in 4 steps: Discover services — Check for → For each service, collect → Identify issues → …
- Checking the health of running services
- SKILL.md covers When to Use This Skill, When NOT to Use This Skill, Steps and Output Format
- Calls docker and kubectl
What it does
Vibe Service Health Dashboard is an agent skill from ash1794/vibe-engineering. Queries all configured services for health status — uptime, restarts, errors, resources. Use when checking the health of running services.
Its SKILL.md is about 490 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. The repository describes itself as: 33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development. Born from… The licence is MIT.
When your agent uses it
- Checking the health of running services
Example prompts
- “Use the vibe-service-health-dashboard skill to query all configured services for health status — uptime, restarts, errors, resources”
- “/vibe-service-health-dashboard”
Requirements
- Docker
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Discover services — Check for
- For each service, collect
- Identify issues
- Provide remediation commands for each issue
What it can do on your machine
Read from SKILL.md and the folder at commit 8f1d71b. 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
Shell commands in SKILL.md call:
dockerkubectl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker and kubectl, which can reach the network depending on how they are called.
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
Vibe Service Health Dashboard loads about 486 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 199 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 ash1794/vibe-engineering at commit 8f1d71b, republished under its MIT licence (© ash1794). 199 words, ~486 tokens.
Download SKILL.mdSave it as
.claude/skills/vibe-service-health-dashboard/SKILL.md (or your agent's skills folder).- name
- vibe-service-health-dashboard
- description
- Queries all configured services for health status — uptime, restarts, errors, resources. Use when checking the health of running services.
- user-invocable
- true
vibe-service-health-dashboard
Know what's running, what's crashed, and what's about to crash.
When to Use This Skill
- Checking service health after deployment
- Investigating performance or availability issues
- Morning standup health check
- After infrastructure changes
When NOT to Use This Skill
- No services running (pure library/CLI project)
- Already have a monitoring dashboard (Grafana, Datadog, etc.)
- Development-only local services that don't need monitoring
Steps
Discover services — Check for:
- systemd:
systemctl --user list-units --type=service --state=running - Docker:
docker ps - PM2:
pm2 list - Kubernetes:
kubectl get pods
- systemd:
For each service, collect:
- Status (running/stopped/crashed)
- Uptime
- Last restart time and reason
- Recent error count (from logs)
- Resource usage (CPU, memory) if available
Identify issues:
- Crashed services (not running when expected)
- High-restart services (restarted >3 times recently)
- Resource-hungry processes (>80% CPU or memory)
- Error spikes (more errors than usual)
Provide remediation commands for each issue
Output Format
Service Health Dashboard
Services: X running, Y stopped, Z error Overall: HEALTHY / DEGRADED / CRITICAL
| Service | Status | Uptime | Restarts | Errors (1h) | CPU | Memory |
|---|---|---|---|---|---|---|
| api | ✓ Running | 3d 4h | 0 | 2 | 15% | 256MB |
| worker | ✗ Crashed | - | 5 | 38 | - | - |
Issues
- worker crashed — Last error: "OOM killed"
- Fix:
systemctl --user restart workeror increase memory limit
- Fix:
Recommended Actions
- [Action with command]
© ash1794, MIT. 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 plugins/vibe-engineering/skills/vibe-service-health-dashboard of ash1794/vibe-engineering.
Open the folder on GitHubat commit 8f1d71b
Compare with similar skills
Vibe Service Health Dashboard 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 |
|---|---|---|---|---|---|---|
| Vibe Service Health Dashboard this skillash1794/vibe-engineering | 163 | — | ~486 | Automated safety check: Pass | MIT | |
| Monitor CInrwl/nx | 29k | 6 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Terraform and OpenTofu Guideagentscope-ai/QwenPaw | 36k | 6 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Terraform and OpenTofu Guide
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
- Official
Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
Docs Learn PR Preview
netdata/netdata
Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.
More from ash1794/vibe-engineering
All 33 skills in this repoVibe Concurrent Test Safety
ash1794/vibe-engineering
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.
Vibe Fuzz Parser Inputs
ash1794/vibe-engineering
Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).
Vibe Golden File Testing
ash1794/vibe-engineering
Implements snapshot/golden file tests with temporal normalization so tests don't break daily.
Vibe Parallel Task Decomposition
ash1794/vibe-engineering
Analyzes large tasks for independent subtasks that can be safely parallelized.
Vibe Slop Filter
ash1794/vibe-engineering
Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).
Vibe Spec Sync
ash1794/vibe-engineering
Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.
Related
Categories
Questions about Vibe Service Health Dashboard
What does Vibe Service Health Dashboard do?
Queries all configured services for health status — uptime, restarts, errors, resources. Vibe Service Health Dashboard is an agent skill from ash1794/vibe-engineering. Queries all configured services for health status — uptime, restarts, errors, resources.
When should I use Vibe Service Health Dashboard?
Vibe Service Health Dashboard fits situations like: checking the health of running services.
How do I install Vibe Service Health Dashboard in Claude Code?
Run `npx skills add ash1794/vibe-engineering --skill vibe-service-health-dashboard -a claude-code`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-service-health-dashboard in ash1794/vibe-engineering) into .claude/skills/vibe-service-health-dashboard in your project. Claude Code loads it when a task matches its description.
How do I install Vibe Service Health Dashboard in Codex?
Run `npx skills add ash1794/vibe-engineering --skill vibe-service-health-dashboard -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-service-health-dashboard in ash1794/vibe-engineering) into .agents/skills/vibe-service-health-dashboard in your project. Codex loads it when a task matches its description.
Can I use Vibe Service Health Dashboard 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 ash1794/vibe-engineering --skill vibe-service-health-dashboard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-service-health-dashboard, .gemini/skills/vibe-service-health-dashboard, .github/skills/vibe-service-health-dashboard and .opencode/skills/vibe-service-health-dashboard in your project.
What does Vibe Service Health Dashboard need to run?
Going by SKILL.md and its folder, Vibe Service Health Dashboard needs the command-line tools its instructions call (docker and kubectl). Our summary lists: Docker.
Does Vibe Service Health Dashboard access the network?
SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Vibe Service Health Dashboard 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 Vibe Service Health Dashboard use?
Vibe Service Health Dashboard is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vibe Service Health Dashboard use?
About 486 tokens (SKILL.md is roughly 1.9k 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 Vibe Service Health Dashboard?
Skills that share tags, products or a category with Vibe Service Health Dashboard: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 36k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibe Service Health Dashboard?
ash1794 (a GitHub user) maintains it in ash1794/vibe-engineering, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.
Source: ash1794/vibe-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.