Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

vibeguard-observe

Sterne27

Forks4

Aktualisiert12. Juni 2026 um 01:43

Use when the user asks for a VibeGuard dashboard, hook health, stats, doctor output, metrics export, or local observability status from the Codex App plugin.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

majiayu000

majiayu000/vibeguard

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Netzwerk- und ComputersystemadministratorenInformatik- und Mathematikberufe·SOC 15-1244

SKILL.md

readonly

name	vibeguard-observe
description	Use when the user asks for a VibeGuard dashboard, hook health, stats, doctor output, metrics export, or local observability status from the Codex App plugin.

VibeGuard Observe

This skill uses VibeGuard's local observability commands through the Codex App plugin bridge. Observability is local-first: use repository scripts and local JSONL logs before discussing external telemetry.

When to Activate

User asks to show a VibeGuard dashboard or GUI.
User asks whether hooks are installed, noisy, slow, warning, blocking, or stale.
User asks for project/global hook stats, health, doctor output, or metrics.
User asks to inspect the VibeGuard website/product page from the plugin.

Red Flags

No custom Codex panel - the documented plugin manifest does not expose a local HTML panel field. Use the generated local dashboard instead.
Runtime/eval collapse - hook health and eval quality are separate surfaces.
Remote telemetry drift - do not enable Prometheus, Victoria, OpenTelemetry, or hosted Sites by default.
Raw data leak - do not paste local logs, prompts, secrets, or full command payloads unless the user explicitly asks and it is safe.

Checklist

Resolve the source checkout with plugins/vibeguard/scripts/vibeguard-plugin.sh repo-dir.
Use dashboard for a local HTML overview.
Use health for recent hook health.
Use stats for project/global trigger summaries.
Use doctor or codex-status for install/capability diagnosis.
Keep setup changes explicit; do not install hooks while answering observe-only requests.

Commands

From a VibeGuard checkout:

bash plugins/vibeguard/scripts/vibeguard-plugin.sh dashboard
bash plugins/vibeguard/scripts/vibeguard-plugin.sh dashboard --no-open --output /tmp/vibeguard-dashboard.html
bash plugins/vibeguard/scripts/vibeguard-plugin.sh health 24
bash plugins/vibeguard/scripts/vibeguard-plugin.sh stats all
bash plugins/vibeguard/scripts/vibeguard-plugin.sh stats --scope global all
bash plugins/vibeguard/scripts/vibeguard-plugin.sh doctor
bash plugins/vibeguard/scripts/vibeguard-plugin.sh metrics-export
bash plugins/vibeguard/scripts/vibeguard-plugin.sh open-site

When running from a plugin cache:

VIBEGUARD_REPO_DIR=/path/to/vibeguard \
  bash scripts/vibeguard-plugin.sh dashboard --no-open

Mehr aus diesem Repository

gleiches Repository

benchmark-regression-triage

majiayu000/vibeguard

Use this skill whenever VibeGuard hook latency, benchmark-action output, GitHub Actions bench-output artifacts, or a suspected performance regression needs investigation. It preserves the PR-to-CI-artifact workflow for comparing recent PRs, older anchors such as PR

2026-06-2127

vibeguard-setup

majiayu000/vibeguard

Use when the user asks to install, verify, inspect, or remove VibeGuard Codex hooks through the Codex App plugin.

2026-06-1227

vibeguard

majiayu000/vibeguard

Use when the user asks Codex to apply VibeGuard anti-hallucination rules, inspect VibeGuard observability, or route a task through VibeGuard preflight/review/check workflows.

2026-06-1227

vibeguard

majiayu000/vibeguard

AI-assisted development of anti-hallucination specifications. Check out the seven-layer defense architecture, quantitative indicators, execution templates and practical cases. Used for code review, task startup inspection, and weekly review.

2026-05-3127

auto-optimize

majiayu000/vibeguard

Automate analysis, evaluation, design and optimization of target projects. Integrate VibeGuard as a baseline scan, the remediation process adheres to VibeGuard specifications, and a compliance check is run at the end. Support auto-run-agent autonomous execution.

2026-05-3127

optflow

majiayu000/vibeguard

Discover and deliver repository optimization work end to end: identify performance/reliability/maintainability/security/dx/cost optimization points, prioritize by impact-effort-risk, then execute fixes step by step with continuous testing and explicit commit policy (`final_only`, `per_step`, `milestone`). Default to `per_step` for implementation work so each feature is tested then committed before the next feature. Supports optional BDD (Given/When/Then).

2026-05-3127

VibeGuard Observe

When to Activate

User asks to show a VibeGuard dashboard or GUI.

User asks whether hooks are installed, noisy, slow, warning, blocking, or stale.

User asks for project/global hook stats, health, doctor output, or metrics.

User asks to inspect the VibeGuard website/product page from the plugin.

Red Flags

No custom Codex panel - the documented plugin manifest does not expose a local HTML panel field. Use the generated local dashboard instead.

Runtime/eval collapse - hook health and eval quality are separate surfaces.

Remote telemetry drift - do not enable Prometheus, Victoria, OpenTelemetry, or hosted Sites by default.

Raw data leak - do not paste local logs, prompts, secrets, or full command payloads unless the user explicitly asks and it is safe.

Checklist

Resolve the source checkout with plugins/vibeguard/scripts/vibeguard-plugin.sh repo-dir.

Use dashboard for a local HTML overview.

Use health for recent hook health.

Use stats for project/global trigger summaries.

Use doctor or codex-status for install/capability diagnosis.

Keep setup changes explicit; do not install hooks while answering observe-only requests.

Commands

From a VibeGuard checkout:

bash plugins/vibeguard/scripts/vibeguard-plugin.sh dashboard bash plugins/vibeguard/scripts/vibeguard-plugin.sh dashboard --no-open --output /tmp/vibeguard-dashboard.html bash plugins/vibeguard/scripts/vibeguard-plugin.sh health 24 bash plugins/vibeguard/scripts/vibeguard-plugin.sh stats all bash plugins/vibeguard/scripts/vibeguard-plugin.sh stats --scope global all bash plugins/vibeguard/scripts/vibeguard-plugin.sh doctor bash plugins/vibeguard/scripts/vibeguard-plugin.sh metrics-export bash plugins/vibeguard/scripts/vibeguard-plugin.sh open-site

When running from a plugin cache:

VIBEGUARD_REPO_DIR=/path/to/vibeguard \ bash scripts/vibeguard-plugin.sh dashboard --no-open