telemetry-terminology-similaritylisted

# Telemetry Terminology Similarity Score pairwise similarity of telemetry field names across three independent layers. Emits raw scores — no thresholds, no clustering, no opinions. The consuming AI agent applies its own domain judgment. > **Self-Evolving Skill**: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues. ## When to Use This Skill Use this skill when: - Auditing a telemetry/logging schema for naming collisions - Comparing two JSONL log schemas for field overlap - Detecting `trace_id` vs `traceId` vs `request_id` vs `correlation_id` style problems - Validating field naming consistency before shipping telemetry changes ## Architecture 5-layer scoring pipeline — each layer catches what the others miss: ``` ┌─────────────────────────���───────────────────────────────┐ │ Layer 1: NORMALIZE │ │ camelCase/snake_case split + abbreviation expansion │ │ wordninja for concatenated words │ │ "traceId" → "trace id", "ts" → "timestamp" │ ├─────────────────────────────────────────────────────────┤ │ Layer 2: SYNTACTIC (RapidFuzz, 0-100) │ │ token_set_ratio on normalized forms │ │ Catches: trace_id ↔ traceId, level ↔ log_level │ ├─────────────────────────────────────────────────────────┤ │ Layer 3: TAXONOMIC (WordNet