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 stdio (process-based) MCP transport when the user explicitly wants the server launched as a local subprocess — rather than reaching for HTTP transports that don't apply here.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses the process-based MCP transport",
"description": "Builds the MCP registry using McpToolRegistryProvider.fromProcess(process). Does NOT use streamableHttp or fromSseUrl — the user explicitly chose stdio against a local subprocess",
"max_score": 30
},
{
"name": "Launches the process with ProcessBuilder",
"description": "Creates the subprocess via ProcessBuilder(\"npx\", \"-y\", \"@playwright/mcp@latest\").start() (or an equivalent constructor producing a java.lang.Process). Each argument is its own element in the command list — does not pass the whole command as a single shell-quoted string",
"max_score": 20
},
{
"name": "Adds the agents-mcp dependency",
"description": "Adds the MCP client dependency `ai.koog:agents-mcp-jvm:1.0.0-beta` to build.gradle.kts. The umbrella koog-agents does not include MCP, so the dependency must be added explicitly. The artifact requires the `-jvm` suffix (only JVM variants are published at this version) and the `1.0.0-beta` version (Koog 1.0 stable did not publish `agents-mcp` at `1.0.0`)",
"max_score": 20
},
{
"name": "Builds the registry before constructing the agent",
"description": "Calls McpToolRegistryProvider.fromProcess(...) and assigns it to a variable BEFORE the AIAgent(...) call, then passes that variable as toolRegistry. Does not try to add MCP tools after the agent is constructed",
"max_score": 15
},
{
"name": "Calls the suspending builder inside a coroutine context",
"description": "The fromProcess builder runs inside the existing runBlocking { ... } (or another coroutine scope), since it is a suspending call",
"max_score": 10
},
{
"name": "Does not import Ktor or HTTP-client types",
"description": "The stdio transport has no HTTP component — the produced file should not import Ktor HttpClient, OkHttp, or any HTTP-transport configuration the agent does not need",
"max_score": 5
}
]
}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