CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/health-checks

Health check and readiness endpoints for web services — liveness probes,

97

3.61x
Quality

99%

Does it follow best practices?

Impact

94%

3.61x

Average score across 4 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

health-endpoint.jsonverifiers/

{
  "instruction": "Add /health and /ready endpoints for liveness and readiness probes",
  "relevant_when": "Agent builds a backend web service",
  "context": "Load balancers and container orchestrators need health endpoints. Liveness (/health) checks the process is running. Readiness (/ready) checks dependencies like database connections.",
  "sources": [
    {
      "type": "file",
      "filename": "skills/health-checks/SKILL.md",
      "tile": "tessl-labs/health-checks@0.1.2"
    }
  ],
  "checklist": [
    {
      "name": "health-route-exists",
      "rule": "Agent creates a GET /health endpoint that returns 200 with a status field",
      "relevant_when": "Agent sets up API routes"
    },
    {
      "name": "readiness-route-exists",
      "rule": "Agent creates a GET /ready endpoint that checks dependencies and returns 503 when they are unavailable",
      "relevant_when": "Agent sets up API routes and the service has database or external dependencies"
    },
    {
      "name": "health-endpoints-unauthenticated",
      "rule": "Health check endpoints are excluded from authentication middleware",
      "relevant_when": "Agent configures authentication or auth middleware"
    }
  ]
}

tile.json