CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/koog

Koog 1.0 idioms, gotchas, and scaffolding skills for Kotlin agents on the JVM

86

1.86x
Quality

88%

Does it follow best practices?

Impact

86%

1.86x

Average score across 45 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-36/

{
  "context": "Negative case — tests whether the agent recognizes that the developer's actual workload (one-shot text-to-text with no tools and no distinct phases) does not benefit from the subtask-pipeline pattern, and routes them to a simpler shape rather than building the pipeline because the developer asked for it by name.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Names the absence of distinct phases as the disqualifier",
      "description": "Identifies in prose that the workload has no phases that produce structurally different intermediate artifacts — it is one transformation. The pipeline pattern's benefit is the typed handoff between phases; with no handoff there is no benefit",
      "max_score": 25
    },
    {
      "name": "Redirects to the simpler shape",
      "description": "Recommends the default agent shape — `AIAgent(systemPrompt = ..., promptExecutor = ..., llmModel = ...)` (the default `singleRunStrategy()` is implicit and usually omitted) — OR the functional-agent shape if some Kotlin logic is needed. Names one of these specifically. Does NOT build a contrived subgraphWithTask<String, String> pipeline just to satisfy the developer's request",
      "max_score": 30
    },
    {
      "name": "Does not produce subgraphWithTask code",
      "description": "The output contains no subgraphWithTask, subgraphWithVerification, or strategy { ... } block. Building the pipeline pattern for a one-shot text transform is the failure mode this scenario tests",
      "max_score": 20
    },
    {
      "name": "Does not introduce typed handoff data classes",
      "description": "The output contains no @Serializable @LLMDescription'd intermediate data classes. Inventing a fake intermediate type just to have a 'typed handoff' for a one-step transform is over-engineering",
      "max_score": 15
    },
    {
      "name": "Engages with the developer's framing without capitulating",
      "description": "Acknowledges that the pattern is real and powerful — and explains the criterion that makes it fit: distinct phases with structurally different intermediate shapes. Does not just refuse without explaining when the pattern would fit",
      "max_score": 10
    }
  ]
}

evals

README.md

tile.json