CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

llmobs-integration

Use when adding, debugging, or modifying LLMObs plugins for an LLM library in dd-trace-js. Triggers: "add LLMObs support", "instrument chat completions / streaming / embeddings / agent runs / orchestration / tool calls / retrieval", "LLMObsPlugin", "getLLMObsSpanRegisterOptions", "setLLMObsTags", "SPAN_KINDS", "span kind", any provider tag ("openai" / "anthropic" / "genai" / "google" / "langchain" / "langgraph" / "ai" llmobs), "VCR cassettes".

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-crafted, information-dense skill body that stays almost entirely on non-obvious, codebase-specific knowledge with a clear implementation sequence and a sensible reference bundle. The gaps are small: no in-body code skeleton, validation outsourced to a sibling skill, one orphaned reference file, and slight rhetorical padding in the source-reading section.

Suggestions

Add a minimal leaf-plugin code skeleton (or a one-line link to references/reference-implementations.md) in the Implementation Steps so the body demonstrates the concrete shape of getLLMObsSpanRegisterOptions and setLLMObsTags.

Link references/reference-implementations.md from SKILL.md (e.g., in the Implementation Steps or Core Concepts) so the bundle's working examples are discoverable from the entry point.

Make the validation checkpoint explicit in the workflow, e.g. a final step 'Run the integration's VCR-based llmobs tests to verify span kind and tags' rather than relying on the pointer to the llmobs-testing skill.

DimensionReasoningScore

Conciseness

The body is dense with dd-trace-js-specific facts (LLMObsPlugin contracts, SPAN_KINDS file path, package-shape categories, message shapes) with almost no explanation of concepts Claude already knows. Minor trimmable material: the rhetorical "LLM libraries iterate fast — six-month-old assumptions... are usually wrong" intro, and provider-specific message handling that is then restated as "See [references/message-extraction.md] for provider-specific patterns". Fits the 4 anchor ('efficient; minor instances of over-explanation') rather than 5.

4 / 5

Actionability

Highly concrete guidance: exact paths ("packages/dd-trace/src/llmobs/plugins/{integration}/", "packages/dd-trace/src/llmobs/constants/tags.js"), method signatures to implement, the tagger message shape, and export conventions (single class vs array vs CompositePlugin). Falls short of 5 because the body contains no executable code example (working examples live in references/plugin-architecture.md and reference-implementations.md) and step 5 "Cover the edges" is a checklist without specifics.

4 / 5

Workflow Clarity

Implementation Steps 1–5 form a clear ordered sequence (map shape from source → create plugins → implement register options → implement tags → cover edges), and testing strategy is delegated to the sibling llmobs-testing skill. Matches the 4 anchor ('clear sequence with most checkpoints present; minor validation gaps') — there is no explicit in-body validation command or run-the-tests checkpoint, but the work is neither destructive nor batch, so no cap applies.

4 / 5

Progressive Disclosure

Well-organized overview with three one-level-deep, well-signaled references (plugin-architecture.md, category-detection.md, message-extraction.md) all verified to exist, plus sibling-skill links for testing and upstream-source guidance. Held below 5 because references/reference-implementations.md exists in the bundle but is never linked from SKILL.md, leaving it undiscoverable from the entry point.

4 / 5

Total

16

/

20

Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, niche-scoped description with an explicit use-when clause and an unusually thorough trigger list covering user phrases, internal API identifiers, library names, and test tooling. The only weakness is that bare provider names as standalone triggers slightly raise conflict risk with general LLM coding skills.

DimensionReasoningScore

Specificity

Names the domain ("LLMObs plugins for an LLM library in dd-trace-js") and three concrete actions ("adding, debugging, or modifying"), plus instrumented operations listed as triggers ("chat completions / streaming / embeddings / agent runs / orchestration / tool calls / retrieval"). Falls just short of the 5 anchor because the actions are generic verbs applied to the domain and coverage details live in trigger terms rather than the capability statement.

4 / 5

Completeness

Explicitly answers both questions: the what is "adding, debugging, or modifying LLMObs plugins for an LLM library in dd-trace-js" and the when is an explicit "Use when..." clause followed by a concrete Triggers list. Matches the 5 anchor ('clearly and explicitly answers both what AND when with concrete trigger phrases').

5 / 5

Trigger Term Quality

Comprehensive trigger coverage spanning natural phrases ("add LLMObs support"), API identifiers ("LLMObsPlugin", "getLLMObsSpanRegisterOptions", "setLLMObsTags", "SPAN_KINDS"), all relevant library names ("openai" / "anthropic" / "genai" / "google" / "langchain" / "langgraph"), and test fixtures ("VCR cassettes") — exactly the terms a dd-trace-js contributor would naturally use. Clearly exceeds the 4 anchor ('a few natural terms missing').

5 / 5

Distinctiveness Conflict Risk

The dd-trace-js/LLMObs scoping and identifiers like "LLMObsPlugin" make the niche clear, but the trigger list includes bare provider tags ("openai" / "anthropic" / "langchain") that commonly appear in generic LLM-development requests, creating minor overlap risk with closely related LLM skills. Fits the 4 anchor ('mostly distinct; minor overlap risk') better than 5.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

DataDog/dd-trace-js

Path

.agents/skills/llmobs-integration/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.