CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

koko

Develop and extend Koko — the Elixir/OTP agent living alongside joelclaw. Covers OTP patterns, Redis bridge protocol, shadow execution, and workload implementation.

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 ./skills/koko/SKILL.md
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.

The body is an efficient, actionable project brief: concrete commands, hard constraints, ADR-driven checkpoints, and no filler. Its main weaknesses are the absent error-recovery loop around crash debugging and slight redundancy between the opening line and the description.

Suggestions

Add a short crash-recovery loop for the supervision-tree debugging use case (e.g., reproduce in iex, check supervisor restarts via Observer or logger output, fix the child spec, re-run mix test).

Remove the opening sentence that restates the description, or replace it with the single highest-value fact not already known.

Consider moving the ADR table and four-phase roadmap into a references/ file (e.g. references/ADRS.md) with a one-line pointer, keeping SKILL.md focused on commands, constraints, and patterns.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no OTP/BEAM primers, no padded explanations — with every section carrying project-specific facts (Redis location, key names, ssh target). It falls short of 5 because the opening line ('Use this skill when working on the Koko Elixir project — the BEAM co-resident agent alongside joelclaw') duplicates the description, and Phase 4 graduation criteria ('DX is enjoyable') are roadmap content with marginal operational value.

4 / 5

Actionability

Concrete, copy-paste-ready commands ('mix deps.get', 'mix run --no-halt', 'iex -S mix', 'ssh joel@panda "cd ~/Code/joelhooks/koko && mix run --no-halt"'), exact resource names ('joelclaw:gateway:events', 'joelclaw:koko:shadow:<function>', 'localhost:6379'), and specific OTP directives ('Logger.info("[koko]")', 'one_for_one unless processes are coupled'). Minor gaps keep it from 5: no example GenServer skeleton or handle_info pattern to copy when adding a workload.

4 / 5

Workflow Clarity

Conditional checkpoints are explicit ('Before adding a new workload: Check ADR-0117... and ADR-0118', 'Before changing Redis integration: Check ADR-0116', 'Before any architectural change: Propose or update an ADR'), and development commands form a runnable sequence with 'mix test' as validation. It is not 5 because there is no explicit validate/fix/retry loop for the riskiest operation — debugging supervision-tree crashes is listed as a use case but the workflow stops at 'mix test' with no error-recovery guidance.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the ~95-line body is well-organized with clear one-level-deep pointers: the ADR table links each decision by URL, 'AGENTS.md: Full context in repo root' signals where depth lives. Not 5 because the four-phase roadmap and the ADR table (five external links) are content that could live in a single reference file, and there is no explicit mapping of which sections to consult for which task beyond the three 'Before...' lines.

4 / 5

Total

16

/

20

Passed

Description

62%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.

The description clearly and specifically states what the skill does and is highly distinctive, but it omits any 'when to use' trigger guidance and lacks natural trigger-term synonyms, leaving it strong on what yet incomplete on when.

Suggestions

Append an explicit 'when' clause, e.g. 'Use when working on the Koko Elixir project, joelclaw's BEAM co-resident agent, or when the user mentions koko, elixir agent, shadow executor, or koko workloads.'

Add natural trigger-term variations users would actually say (e.g., 'elixir agent', 'BEAM agent', 'koko workload', 'mix') to improve trigger-term coverage.

Keep the existing specificity; the four named capability areas (OTP patterns, Redis bridge protocol, shadow execution, workload implementation) are a strength worth preserving.

DimensionReasoningScore

Specificity

'Develop and extend Koko' names two concrete actions, and 'Covers OTP patterns, Redis bridge protocol, shadow execution, and workload implementation' lists several specific capability areas. It sits above the 3 anchor (domain + only 1-2 actions) because coverage spans four concrete areas, but below 5 because 'Covers...' enumerates topics rather than fully action-oriented verbs.

4 / 5

Completeness

The 'what' is clear (develop and extend Koko; covers OTP patterns, Redis bridge protocol, shadow execution, workload implementation), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is specific and multi-faceted rather than vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ('Koko', 'Elixir/OTP', 'Redis bridge protocol', 'shadow execution', 'joelclaw') but common variations and natural phrases a user would say ('elixir agent', 'koko workload', 'use when working on koko') are absent from the description itself. This matches the anchor for 'some relevant keywords but missing common variations or synonyms' rather than 4, whose examples show a denser spread of natural terms.

3 / 5

Distinctiveness Conflict Risk

Proper nouns and project-specific terms ('Koko', 'joelclaw', 'shadow execution', 'Redis bridge protocol') create a clear niche with distinct triggers and minimal conflict risk with other skills. No generic phrasing that would collide with unrelated skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

joelhooks/joelclaw

Path

skills/koko/SKILL.md

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.