CtrlK
BlogDocsLog inGet started
Tessl Logo

cekura-predefined-metrics

Use when the user asks "what predefined metrics are available", "which built-in metrics should I use", "what does CSAT measure", "how does hallucination detection work", "what's the difference between Interruption Score and AI Interrupting User", "which metrics are free", "which metrics need audio", "configure silence threshold", "set up sentiment metric", or any question about Cekura's out-of-the-box metrics. Covers the full catalog of predefined metrics — what each does, costs, constraints, configuration options, and when to use each one.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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.

A well-structured reference skill: actionable catalog tables, a sequenced workflow with a validation loop, and exemplary progressive disclosure to three genuine reference files. Its main weakness is redundancy — the cost quick-reference, the enabling-steps restatement, and the constraints section duplicate information already present in the catalog tables.

Suggestions

Remove or collapse the "Cost & Credits Quick Reference" table — the per-metric Cost column in the four catalog tables already carries this information, or move the consolidated view to a reference file.

Delete the "Enabling Predefined Metrics" section (it restates workflow steps 3–4) or merge its extra detail (the GET endpoint and `code`-field note) into the workflow step itself.

Trim "Key Constraints" to only the constraints not already stated in the catalog Notes column (most are verbatim repeats), keeping it as a short checklist.

DimensionReasoningScore

Conciseness

Mostly efficient — dense catalog tables with no basic-concept padding — but with genuine tightening opportunities: the "Cost & Credits Quick Reference" table restates the Cost column already present in all four catalog tables, "Enabling Predefined Metrics" repeats workflow steps 3–4 verbatim, and "Key Constraints" re-summarizes notes already in the catalog. This fits "mostly efficient but could be tightened" rather than the minor-trim anchor at 4.

3 / 5

Actionability

Concrete, executable guidance throughout: typed config keys with defaults and example payloads (e.g., `pronunciation_words` as "[{"word": "Cekura", "phoneme": "sɛˈkjʊrə"}]"), a real endpoint (`GET /test_framework/v1/predefined-metrics/`), and pitfalls phrased as checks. Minor gaps — the remaining API calls are deferred to references and the tool names are given without argument schemas — place it at 4 rather than fully copy-paste-ready 5.

4 / 5

Workflow Clarity

The 6-step workflow is clearly sequenced and includes a validation step with a feedback loop ("Validate by running ... If results look off, check the Common Pitfalls") plus an explicit failure warning ("missing either means the metric never fires"). Not 5: the sequence lacks a per-step checkpoint/checklist and the repeated "Enabling Predefined Metrics" section slightly muddies which instructions are canonical.

4 / 5

Progressive Disclosure

Three real, one-level-deep reference files (verified to exist: configuration-guide.md, api-reference.md, selection-by-use-case.md, ~436 lines total) are each described in Additional Resources and cited at point of need in the workflow, while the core catalog tables — the skill's primary value — stay inline. Clear overview with well-signaled references; matches the 5 anchor.

5 / 5

Total

16

/

20

Passed

Description

96%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, comprehensive "Use when" triggers phrased as natural user questions, an explicit and complete statement of what the skill covers, and a clearly bounded niche. The only weakness is minor trigger overlap with the custom-metric-design sibling skill.

DimensionReasoningScore

Specificity

The description states comprehensive, concrete coverage: "Covers the full catalog of predefined metrics — what each does, costs, constraints, configuration options, and when to use each one". All capability areas of the skill are enumerated with no meaningful gaps, matching the comprehensive-coverage anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

It explicitly answers "when" with an extended "Use when the user asks ... or any question about Cekura's out-of-the-box metrics" clause with concrete trigger phrases, and explicitly answers "what" in the closing sentence — the exact pattern of the 5 anchor. Not 4, since the "when" needs no added explicitness.

5 / 5

Trigger Term Quality

Ten quoted natural user questions ("what predefined metrics are available", "which metrics are free", "configure silence threshold", "what does CSAT measure") plus synonyms ("built-in", "out-of-the-box") give comprehensive natural-phrase coverage, including specific metric names a user would actually mention.

5 / 5

Distinctiveness Conflict Risk

"Cekura's out-of-the-box metrics" carves a clear niche with metric-specific triggers, but phrases like "set up sentiment metric" overlap the sibling cekura-metric-design (custom metrics) skill. Mostly distinct with minor overlap risk against a closely related skill — the 4 anchor, not 5.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.