fault_diagnosis

Orchestrate FAE fault-diagnosis API start, poll, and query in one call.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/huangxn27/broadband-agent-demo --skill fault-diagnosis-huangxn27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fault_diagnosis
Source: https://github.com/huangxn27/broadband-agent-demo/tree/main/backend/skills/fault_diagnosis
Command: npx skills add https://github.com/huangxn27/broadband-agent-demo --skill fault-diagnosis-huangxn27

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill wraps the FAE fault-diagnosis API into a single tool call that internally orchestrates start, poll, and query, returning the current fault diagnosis results for the active scenario.

Core Features & Use Cases

  • End-to-end orchestration: start → poll → query is handled inside the skill, returning a structured diagnosis payload.
  • Multi-scenario support: handles NETWORK_ACCESS_SLOW, NETWORK_ACCESS_FAILURE, LIVE_STUTTERING, GAME_STUTTERING contexts.
  • Structured output: returns taskId, status, scenario, queryType, queryValue, and diagnoseResult; logs during start/poll go to stderr for clean stdout.

Quick Start

Invoke the fault_diagnosis tool with the required scenario, query-type, and query-value arguments to start a diagnostic task and fetch results.

Frequently Asked Questions about fault_diagnosis

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

FAQPage Schema
How do I orchestrate end-to-end network fault diagnosis across multiple scenarios?

End-to-end network fault diagnosis is orchestrated by wrapping the FAE API to handle start, poll, and query stages in a single call, returning a structured diagnosis payload for scenarios like NETWORK_ACCESS_SLOW and NETWORK_ACCESS_FAILURE.

Can I automate provisioning fault diagnosis from the command line?

Provisioning fault diagnosis can be automated via CLI argument construction, managing tokens through fae_poc, and executing multi-stage orchestration that outputs structured results to stdout while emitting progress logs to stderr.

What scenarios are supported by FAE fault diagnosis for troubleshooting flows?

FAE fault diagnosis supports troubleshooting flows for NETWORK_ACCESS_SLOW, NETWORK_ACCESS_FAILURE, LIVE_STUTTERING, and GAME_STUTTERING scenarios, returning specific diagnoseResult fields for each active context.

How do I get structured diagnostic results without CLI progress logs polluting the output?

Structured diagnostic results containing taskId, status, scenario, and diagnoseResult are returned cleanly to stdout, while all multi-stage orchestration progress logs during start and poll phases are redirected to stderr.

Do I need to manually manage API tokens when running FAE fault diagnosis queries?

Manual token management is not required for FAE fault diagnosis queries; the skill internally handles token management via fae_poc while orchestrating the start, poll, and query lifecycle automatically.

What is the best way to diagnose live streaming and game stuttering issues?

Diagnosing LIVE_STUTTERING and GAME_STUTTERING issues is handled by invoking the fault diagnosis tool with the specific scenario, query-type, and query-value arguments to fetch the current structured diagnosis payload.