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.
60
70%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./cekura/skills/cekura-coordinator/SKILL.mdQuality
Discovery
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 trigger terms and distinctiveness — it's very clear when this skill should activate, with numerous natural user phrases. However, it critically lacks a 'what does this do' statement, making it incomplete. Adding a concise capability statement at the beginning would significantly improve it.
Suggestions
Add a leading capability statement describing what the skill does, e.g., 'Lists all available Cekura skills, summarizes their capabilities, and provides usage guidance to help users find the right skill for their task.'
Use third-person voice for the capability statement (e.g., 'Displays available skills and commands' rather than relying solely on trigger phrases).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description does not list any concrete actions or capabilities. It only describes when to trigger but never says what the skill actually does beyond vague 'guidance' language. | 1 / 3 |
Completeness | The 'when' is thoroughly covered with explicit trigger phrases, but the 'what' is essentially missing — it never clearly states what the skill does (e.g., 'Lists available Cekura skills and provides usage guidance'). The description answers when but not what. | 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 realistic user queries. | 3 / 3 |
Distinctiveness Conflict Risk | This is clearly a help/overview/onboarding skill for the Cekura system. The triggers are very specific to meta-questions about available skills and features, making it unlikely to conflict with any task-specific skill. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
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 provides clear, actionable routing from user needs to specific skills and commands. Its main weakness is internal redundancy — the available skills/commands tables, routing guide, and next steps section all partially repeat the same mappings, which inflates token usage. The user journeys are a strong addition that adds genuine value beyond simple routing.
Suggestions
Consolidate the Available Skills & Commands tables, Routing Guide, and Next Steps into a single comprehensive routing table to eliminate redundancy and save tokens.
Remove the 'Performing Platform Actions' section — 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/commands, and next steps sections overlap significantly. The 'Performing Platform Actions' section explains things Claude should already understand about tool usage. The routing table could subsume the skills/commands tables. | 2 / 3 |
Actionability | The skill provides highly concrete routing guidance with specific skill names and slash commands mapped to exact user needs. The routing table, user journeys, and next steps give Claude unambiguous instructions on what to invoke for any given user request. | 3 / 3 |
Workflow Clarity | The 'Typical User Journeys' section provides clear, numbered sequences for different user scenarios. For a routing/coordinator skill, the workflows are well-sequenced and the routing logic is unambiguous. No destructive operations are involved, so validation checkpoints aren't necessary. | 3 / 3 |
Progressive Disclosure | The skill appropriately references external skills and commands rather than inlining their content, and links to API docs. However, the content itself is somewhat monolithic — the routing guide, skills table, commands table, and next steps contain significant overlap that could be consolidated. No bundle files are provided to offload the detailed routing table or journeys. | 2 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- cekura-ai/cekura-skills
- Commit
24ad1d0
- 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.