CtrlK
BlogDocsLog inGet started
Tessl Logo

juliusbrussee/caveman

Compressed caveman-style prose for AI coding agents — cuts ~65% output tokens while keeping full technical accuracy

96

1.00x
Quality

100%

Does it follow best practices?

Impact

96%

1.00x

Average score across 38 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-16/

{
  "context": "Tests whether the response correctly configures all three Kubernetes probe types with appropriate settings for a slow-starting Java app.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Configures startup probe for slow start",
      "description": "Uses a startup probe with enough failureThreshold * periodSeconds to cover the 30-second startup without the liveness probe killing the pod",
      "max_score": 15
    },
    {
      "name": "Separates liveness from readiness concerns",
      "description": "Explains that liveness = is the process stuck (restart it), readiness = can it serve traffic (stop routing to it)",
      "max_score": 12
    },
    {
      "name": "Readiness checks dependency health",
      "description": "Readiness probe checks database connectivity or downstream dependencies, not just that the process is alive",
      "max_score": 10
    },
    {
      "name": "Accounts for GC pauses in liveness config",
      "description": "Sets liveness probe timeoutSeconds and failureThreshold high enough that a long GC pause doesn't trigger a restart",
      "max_score": 10
    },
    {
      "name": "Uses correct YAML or probe spec syntax",
      "description": "Probe configuration uses valid Kubernetes YAML with correct field names (httpGet, initialDelaySeconds, periodSeconds, etc.)",
      "max_score": 8
    },
    {
      "name": "No incorrect information",
      "description": "Response does not contain factually wrong statements about Kubernetes probes or Spring Boot actuator",
      "max_score": 10
    }
  ]
}

evals

README.md

SKILL.md

tile.json