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.

Quality

70%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./cekura/skills/cekura-coordinator/SKILL.md

Quality

Content

77%

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

This is a well-structured coordinator skill that excels at actionability and workflow clarity — the routing tables and user journeys make it very clear which skill to invoke for any given user need. Its main weakness is redundancy: the same skill-to-task mappings appear in the skills table, routing guide, and next steps section, inflating token cost without adding new information. Trimming the repeated mappings would make this significantly more token-efficient.

Suggestions

Consolidate the routing guide, available skills table, and next steps section into a single comprehensive routing table to eliminate redundancy and save ~40 lines.

Remove the 'Performing Platform Actions' paragraph — Claude already understands to prefer available tools over describing API calls when tools are configured.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good use of tables, but there's notable redundancy — the routing guide, available skills table, and next steps section all repeat the same skill-to-task mappings. The 'Performing Platform Actions' section explains things Claude should already understand about tool usage. Could be tightened by ~30%.	2 / 3
Actionability	Highly actionable as a routing/coordinator skill. Every user need maps to a specific skill or slash command. The routing table is concrete and unambiguous — Claude knows exactly which skill to invoke for each scenario. No code is needed since this is a routing skill, not a code skill.	3 / 3
Workflow Clarity	The 'Typical User Journeys' section provides clear, numbered sequences for different user personas (new user, has agent, has metrics, production monitoring). The routing guide provides unambiguous decision logic. For a coordinator/routing skill, this level of workflow clarity is excellent.	3 / 3
Progressive Disclosure	The skill appropriately references external skills and commands as one-level-deep pointers, and links to external docs. However, with no bundle files, the references to other skills can't be verified. The content itself is somewhat long for a routing skill — the routing guide, user journeys, and next steps sections overlap significantly and could be better organized to reduce redundancy.	2 / 3
	Total	10 / 12 Passed

Description

62%

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

This description excels at defining when it should be triggered, with extensive natural-language trigger phrases, but completely fails to describe what the skill actually does. It reads as a pure trigger list without any capability description, which makes it half-complete. Adding a brief statement of what the skill does (e.g., 'Lists available Cekura skills and provides guidance on which skill to use for a given task') would significantly improve it.

Suggestions

Add a 'what it does' statement at the beginning, e.g., 'Lists all available Cekura skills, describes their capabilities, and guides users to the right skill for their task.'

Restructure to lead with concrete actions (displays skill catalog, explains command usage, recommends appropriate skills) before the 'Use when...' trigger clause.

Dimension	Reasoning	Score
Specificity	The description does not list any concrete actions or capabilities. It only describes when to trigger, not what the skill actually does. There are no specific actions like 'lists available commands' or 'displays skill documentation'.	1 / 3
Completeness	The 'when' is thoroughly covered with explicit trigger phrases, but the 'what' is almost entirely missing. The description never explains what the skill actually does — it only says when to use it, not what actions it performs.	2 / 3
Trigger Term Quality	Excellent coverage of natural trigger phrases users would say: 'what can Cekura do', 'what commands are available', 'help me with Cekura', 'what skills do I have', 'show me Cekura features', 'how do I use Cekura'. These are very natural phrasings.	3 / 3
Distinctiveness Conflict Risk	The skill occupies a clear niche as a help/overview/entry-point skill for the Cekura system. The trigger terms are specific to meta-level questions about available capabilities, making it unlikely to conflict with task-specific skills.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: cekura-ai/cekura-skills
Commit: 3dd6d23

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.