Koog 1.0 idioms, gotchas, and scaffolding skills for Kotlin agents on the JVM
88
88%
Does it follow best practices?
Impact
88%
1.95xAverage score across 43 eval scenarios
Passed
No known issues
{
"context": "Tests whether the agent picks the right Koog 1.0 API for history compression (a writeSession-locked replaceHistoryWithTLDR call at a deliberate boundary) rather than reaching for an external string-manipulation approach or compressing on every node.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Calls replaceHistoryWithTLDR inside llm.writeSession",
"description": "Invokes replaceHistoryWithTLDR() (or an equivalent HistoryCompressionStrategy invocation) inside llm.writeSession { ... }. Does NOT manipulate the prompt history outside a write session — the session lock is mandatory for safe mutation",
"max_score": 35
},
{
"name": "Compresses only at the boundary node, not every node",
"description": "The compression call appears in exactly one place — the boundary node the developer identified. Does NOT add per-node compression that would summarize away each step's findings",
"max_score": 25
},
{
"name": "Picks WholeHistory or equivalent TL;DR strategy",
"description": "Uses HistoryCompressionStrategy.WholeHistory (the TL;DR-everything variant) or replaceHistoryWithTLDR which maps to it. Not FromLastNMessages (which keeps a sliding window — different semantics) or NoCompression",
"max_score": 15
},
{
"name": "Does not introduce LongTermMemory",
"description": "Does not install the LongTermMemory feature — the developer's need is within-run compression, not cross-session memory. Adding LongTermMemory would be wrong scope and an unjustified dependency",
"max_score": 15
},
{
"name": "Compression happens before the next LLM call in drafting",
"description": "The replaceHistoryWithTLDR happens before the drafting phase's first nodeLLMRequest, so the drafting LLM sees the summarized history. Calling it after the drafting node would waste the call",
"max_score": 10
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
scenario-42
scenario-43
skills
add-observability
add-persistence
add-rag
add-structured-output
add-token-budgeting
add-tool
cache-llm-calls
define-prompt
domain-model-subtask-pipeline
references
enable-prompt-caching
handle-agent-events
manage-state
migrate-from-0-x
model-planner-subtasks
persist-chat-history
query-sql-from-agent
scaffold-agent
snapshot-and-restore
test-koog-agents
trace-agent-internals
use-attachments
use-functional-agent
use-llm-node-variants
use-planner
wire-a2a
wire-acp-server
wire-ktor-server
wire-mcp-server
wire-spring-boot