semconv

Enforce additive-only semantic conventions for OpenTelemetry attributes in the claude.* namespace.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/agentglass/claude-trace --skill semconv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semconv
Source: https://github.com/agentglass/claude-trace/tree/main/.claude-plugin/skills/semconv
Command: npx skills add https://github.com/agentglass/claude-trace --skill semconv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pytest, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill enforces strict rules for managing semantic conventions in claude.* attributes, ensuring consistency, backward compatibility, and adherence to naming patterns.

Core Features & Use Cases

  • Additive-Only Changes: Guarantees that existing attributes are never removed or renamed, preventing breakage in user monitoring pipelines.
  • Naming Pattern Enforcement: Validates that all new attributes follow the claude.[category].[name] pattern.
  • Category and Type Validation: Restricts attributes to predefined categories (session, turn, tool, cost) and allowed data types (string, int, float, bool, string[]).
  • Use Case: When a developer proposes adding a new telemetry attribute for agent cost, this Skill automatically checks if the name is valid, if the category is correct, and if the data type is appropriate, preventing potential future issues.

Quick Start

Use the semconv skill to validate the naming convention for a new attribute claude.session.user_agent.

Frequently Asked Questions about semconv

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce backward compatibility for OpenTelemetry semantic conventions?

You enforce backward compatibility for OpenTelemetry semantic conventions by applying additive-only rules that prevent existing attributes from being removed or renamed, ensuring monitoring pipelines never break. This Skill automates those validation checks against predefined baselines.

What is the correct naming pattern for claude.* OpenTelemetry attributes?

The correct naming pattern for claude.* OpenTelemetry attributes is claude.[category].[name]. This Skill validates that all new and existing telemetry attributes strictly follow this structure to maintain API contract integrity and naming consistency.

How do I validate new OpenTelemetry attribute data types and categories?

You validate new OpenTelemetry attribute data types and categories by checking them against predefined rules. This Skill restricts categories to session, turn, tool, and cost, while limiting data types to string, int, float, bool, and string arrays.

Can I use pytest to test OpenTelemetry semantic convention rules?

Yes, you can use pytest to test OpenTelemetry semantic convention rules. This Skill lists pytest as a dependency, allowing you to automate validation checks for naming patterns, category rules, and data types within your testing pipeline.

Why do my OpenTelemetry attribute changes break existing monitoring pipelines?

OpenTelemetry attribute changes break existing monitoring pipelines when attributes are removed or renamed rather than added. This Skill solves the problem by enforcing additive-only changes and validating API contract integrity against baseline rules.