dialogue-trigger

Detect repeated errors and prompt interactive dialogue resolution via AskUserQuestion.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/amijadoamijado/sd003 --skill dialogue-trigger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dialogue-trigger
Source: https://github.com/amijadoamijado/sd003/tree/main/.gemini/skills/dialogue-trigger
Command: npx skills add https://github.com/amijadoamijado/sd003 --skill dialogue-trigger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects repeated or non-converging errors and prompts an interactive dialogue resolution path.

Core Features & Use Cases

  • Trigger-based proposal: Monitors repeated errors and user mentions to prompt a diagnostic dialogue.
  • Non-executing guidance: Provides decision support without executing any remediation.
  • Use Case: When errors recur across attempts or progress stalls, the system suggests entering a dialogue-driven resolution path with the user.

Quick Start

Prompt the user to initiate the dialogue-resolution path when error recovery stalls.

Frequently Asked Questions about dialogue-trigger

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

FAQPage Schema
How do I trigger an interactive dialogue when repeated error fixes keep stalling?

Interactive dialogue is triggered when the same error occurs two or more times or users report confusion, prompting a diagnostic resolution path using AskUserQuestion to obtain explicit consent before transitioning.

What is a dialogue-driven approach for non-converging error resolution?

A dialogue-driven approach provides non-executing guidance for non-converging errors, offering decision support and prompting a diagnostic path rather than automatically executing remediation actions.

How do I get user consent before entering a diagnostic dialogue path?

You obtain user consent by implementing AskUserQuestion, which prompts the user and waits for explicit agreement before transitioning into the interactive dialogue resolution path.

Can I use this interactive guidance to resolve errors without executing automated fixes?

Yes, this interactive guidance provides decision support without executing any remediation, meaning it suggests a dialogue-driven resolution path rather than directly modifying your system to fix errors.

When should I prompt for a dialogue-based error resolution path instead of retrying?

You should prompt for a dialogue-based resolution path when error recovery stalls, specifically when the same error recurs two or more times or when users report confusion during troubleshooting.

Does interactive dialogue resolution work for errors that occur only once?

Interactive dialogue resolution is designed for repeated or non-converging errors, applying explicitly when the same error occurs two or more times, rather than triggering on single occurrences.