CtrlK
BlogDocsLog inGet started
Tessl Logo

coralogix/opentelemetry-skills

OpenTelemetry Collector deployment, instrumentation (Java/Python/Node.js/.NET/Go), and OTTL pipeline transforms for Coralogix — coralogix exporter config, Helm chart selection, Kubernetes topology, ECS/EKS/GKE deployments, SDK setup, APM transactions, and OTTL cardinality/PII/routing.

92

1.10x
Quality

96%

Does it follow best practices?

Impact

92%

1.10x

Average score across 127 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-105/

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nProfiling spans? The profiles pipeline has OTel v1.10 proto changes like ProfilesDictionary and profile attribute indices, and app / subsystem metadata is not where logs and traces put it. Should the semconv skill own the full fix?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-profilesdictionary",
      "description": "The response contains \"ProfilesDictionary\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "profiles-profiling",
      "description": "The response matches the pattern: (?i)(profiles|profiling)",
      "max_score": 3
    },
    {
      "name": "boundary-hand-off",
      "description": "The response matches the pattern: (?i)(boundary|hand ?off|belongs?|owned|owner)",
      "max_score": 3
    },
    {
      "name": "says-profiling-proto-resource-enrichment-is-a",
      "description": "Says profiling proto/resource enrichment is an associated boundary: semconv can identify resource-vs-profile metadata concerns, but full OTel profiles proto handling and pipeline setup belong to the profiling or collector owner. FAIL if it invents stable Coralogix profile semconv requirements as if they were current trace/span requirements.",
      "max_score": 2
    }
  ]
}

evals

scenario-105

criteria.json

task.md

llms.txt

README.md

tessl.json

tile.json