net-incident-intake

Normalize freeform user complaints into structured NETTOOLS incident records.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/ekkus93/vscode_skills --skill net-incident-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: net-incident-intake
Source: https://github.com/ekkus93/vscode_skills/tree/main/skills/net-incident-intake
Command: npx skills add https://github.com/ekkus93/vscode_skills --skill net-incident-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalizes a freeform user complaint into a structured NETTOOLS incident record for streamlined triage and follow-up actions.

Core Features & Use Cases

  • Normalize unstructured complaints into a consistent incident payload with inferred fields.
  • Recommend likely downstream NETTOOLS skills such as roaming analysis or DHCP path based on the complaint text.
  • Supports optional context fields (site, reporter, device, timestamps) to enrich the incident.

Quick Start

Provide a freeform incident complaint and optional context to generate a structured NETTOOLS incident record.

Frequently Asked Questions about net-incident-intake

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

FAQPage Schema
How do I convert freeform network complaints into structured incident records?

You can normalize freeform network complaints into structured incident records by extracting inferred fields from unstructured text. This process creates a consistent incident payload for streamlined triage and follow-up actions across wireless mobility and device connectivity scenarios.

What is data normalization for unstructured network incident complaints?

Data normalization for unstructured network incident complaints is the process of parsing freeform user text to extract consistent fields. It turns subjective service degradation reports into a standardized incident payload, enabling automated triage and downstream analysis.

Can I use natural language input to triage wireless mobility and connectivity issues?

Yes, you can use natural language input to triage wireless mobility and connectivity issues. The system extracts relevant incident fields from the freeform complaint text and supports optional context like site, reporter, and device to enrich the structured record.

How do I generate a structured incident record from a user complaint?

To generate a structured incident record from a user complaint, provide the freeform complaint text along with optional context fields such as site, reporter, device, and timestamps. The system extracts the necessary fields and outputs a structured incident payload.

Does this incident intake process recommend follow-up skills for network troubleshooting?

Yes, the incident intake process recommends follow-up skills for network troubleshooting. Based on the complaint text, it suggests likely downstream analysis skills such as roaming analysis or DHCP path investigation to guide your next diagnostic steps.

What context fields are supported when normalizing service degradation complaints?

When normalizing service degradation complaints, the system supports optional context fields including site, reporter, device, and timestamps. Enriching the unstructured complaint with these parameters helps generate a more accurate structured incident payload.