CtrlK
BlogDocsLog inGet started
Tessl Logo

cekura-onboarding

Use when the user says "get started with Cekura", "set up Cekura", "onboard to Cekura", "I'm new to Cekura", "help me set up my agent", "how do I use Cekura", "walk me through Cekura", "configure my project", "first time using Cekura", or needs guidance on initial platform setup, or types the command /cekura-onboarding. Not for adding an agent, more scenarios or more metrics to an existing workspace — those are cekura-create-agent, cekura-eval-design and cekura-metric-design. Covers two onboarding paths: **testing** (default — build evaluators and run simulated calls) and **observability** (ingest production call logs and evaluate them).

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, lean orchestrator with a clear phase sequence, explicit verification gates, and strong behavioral rules (no invented IDs, retry-on-failure, minimal-pauses). Its critical weakness is that every referenced phaseN-*.md file is absent from the bundle, so the guidance the workflow depends on — including the actual gate conditions — cannot be reached from this skill directory.

Suggestions

Include the ten phaseN-*.md files in the skill directory (or inline each phase's essential steps and gate condition), since the phase table links to them as the primary execution guide and none of them resolve in the current bundle.

Inline the concrete gate conditions in the phase table or a short section (e.g., what the testing-path verification gate checks: completed test call + visible transcript) so workflow validation is verifiable without the phase files.

Tighten the "Ask questions ONLY..." and "Onboarding is self-contained..." paragraphs — both restate the no-reconfirmation/Phase-6-handoff points and could be merged to cut ~10 lines without losing guidance.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no concept explanations, just directives like "Prefer the platform tools over describing API calls" and "Every agent ID... comes from a real tool response". It sits at anchor 4 (efficient, minor trimmable instances) rather than 5 because paragraphs like "Ask questions ONLY to collect missing inputs" and "Onboarding is self-contained" are long and partially restate the no-reconfirmation and Phase-6-handoff points.

4 / 5

Actionability

Guidance is concrete for an instruction-only skill: named tools ("ONE `aiagents_list` call", "`projects_list` / `projects_create`"), a hard rule with recovery ("If a call fails, fix the cause or ask for the missing input, then retry"), and the "Never invent IDs" rule — matching anchor 4's "mostly executable guidance... minor gaps". It falls short of anchor 5 because the executable detail is delegated to ten phase files that are not present in this skill directory, so the actual steps cannot be executed from what is written here.

4 / 5

Workflow Clarity

The phase table gives a clear ordered sequence with named gates ("First test run + **verification gate**", "Ingest call logs + **verification gate**") and a verification definition ("onboarding is NOT done when the agent/scenario rows exist... done when one test call completed"), plus error-recovery guidance — better than anchor 3's implicit checkpoints. It is not anchor 5 because the actual gate conditions and checklists live in the missing phase files, so validation specifics are named but not defined in this document.

4 / 5

Progressive Disclosure

The design is right — an overview body, one phase file per phase, and one-level-deep references (references/client-setup.md and references/api-quickstart.md both exist) — but the ten primary navigation targets (phase0-path.md, phase2-agent.md, phase3-testing-metrics.md, phase4-testing-evaluators.md, phase5-testing-first-run.md, phase6-testing-next.md, phase3-observability-ingest.md, phase4-observability-metrics.md, phase5-observability-evaluate.md, phase6-observability-review.md) do not exist in the bundle, so the main references do not resolve. That breaks navigation in practice, dropping it below anchor 4 despite the well-signaled structure.

3 / 5

Total

15

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: explicit trigger phrases, a clear what/when pair, explicit two-path scope, and an explicit negative boundary against sibling skills. The only gap is that the shared setup actions (agent connection, metrics) are not named alongside the two path descriptions.

DimensionReasoningScore

Specificity

Concrete actions are named per path — "build evaluators and run simulated calls" and "ingest production call logs and evaluate them" — covering the two onboarding paths with several specific actions, but other covered capabilities (agent connection, metric setup, verification) are omitted, leaving minor gaps in coverage. Fits anchor 4 ("several specific actions; minor gaps") rather than 5, whose examples enumerate comprehensive coverage, and clearly above anchor 3's "1-2 concrete actions".

4 / 5

Completeness

The "when" is explicit and trigger-phrase-driven ("Use when the user says...") and the "what" is explicit ("Covers two onboarding paths: **testing**... and **observability**..."), matching anchor 5's "clearly and explicitly answers both what AND when with concrete trigger phrases". It is not anchor 4 because the "when" here is more explicit than "could be more specific" — it enumerates triggers verbatim.

5 / 5

Trigger Term Quality

Nine quoted natural phrases ("get started with Cekura", "I'm new to Cekura", "first time using Cekura", "configure my project"), a slash command (/cekura-onboarding), and a general condition ("needs guidance on initial platform setup") give comprehensive coverage including synonyms and paraphrases users would actually say. Matches anchor 5's comprehensive synonym coverage; no natural variation is missing.

5 / 5

Distinctiveness Conflict Risk

A clear niche (onboarding) with an explicit negative boundary — "Not for adding an agent, more scenarios or more metrics to an existing workspace — those are cekura-create-agent, cekura-eval-design and cekura-metric-design" — routing overlapping requests to named siblings. This is distinct-trigger, minimal-conflict (anchor 5); the only mild overlap is "help me set up my agent", which the negative clause already disambiguates, keeping it above anchor 4.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 10 missing

Warning

Total

15

/

16

Passed

Repository
cekura-ai/cekura-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.