Session analyst
Skill tough-tongue/toughtongue-skills/skills/session-analyst
Analyze Tough Tongue AI practice-session performance and build reports via the ttai MCP server. Pulls sessions with scores, strengths, and weaknesses, aggregates patterns across a team or scenario, and produces structured reports with improvement areas and action items. Use when the user asks "how is my team doing?", "top improvement areas for scenario X", "pull the lowest-scoring sessions", "build me a coaching report", "session trends this month", or wants session data turned into a deck, email, or dashboard.From its SKILL.md
npx -y skills add tough-tongue/toughtongue-skills --skill session-analystAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
6.5 KB, as published. Nobody here has run it
Session Analyst
Pull session data → aggregate patterns → produce a structured report → optionally hand off to slides/email tools for distribution.
Prerequisites
- The ttai MCP server must be connected. Tool references below use the
ttai:server prefix (e.g.ttai:list_sessions); some agents surface these asmcp__ttai__list_sessions. If the tools are missing, point the user at the repo README to install the plugin or add the MCP server — the client runs a browser OAuth login on first use.
Data model (what a session gives you)
Each session from ttai:list_sessions / ttai:get_sessions_batch includes:
- Identity:
scenario_id,scenario_name,user_name,user_email - Lifecycle:
status,created_at,completed_at,duration_minutes evaluation_results:final_score,strengths,weaknesses, andreport_card[]— per-topic{topic, score, note, weight}improvement_results:improvement_areas,action_items,resourcesextraction_results: structured variables (if the scenario extracts them)transcript_url(signed URL — fetch it for the conversation text) andanalytics_url(human-viewable analysis page)
report_card topics are the backbone of aggregation: they are consistent
within a scenario because they come from its rubric.
Workflow
Step 1: Scope
- Call
ttai:list_organizations. Team analysis almost always needs anorg_id— pass it on every call, along withis_org: trueonttai:list_sessionsfor org-wide data. - Resolve the scenario:
ttai:list_scenariosif the user gave a name, not an ID. - Confirm the window and population: which scenario(s), which date range
(
from_date/to_date), which people (user_emailfilter), how many sessions.
Step 2: Pull
ttai:list_sessionswithscenario_id, date filters, and pagination (page,limit). Iterate pages until you have the requested population — check the page metadata rather than assuming one page is everything.- Sessions missing
evaluation_results: either exclude them from scoring aggregates (note the count), or backfill — callttai:post_process_sessionfor each, then re-fetch after a wait and check thatevaluation_resultsappeared. Backfill only when the user needs completeness. - Deep dives (outliers, disputed scores):
ttai:get_sessions_batchwith the session IDs, then fetchtranscript_urlcontents for the actual conversation.
Step 3: Aggregate
Compute, at minimum:
- Score distribution: mean, median, range of
final_score; flag the count of unanalyzed sessions excluded. - Per-topic breakdown: average
report_cardscore per topic, weighted byweight. The lowest topics are the improvement areas. - Recurring weaknesses: cluster
weaknessesandimprovement_areastext across sessions into themes; count occurrences. Name each theme by the behavior, not an abstraction ("jumps to price before discovery" beats "communication issues"). - Trend: score over time if the window is long enough (week buckets work well); per-person averages for team views.
- Evidence: for each top theme, pull 1-2 short transcript quotes from representative sessions. Reports without evidence read as opinion.
For org-wide rollups (usage, member breakdown, time series),
ttai:get_analytics with is_org_wide: true complements per-session
aggregation.
Step 4: Report
Use the matching template from references/report-templates.md:
- Team performance report — "how is my team doing?"
- Scenario health report — "is this scenario working?" (pairs with the scenario-refiner skill when the answer is no)
- Individual coaching report — one person, one skill gap, action items
Always include: population and window, score summary, top 3-5 improvement
areas with evidence, concrete action items, and analytics_url links for
sessions worth reviewing by a human.
Step 5: Distribute (optional)
If the user wants a deck, email, or document, hand the report content to their connected tools (slides MCP, email MCP, docs). Keep the structure: one improvement area per slide/section, evidence quote included.
Recipes
"Top 5 improvement areas for scenario X, last 50 sessions"
ttai:list_scenarios (resolve ID) → ttai:list_sessions (scenario_id,
limit 50, org context) → aggregate report_card topics + weakness themes →
Team performance report → deck if asked.
"Pull the 5 lowest-scoring sessions and find out what went wrong"
ttai:list_sessions (scenario_id + window) → sort by
evaluation_results.final_score ascending, take 5 →
ttai:get_sessions_batch → fetch transcripts → diagnose common failure
patterns → if the fault is in the scenario (not the users), hand off to the
scenario-refiner skill with the diagnosis.
"How did [person] do this month?"
ttai:list_sessions (user_email + from_date) → per-topic averages, trend
across their sessions → Individual coaching report with action items from
improvement_results.
Automated post-call coaching (webhook-driven)
For teams wiring this into pipelines (e.g. every real sales call gets a
coaching report): see the recipe in
references/report-templates.md —
ttai:create_session ingests an external transcript against a coaching
scenario, ttai:post_process_session triggers analysis, poll until
evaluation_results appears, then format and send the report.
Pitfalls
- Don't average across different scenarios' report cards — topics and weights differ per rubric. Aggregate per scenario, compare qualitatively.
- Small samples: below ~10 analyzed sessions, report observations, not statistics — and say so.
- Session status: only
completedsessions have meaningful duration and results; excludein_progressandfailedfrom aggregates. - Privacy: coaching reports name individuals. Confirm the audience before distributing anything per-person to a group channel.
What ships with it: 2 files
4.2 KB alongside SKILL.md
agents/
- openai.yaml456 B
references/
- report-templates.md3.8 KB
Gives 0 of the 12 instructions most research analysis skills give
Counted across 1,213 of the 2,113 authors here whose files we hold, read 2026-09-06
- Cite sources for every important claimin 47 of 1213, across 38 files
- Separate facts from inferences and recommendationsin 21 of 1213, across 12 files
- Write findings to a markdown filein 19 of 1213
- Label every insight with a confidence levelin 18 of 1213, across 8 files
- Read product marketing context before asking questionsin 18 of 1213, across 8 files
- Rank themes by frequency and intensityin 16 of 1213, across 6 files
- Establish research mode before proceedingin 16 of 1213, across 6 files
- Segment survey responses by customer tier or tenurein 16 of 1213, across 6 files
- Categorize support tickets before analyzingin 16 of 1213, across 6 files
- Weight research sources from the last twelve monthsin 16 of 1213, across 6 files
- Use at least five data points per segmentin 15 of 1213, across 5 files
- Extract verbatim quotes for all research findingsin 15 of 1213, across 5 files
Said here and by no other author read
- Connect to the ttai MCP server
- Resolve scenario names to IDs
- Filter sessions by date and population
- Iterate through all session pages
- Backfill missing evaluation results if needed
- Aggregate scores and report card topics
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.