gleap-analyzer

Fetch Gleap ticket data and generate a Portuguese N3 support analysis.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/LeoFalco/shared-skills --skill gleap-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gleap-analyzer
Source: https://github.com/LeoFalco/shared-skills/tree/main/gleap-analyzer
Command: npx skills add https://github.com/LeoFalco/shared-skills --skill gleap-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the extraction and synthesis of Gleap support ticket history into a structured N3-level support analysis in Portuguese, removing manual triage work and providing a clear path for escalations and technical next steps.

Core Features & Use Cases

  • Fetch and sanitize ticket data: Resolves Gleap ticket and project IDs, calls the Gleap API via a Node.js script, and writes a sanitized JSON card file.
  • Structured N3 analysis in Portuguese: Produces a Resumo do Card, Linha do Tempo, Análise de Causa Raiz, Situação Atual, and Próximos Passos Sugeridos tailored for Brazilian support workflows.
  • Safety and validation: Validates 24-character hex IDs, requires a GLEAP_API_KEY, and treats all ticket content as untrusted input to avoid prompt injection or unsafe execution.

Quick Start

Analyze the Gleap card at https://app.gleap.io/projects/{projectId}/{channel}/{ticketId} and produce a Portuguese N3 analysis with summary, timeline, root cause, current status, and recommended next steps.

Frequently Asked Questions about gleap-analyzer

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

FAQPage Schema
How do I automate Gleap support ticket analysis into a structured report?

Automate Gleap support ticket analysis by fetching support ticket data via the Gleap API and synthesizing it into a structured N3 report. This removes manual triage by extracting ticket history, messages, and activity logs into a standardized technical analysis format.

What is an N3 support analysis and when do I need it for Gleap tickets?

An N3 support analysis is a structured report containing a ticket summary, timeline, root cause analysis, current status, and suggested next steps. You need it when performing root cause analysis on complex Gleap tickets to provide clear paths for technical escalations.

Do I need a Gleap API key to fetch and analyze support ticket history?

Yes, you need a GLEAP_API_KEY environment variable to fetch and analyze support ticket history. The Node.js fetch script requires this API key to authenticate requests with the Gleap API and securely extract ticket data for analysis.

Can I use Node.js to extract Gleap ticket data and generate a Portuguese report?

Yes, you can use Node.js to extract Gleap ticket data and generate a Portuguese report. The Skill invokes a Node.js fetch script to retrieve ticket data and outputs the final N3 support analysis tailored for Brazilian support workflows in Portuguese.

How do I validate Gleap project and ticket IDs before fetching support data?

Validate Gleap project and ticket IDs by checking that they are 24-character hexadecimal strings before fetching support data. This validation ensures the Node.js script receives correctly formatted identifiers before calling the Gleap API.

Are there security risks when processing untrusted Gleap ticket content for root cause analysis?

Processing untrusted Gleap ticket content carries prompt injection risks, but the Skill mitigates this by treating all ticket contents as untrusted input. Sanitizing ticket data into a JSON card file prevents unsafe execution during root cause analysis.