[DOCS] Monitoring docs omit `skill_activated` slash-command trigger attribute

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/monitoring-usage

Section/Topic

"Skill activated event" under "Events"

Current Documentation

The skill_activated event section currently says:

Logged when a skill is invoked.

It lists these event-specific attributes:

event.name: "skill_activated" event.timestamp: ISO 8601 timestamp event.sequence: monotonically increasing counter for ordering events within a session skill.name: Name of the skill. For user-defined and third-party plugin skills the value is the placeholder "custom_skill" unless OTEL_LOG_TOOL_DETAILS=1 * skill.source: Where the skill was loaded from (for example, "bundled", "userSettings", "projectSettings", "plugin")

The section does not mention slash-command-triggered skill activations or an invocation_trigger attribute.

What's Wrong or Missing?

The Claude Code v2.1.126 changelog says the claude_code.skill_activated OpenTelemetry event now also fires for user-typed slash commands and carries a new invocation_trigger attribute with values "user-slash", "claude-proactive", or "nested-skill".

The monitoring docs already document claude_code.skill_activated, but the attribute table is outdated. Users configuring OpenTelemetry dashboards or audit rules from the docs cannot tell:

• that user-typed slash command invocations now produce skill_activated events, not just autonomous or tool-driven skill invocations
• that invocation_trigger is available for distinguishing direct slash-command use from Claude-proactive and nested-skill activations
• what values to expect for that attribute

Suggested Improvement

Update the "Skill activated event" section to describe the new trigger semantics and attribute. For example:

Before:

Logged when a skill is invoked.

After:

Logged when a skill is invoked, including user-typed slash command invocations.

Add an attribute row or bullet:

* invocation_trigger: How the skill was invoked. One of "user-slash", "claude-proactive", or "nested-skill".

If any values are gated, renamed before export, or only emitted in specific contexts, document those constraints next to the attribute.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/monitoring-usage | Skill activated event | Documents claude_code.skill_activated but omits invocation_trigger and slash-command trigger coverage |

Total scope: 1 page affected

This appears to be a v2.1.126 documentation catch-up item for the existing OpenTelemetry event schema.