CtrlK
BlogDocsLog inGet started
Tessl Logo

cekura-coordinator

Use when the user asks "what can Cekura do", "what commands are available", "help me with Cekura", "what skills do I have", "show me Cekura features", "what's available", "how do I use Cekura", or needs guidance on which Cekura skill to use for their task. Also relevant as the entry point when a user has just installed cekura-skills for the first time.

68

Quality

82%

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

75%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, highly actionable coordinator body that routes users to exact skills and commands via tables and journeys. Its main weakness is triplicate re-listing of the same skills across three sections, which adds tokens without new information.

Suggestions

Consolidate the skill list: the Available Skills table, Routing Guide, and Next Steps each re-enumerate the skills — collapse Next Steps into a brief pointer to the Routing Guide to remove redundancy.

Add a one-line confirmation/checkpoint to each journey (e.g., 'Confirm the user's goal before invoking the next skill') to raise workflow clarity.

Move the long Routing Guide table into a references/routing.md file and link to it from SKILL.md, keeping only the most common routes inline, to improve progressive disclosure and token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient tables and routing guidance with no concept over-explanation, but the available-skills list is re-stated across the Skills table, the Routing Guide, and the Next Steps section, creating more than minor redundancy that could be tightened.

3 / 5

Actionability

Provides concrete, executable routing: exact skill names, exact slash commands, and a decision table mapping specific user needs to specific destinations, covering the common cases for an instruction-only coordinator.

5 / 5

Workflow Clarity

Numbered Typical User Journeys give clear sequenced processes and the routing decision is explicit; it sits just below a 5 because the journeys lack explicit validation/confirmation checkpoints, though none are strictly required for a non-destructive routing skill.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and self-contained content, and external docs are signaled one level deep at the end; no bundle files exist to verify, so it does not reach the top anchor reserved for clearly signaled one-level references split across files.

4 / 5

Total

16

/

20

Passed

Description

90%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 coordinator description with explicit 'Use when' triggers, comprehensive natural-language phrasings, and a clearly distinct Cekura niche. The only weakness is that it states few concrete actions beyond 'route/find', which keeps specificity at the mid anchor.

DimensionReasoningScore

Specificity

Names the domain and a couple concrete actions ('Route users to the right Cekura skill or command', 'helps users find the right tool') but does not enumerate multiple specific actions, fitting the 'names domain and 1-2 concrete actions' anchor rather than the comprehensive anchor 4.

3 / 5

Completeness

Explicitly answers both 'what' (route users to the right Cekura skill/command, the 'front desk') and 'when' with concrete trigger phrases plus a first-install entry point, matching the top anchor.

5 / 5

Trigger Term Quality

Lists many natural phrases users would actually say ('what can Cekura do', 'what commands are available', 'help me with Cekura', 'what skills do I have', 'how do I use Cekura') with synonyms and variations, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear Cekura-specific niche with Cekura-branded triggers, so it is unlikely to fire for unrelated skills and carries minimal conflict risk.

5 / 5

Total

18

/

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.