CtrlK
BlogDocsLog inGet started
Tessl Logo

cekura-infra-test-suite

Use when the user asks to create, update, or review a source-controlled Cekura JSON CI/CD test suite for a voice AI repository; create Tests-as-Code specs; turn a voice-agent code change into regression coverage; add deterministic Cekura voice tests to CI; or test an STT, LLM, TTS, VAD, interruption, idle-timer, DTMF, or call-lifecycle pipeline; or set up a CI gate that blocks a merge when the voice pipeline regresses. Inspects the repository before authoring a compact JSON suite, validates it safely with Cekura dry-run, and wires the workflow that runs it.

73

Quality

90%

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

81%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, opinionated workflow with concrete commands and a strong validation loop, slightly held back by some repetition and a missing referenced example file. It assumes Claude's competence and avoids explaining basic concepts.

Suggestions

Deduplicate the 'one question per run, asked first' rule — state it once in 'The interaction contract' and reference it from step 6 and the deliverable instead of restating it.

Create the referenced examples/cekura.tests.json or remove the bullet citing it, so every bundled-asset pointer resolves to a real file.

Replace the bare <skill> placeholder in commands with a concrete resolution note (e.g. 'substitute this skill's directory path') so snippets are copy-paste ready without inference.

DimensionReasoningScore

Conciseness

Largely efficient and dense with non-obvious domain guidance rather than basics Claude already knows, but the 'one question per run' rule is restated in three places and some rhetorical elaboration could be trimmed; sits above the score-3 anchor but not fully lean.

4 / 5

Actionability

Provides copy-paste-ready bash, curl, and JSON snippets plus a concrete expected_outcome contract, but uses a `<skill>` placeholder the model must resolve and delegates key templates to referenced files, leaving minor gaps short of fully self-contained executability.

4 / 5

Workflow Clarity

Steps 0–8 are explicitly sequenced with a real validation feedback loop — lint, then dry run, then fix, then dry run again until 'valid: true' — including error-recovery guidance, satisfying the score-5 anchor and avoiding the destructive/batch validation cap.

5 / 5

Progressive Disclosure

Good one-level-deep structure: a 'Bundled assets' section signals when to read each of references/discovery.md, case-catalog.md, ci-wiring.md, scripts/lint_suite.py, run_suite.py (all verified present), but examples/cekura.tests.json is referenced and does not exist, a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

100%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, specific description that explicitly covers both what the skill does and when to use it, with rich natural trigger terms and a distinct voice-AI CI niche. It avoids vagueness and over-claims entirely.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create, update, or review a source-controlled Cekura JSON CI/CD test suite', 'create Tests-as-Code specs', 'turn a voice-agent code change into regression coverage', 'set up a CI gate that blocks a merge' — with comprehensive coverage matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both: what ('Inspects the repository before authoring a compact JSON suite, validates it safely with Cekura dry-run, and wires the workflow that runs it') and when (opens with 'Use when the user asks to...'). No missing-trigger cap applies.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases a user would actually say — 'add ... voice tests to CI', 'regression coverage', 'CI gate that blocks a merge', plus the full STT/LLM/TTS/VAD/DTMF/call-lifecycle enumeration — covering synonyms and pipeline variants.

5 / 5

Distinctiveness Conflict Risk

Narrow niche — source-controlled Cekura JSON CI/CD test suite for a voice AI repository — with voice-specific pipeline triggers, making it clearly distinguishable from generic test or eval skills with minimal conflict risk.

5 / 5

Total

20

/

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.

Validation16 / 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.