cekura-onboarding
Installation
SKILL.md
Cekura Platform Onboarding
Walk a new user from account to their first verified result — a completed test call with a visible transcript (testing) or a scored production call (observability).
The One Principle
Keep onboarding minimal, but it may only end at a verified working loop — never at "records created".
- Minimal: one high-leverage connection step per provider; everything else (SDK, mock tools, KB, dynamic variables, custom metrics) is deferred to after the first result.
- Verified: onboarding is NOT done when the agent/scenario rows exist. It is done when one test call completed and its transcript is visible (testing), or one call log is ingested and scored (observability). A misconfigured SIP endpoint or unsupported phone number must surface during onboarding, not days later.
Two Paths
Both paths share Phases 0 and 2 (path choice, agent connection) and diverge after that. The first objective is always connecting the agent — there is no separate account/project phase: working tools prove auth, and a missing project is handled inline (projects_list / projects_create) on the way into Phase 2.
- Testing (default) — generate evaluators, run them against the agent in simulation, review results.
- Observability — ingest production call logs, attach metrics, evaluate, review.