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.

63

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./cekura/skills/cekura-coordinator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, actionable router skill with clear routing tables and sequenced user journeys. Its main weakness is redundancy: the skill set is restated across three sections, inflating token cost without adding new information.

Suggestions

Collapse the 'Next Steps' list into the 'Routing Guide' or 'Available Skills' table to eliminate the third restatement of the skill set.

Consider whether the 'Available Skills' and 'Available Commands' tables can be merged with the Routing Guide so each skill/command appears once with its use-when and routing entry together.

DimensionReasoningScore

Conciseness

The skill list is enumerated three times — the 'Available Skills' table, the 'Routing Guide' references, and the 'Next Steps' list — which is noticeable redundancy that could be tightened, even though no common-knowledge concepts are over-explained.

3 / 5

Actionability

The Routing Guide maps specific user-need phrases to exact skills and slash commands, giving concrete executable routing guidance; the 'Performing Platform Actions' section stays slightly abstract, keeping it just short of 5.

4 / 5

Workflow Clarity

The 'Typical User Journeys' provide clear numbered sequences for each persona, and routing is non-destructive so no validation cap applies; minor gaps keep it from a 5 that would require explicit checkpoints or feedback loops.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers and one-level-deep external doc links in the Documentation section, and there are no nested or buried references; at ~145 lines it exceeds the simple-skill threshold that would allow a 5 on sections alone.

4 / 5

Total

15

/

20

Passed

Description

81%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 trigger-heavy description with excellent natural phrasing and a distinct Cekura-scoped niche. Its main weakness is that it leads with 'when' and only implies the 'what' (routing users to the right skill) rather than stating the action explicitly.

Suggestions

Lead with a concrete action statement before the triggers, e.g. 'Routes users to the right Cekura skill or command based on their need.' so the 'what' is explicit, not implied.

Add 1-2 more concrete actions (e.g. 'surfaces available skills and commands', 'recommends a skill for a described task') to lift specificity beyond a single action.

DimensionReasoningScore

Specificity

The description names the domain (Cekura skill selection) and one action ('needs guidance on which Cekura skill to use for their task') but does not enumerate multiple concrete routing actions, so it stops at 'names domain and 1-2 concrete actions'.

3 / 5

Completeness

The 'when' is explicit and rich (concrete trigger phrases plus the first-install entry point), but the 'what' is only implied through 'needs guidance on which Cekura skill to use' rather than stated as a crisp action verb, so it is not a clean 5.

4 / 5

Trigger Term Quality

Phrases like 'what can Cekura do', 'what commands are available', 'help me with Cekura', 'what skills do I have', 'show me Cekura features', and 'how do I use Cekura' are natural synonyms a user would actually say, giving comprehensive coverage.

5 / 5

Distinctiveness Conflict Risk

All triggers are Cekura-scoped ('what can Cekura do', 'show me Cekura features'), giving the skill a clear coordinator niche with minimal overlap risk against unrelated skills.

5 / 5

Total

17

/

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.