gleap-analyzer

Fetch and analyze Gleap support cards as an N2 support analyst. Use when asked to analyze a Gleap card, review a support ticket, investigate a Gleap issue, or when the user provides a Gleap URL (app.gleap.io). Triggers on: "analyze gleap card", "gleap card", "review this ticket", "investigate this gleap", or any Gleap URL.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "gleap-analyzer" with this command: npx skills add leofalco/gleap-analyzer/leofalco-gleap-analyzer-gleap-analyzer

Gleap Card Analyzer (N2 Support)

Workflow

1. Get the Gleap card URL

Ask the user for the Gleap card URL if not already provided.

URL format: https://app.gleap.io/projects/{projectId}/{channel}/{ticketId}

Extract IDs from URL:

  • ticketId: last path segment (24-char hex)
  • projectId: segment after /projects/ (24-char hex)

2. Fetch card data

Run the fetch script. It may be installed locally or globally, so resolve the path first:

node "$HOME/.claude/skills/gleap-analyzer/scripts/fetch-gleap-card.js" <ticketId> <projectId>

This outputs a gleap-card-<ticketId>.json file in the current directory.

Requires GLEAP_API_KEY in .env. If missing, tell the user to add it.

3. Read and analyze the JSON

Read the generated gleap-card-<ticketId>.json file.

The file contains:

  • ticket: card metadata (title, description, form data, assigned user, channel)
  • messages: chronological conversation notes between support agents
  • activities: activity log events

4. Produce the N2 analysis

Act as an N2 (level 2) support analyst. Write the analysis in Portuguese (pt-BR) since FieldControl is a Brazilian company.

Structure the output as:

Resumo do Card

  • Título do card
  • Canal (email, chat, etc.)
  • Cliente/conta afetada
  • Responsável atual
  • Data de abertura → último update

Linha do Tempo

Chronological summary of key events from messages and activities. For each entry:

  • Date, author, and what happened/was communicated
  • Highlight escalations, blocks, and status changes

Análise de Causa Raiz

Based on the conversation, identify:

  • What is the reported problem
  • What was investigated
  • What was found as root cause (or if still unknown)

Situação Atual

  • Where does the card stand right now
  • What was the last action taken and by whom
  • Is it waiting on someone? Who?

Próximos Passos Sugeridos

Actionable next steps for N2 support, such as:

  • Technical investigations to perform
  • People to contact
  • Scripts or queries to run
  • Escalation recommendations if needed

5. Clean up

After presenting the analysis, ask the user if they want to keep the generated YAML file or delete it.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

claw2ui

Generate interactive web pages (dashboards, charts, tables, reports) and serve them via public URL. Use this skill when the user explicitly asks for data vis...

Registry SourceRecently Updated
General

WeChat Article Summarize

Read one or more WeChat public account article links from mp.weixin.qq.com, extract cleaned full text and optional image links, summarize each article in Chi...

Registry SourceRecently Updated
General

Openfinance

Connect bank accounts to AI models using openfinance.sh

Registry SourceRecently Updated
General

---

合同审查清单AI助手 - 5类合同+3大特殊条款,风险识别与修改建议

Registry SourceRecently Updated