posthog-ticket-intake

Name: posthog-ticket-intake
Availability: InStock
Author: mongo-ai

Parse support tickets into structured markdown summaries with extracted identifiers.

Updated Aug 27, 2026

Search Tags:#ticket #triage #posthog #intake #issue-classification #identifier-extraction

Ready to run

npx skills add https://github.com/mongo-ai/posthog-triage-agent --skill posthog-ticket-intake

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: posthog-ticket-intake
Source: https://github.com/mongo-ai/posthog-triage-agent/tree/main/.claude/skills/posthog-ticket-intake
Command: npx skills add https://github.com/mongo-ai/posthog-triage-agent --skill posthog-ticket-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Support engineers waste time parsing unstructured ticket text; this skill converts raw tickets into a consistent, machine‑readable format with key identifiers, product area guesses, and next‑step recommendations.

Core Features & Use Cases

Issue classification: Detects primary issue type (bug, how‑to, feature request, etc.).
Context extraction: Pulls distinct IDs, URLs, time windows, plan tier, and environment clues.
Actionable output: Generates a markdown summary and suggests the first diagnostic skill to run, while automatically kicking off parallel evidence searches.

Quick Start

Ask the ticket intake skill to process the following support message and return the normalized summary.

Frequently Asked Questions about posthog-ticket-intake

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

FAQPage Schema

How do I normalize raw support tickets into structured investigation inputs?▼

Normalizing raw support tickets involves parsing unstructured text to classify the issue type, extract distinct IDs, URLs, timeframes, and environment clues, and generate a markdown summary with diagnostic path recommendations.

What is the best way to automate ticket triage for PostHog support issues?▼

Automating ticket triage for PostHog support issues requires parsing incoming ticket text to identify the product area, extract identifiers, and recommend diagnostic paths while kicking off parallel evidence searches.

How does issue classification work for unstructured support ticket text?▼

Issue classification for unstructured support ticket text works by parsing the message to detect the primary issue type, such as a bug, how-to question, or feature request, and converting it into a consistent machine-readable format.

Can I extract URLs and identifiers from customer support tickets automatically?▼

You can automatically extract distinct IDs, URLs, time windows, plan tier, and environment clues from raw support ticket text to create structured investigation inputs for support engineers.

Does ticket intake processing work without external dependencies?▼

Ticket intake processing works without external dependencies, parsing raw text internally to classify issues, extract identifiers, and generate markdown output with parallel search triggers for diagnostic workflows.

What are the limitations of automated issue classification for support tickets?▼

Automated issue classification relies on parsing raw ticket text, meaning highly ambiguous or incomplete messages may limit the accuracy of product area identification and diagnostic path recommendations for support engineers.