trigger-diagnostics

Diagnose Supervibe trigger routing failures and produce structured next actions.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill trigger-diagnostics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trigger-diagnostics
Source: https://github.com/vTRKA/supervibe/tree/main/skills/trigger-diagnostics
Command: npx skills add https://github.com/vTRKA/supervibe --skill trigger-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Trigger Diagnostics explains why a Supervibe trigger, command route, or skill handoff did not match what you expected, including missing evidence, intent mismatches, confidence issues, and safety or validation blockers.

Core Features & Use Cases

  • Route and intent diagnosis: Determine whether the issue is a corpus/keyword gap, an intent mismatch, or an incorrect skill selection.
  • Missing-artifact and safety blocker reporting: Identify exactly which required artifacts or gate conditions are absent and what must be provided before proceeding.
  • Actionable next step for fixes: Produce bounded outputs that either request one missing input, recommend the smallest metadata/corpus repair, or stop until proof is available.
  • Read-only diagnostics discipline: Prevent premature claims of completion and avoid bypassing the owning command or reviewer.

Quick Start

Use the trigger-diagnostics skill to diagnose an unexpected routing outcome by describing the exact user phrase and providing any available plan, handoff, or receipt evidence.

Frequently Asked Questions about trigger-diagnostics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose why a trigger route was blocked unexpectedly?

To diagnose a blocked trigger route, describe the exact user phrase and provide any available plan, handoff, or receipt evidence so the diagnostic process can evaluate intent mismatches, missing artifacts, and safety blockers to produce a structured next action.

What causes a command route to hand off to the wrong skill?

Command routes hand off to the wrong skill due to corpus or keyword gaps, intent mismatches between the user phrase and available commands, or incorrect skill selections that diagnostic analysis identifies through confidence scoring and matched phrase evaluation.

How do I identify missing artifacts preventing a workflow from proceeding?

Identify missing artifacts by running a diagnostic evaluation against the trigger request, which reports exactly which required artifacts or gate conditions are absent and specifies what must be provided before the workflow can proceed.

Can I use diagnostic confidence scoring to fix intent mismatches?

Yes, diagnostic confidence scoring evaluates intent, command, and skill alignment to isolate whether an intent mismatch stems from a corpus gap or a keyword problem, then recommends the smallest metadata or corpus repair needed to restore correct routing.

What should I do when a safety gate stops my command execution?

When a safety gate stops command execution, the diagnostic output reports the specific safety blockers present and produces a bounded next action that either requests one missing input or stops until the required proof is available.

Does trigger routing diagnosis modify the workflow or operate read-only?

Trigger routing diagnosis operates with read-only discipline, meaning it prevents premature claims of completion and avoids bypassing the owning command or reviewer while producing structured evidence-based recommendations for fixes.