replio-project-setup13 KB
View saved version →
---
name: replio-project-setup
description: "Guides users end to end through creating, reviewing and managing Replio AI voice-training projects with the Replio MCP tools: naming the project, adding knowledge (pasted text, web pages, file uploads), agreeing training goals (grounded in the CRM pipeline digest when a CRM is connected), generating and reviewing AI personas, building the quiz, activating the project, configuring its features, inviting trainees, and reading training results (KPIs, recent activity); for managers also the contact library and groups, trainee management, phone training (Replio Call), Replio Live knowledge contexts, the Knowledge Library, reports, usage and the manager team. Use whenever the Replio connector is available and the user wants to set up, change or report on a training project or their Replio workspace (\"create a sales training from our product sheet\", \"did my team train yesterday?\", \"make this persona more skeptical about price\", \"enrol the Lisbon group in the project\", \"turn on phone training\")."
---
# Replio guided project setup
Replio is an AI voice-training platform: trainees practice real conversations
with AI personas in live voice sessions on replio.eu and receive scored
feedback. This connection sets up and manages training projects; the voice
sessions themselves happen on replio.eu, never in this chat.
Live tool schemas and tool results always win over this text. Tools appear as
`replio:<name>` (some clients show `mcp__replio__<name>`). If they are missing,
the server is not connected: see
[references/mcp/clients.md](references/mcp/clients.md).
## Your role
You are the guide and collector. Replio's own pipeline is the extractor of
record: always send the user's ORIGINAL content to knowledge tools, never your
own summary, and never invent knowledge the user did not provide.
## Three kinds of connection
- **Manager** (signed in with a Replio account): every project of their
organizations; may `create_project`. Only this connection has the workspace
tools (contacts, trainees, phone training, Replio Live, Knowledge Library,
organization); see "Manager workspace" below.
- **Setup code** (a client pasted a `REPLIO-XXXX-XXXX-XXXX` code shared by a
Replio manager): ONE pre-created project, read and write, no
`create_project`.
- **Read code**: ONE project, reporting only.
`list_projects` shows what the connection can reach. Never ask for a token or
a code in chat; the consent page collects it.
## Known situations
For a sales objection drill, a support escalation, interviewer practice or a
language conversation, open the matching recipe in
[references/recipes/](references/recipes/) first: it lists what to collect,
the goals to propose and the `businessContext` shape, then hands over to the
flow below.
## Setup flow, in order
1. **Name the project.** Ask what to call the training, then
`set_project_details` (managers may `create_project` first, with the
training `language` and, for a standard scenario, a `templateId` from
`list_project_templates`).
2. **Add knowledge (optional).**
- Files (PDF, Word, PowerPoint, Excel, images): call `get_upload_link` and
give the user the link. Tell them to upload there, wait for the page to
confirm each file, then come back and say so. NEVER paste text you
extracted from a file into `add_knowledge_text`: uploaded files go through
Replio's full parsing pipeline (layout, tables, figures), pasted
extractions do not.
- Text the user typed or pasted in chat: `add_knowledge_text` with their
original words.
- Public web pages: `add_knowledge_url`.
- No materials? Say the training will be built from a standard template
plus the context they describe, and go straight to the goals step.
- Language learning: a document can simply be the conversation topic in the
target language (any subject works).
3. **Wait without bothering the user.** Call `get_project_setup_status` with
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 7 — file references are metadata, not package contents.
replio-session-analyst6.68 KB
View saved version →
---
name: replio-session-analyst
description: "Turns Replio voice-session results into reports a manager can act on, using the Replio MCP read tools: a weekly team report, a coaching note for one trainee, or a review of which personas need attention. Use whenever the Replio connector is available and the user asks how a trainee or a team is doing, wants a report or a summary of training sessions, asks why a score is what it is, or wants to know which scenario or persona to look at (\"how did Anna do this week?\", \"weekly report for the sales training\", \"which persona is giving everyone trouble?\")."
---
# Replio session analyst
Replio is an AI voice-training platform: trainees practice conversations
with AI personas and every session is scored. This skill reads those results
through the Replio MCP tools and writes reports. It changes nothing; project
setup and persona edits belong to the `replio-project-setup` skill of this
plugin.
Live tool schemas and tool results always win over this text. Tools appear
as `replio:<name>` (some clients show `mcp__replio__<name>`).
## The data
- `list_projects`: the projects this connection can reach; every other tool
needs a project id.
- `get_project_kpis`: totals for one project (sessions, completed sessions,
average score, trainee counts, first-versus-recent progression).
- `get_recent_activity`: per-trainee counts and averages over the last
`days` (1 to 30).
- `list_sessions`: one row per session over the last `days` (default 7, max
90), newest first, with `score`, `metric_scores`, `evidence_level`,
`conversation_outcome`, `scoring_override`, `is_incomplete`, `analyzed`.
Paged: `hasMore` and `nextCursor`. Optional `traineeEmail`.
- `get_session`: one session with its analysis (summary, strengths,
improvements, score breakdown, skill scores, key moments) and the
trainee's goal. Expert sessions return a `recap` instead.
- `get_session_transcript`: the conversation turns. Manager connections
only; access codes do not see this tool.
- Manager connections also have `list_project_trainees` (status, session
count, average score and last activity per trainee, paged max 50; page to
the end before any count), `get_trainee` (one trainee's aggregate stats,
top strengths and improvement areas, 10 most recent sessions) and
`get_project_report` (the printable report's numbers: headline stats,
per-trainee rows, team skill averages). Use them for a team or coaching
report instead of rebuilding the aggregates from `list_sessions`; the CSV
export stays on the dashboard.
## How a score is made
Say these facts when they explain a number; never recompute a score.
- The score is 1 to 10: 70 percent post-session analysis of five metrics
(`responseRelevance`, `objectionHandling`, `rapport`, `clarity`,
`persistence`, each 1 to 10; their meaning is adapted per training type),
30 percent live coaching momentum when live feedback was on.
- `evidence_level` is low, medium or high, from session length, exchanges
and how much the trainee said. Sessions under 60 seconds are capped at 5
(`is_incomplete: true`); a session where the trainee said almost nothing
is capped at 2.
- `scoring_override` is `failure` (capped at 4) or `success` (floored at 8)
when the scenario's own success or failure condition was met, applied only
on high-evidence sessions; on lower evidence the verdict is shown but the
score stands. `get_session` returns the one-sentence reason.
- `conversation_outcome` (closed, satisfied, interested, not_interested) is
how the persona ended up; it does not enter the score.
- Expert sessions (`mode: "expert"`) are question-and-answer sessions with
no score; `analyzed: true` means their recap is ready.
## Rules
1. **Numbers come from tool results only.** Page `list_sessions` to the end
(`hasMore: false`) before stating any count, average or "nobody trained".
If a page limit stops you, say how many sessions the report covers.
2. **Averages ex
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 4 — file references are metadata, not package contents.