retell

Name: retell
Author: gracebotly

github.com/gracebotlyData & databases056 installsUpdated 31w ago

About retell

Retell Platform Skill describes how Retell voice-agent call data is normalized for Getflowetic dashboards. It defines call metrics, field mappings, and dashboard templates for performance and quality monitoring.

Key features

01Call volume and success metrics
02Average duration tracking
03Agent and disconnect breakdowns
04Event field normalization mapping
05Voice analytics dashboard templates

Use cases

01Monitoring call volume and success rates
02Comparing performance across agents
03Reviewing disconnect trends and duration outliers

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gracebotly/flowetic-app --skill retell

After installing, type/retellin Claude Code to confirm it loaded.

Bundled filesfield-semantics.yaml

Details

From the project README

Retell Platform Skill

Overview

Retell is a conversational AI platform for building voice agents. Users connect Retell agents to Getflowetic to monitor call quality, track agent performance, and analyze conversation patterns.

Vocabulary

call: A single voice interaction between a Retell agent and a caller
agent: A configured Retell voice agent with an LLM backend and voice
call_status: Call outcome — ended or completed (success) vs other (failure)
disconnect_reason: Why the call ended (agent_hangup, user_hangup, error, silence, max_duration)
duration_ms: Call length in milliseconds
start_timestamp / end_timestamp: Unix timestamps for call timing

Key Metrics for Dashboards

Call Volume: Total calls over time — trend chart on started_at
Success Rate: Percentage of calls with successful outcome — hero stat
Avg Duration: Average call length in ms — supporting metric card
Agent Breakdown: Calls per agent — pie chart on agent_name/workflow_name
Disconnect Reasons: Why calls end — pie chart for quality monitoring

Event Field Mapping

The Retell import route normalizes call data into the standard event schema. These are the fields that appear in event.state:

Event Field	Semantic Type	Dashboard Use
workflow_id	identifier	Maps to agent_id — count only
workflow_name	dimension	Maps to agent_name — breakdown charts
execution_id	surrogate_key	Maps to call_id — "Total Calls" KPI
status	dimension	Success rate percentage — hero stat
duration_ms	measure (avg)	"Avg Call Duration" metric card
started_at	time_dimension	Timeseries trend axis
ended_at	time_dimension	Detail only
platform	constant	Always "retell" — skip

These fields also appear in event.labels:

agent_id, agent_name, call_id, status

Dashboard Templates

voice-analytics: Call volume trend, success rate, avg duration, agent breakdown
agent-performance: Per-agent comparison, disconnect reasons, quality metrics
quality-monitor: Disconnect reason trends, error rates, duration outliers

Mapping Heuristics (Legacy Aliases)

call_status → status
agent_id → workflow_id
agent_name → workflow_name
call_id → execution_id

Comments

Markdown supported

Details

Author: gracebotly
Repository: gracebotly/flowetic-app
Category: Data & databases
Installs: 56
GitHub stars: 0

Report

More skills

All skills

hyperframes-core

github.com/heygen-com

930.7k

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.

lark-base

open.feishu.cn

834.8k

Operate on Feishu Base: create tables, fields, records, and views; handle statistics, formulas/lookups, forms, dashboards, app mode (BaseApp/AppMode pages and components), Workspace directories, workflows, role permissions, and the template center (Base template categories, lists, and search). Use when encountering Base/multidimensional tables/bitable, BaseApp/AppMode, or /base/ or /app/ links. Do not use lark-apps for BaseApp; route file import/export to lark-drive and authentication/authorization to lark-shared.

lark-sheets

open.feishu.cn

833.3k

Feishu Spreadsheets: create and operate spreadsheets. Supports worksheets and row/column structures (add/delete/merge/size/hide/freeze/group), cell read/write (values/formulas/styles/comments/cell images), range copy/move/sort/fill, find and replace, bulk updates, and creating and maintaining objects such as charts, pivot tables, conditional formatting, filters and filter views, dropdown lists, sparklines, and floating images. Also supports formula validation, restoring historical versions, and importing/exporting local Excel/CSV files and Feishu spreadsheets. Use when users need to create or edit spreadsheets, summarize and visualize data, format spreadsheets, calculate formulas (including migrating Excel formulas), or build financial models (DCF, three statements, budgets, Sensitivity, etc.). For multidimensional tables (Base/bitable), use lark-base. If users want to search for spreadsheet files in cloud storage (Drive/cloud storage) by name or keyword, use lark-drive's drive +search to locate resources first. When users provide a doubao.com /sheets/ URL/token, use this skill directly; do not fall back to WebFetch because the domain is not Feishu. Routing is based on the URL path pattern and token, not the domain.

remotion-best-practices

github.com/remotion-dev

714.8k

Best practices and domain knowledge for building videos programmatically with Remotion (videos in React/TypeScript, rendered to MP4). Use whenever writing or editing Remotion code — scaffolding a video project, animating with interpolate/spring over useCurrentFrame(), sequencing scenes and transitions, captions/subtitles, audio, GIFs/Lottie/3D, charts, visual effects, dynamic duration via calculateMetadata, or rendering. Consult before reaching for a Remotion API, since its components and props evolve (e.g. @remotion/media).