CtrlK
BlogDocsLog inGet started
Tessl Logo

dt-js-runtime

Dynatrace server-side JS runtime — function contract, runtime limits, Web APIs, Node.js modules, fetch with credential vault, and the @dynatrace-sdk/* catalog.

67

Quality

80%

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

93%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.

The body is an efficient, actionable overview with well-structured progressive disclosure into real reference files. Its only gap is the absence of an explicit validation/verification checkpoint after running a function.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence (no explanation of what JS/TypeScript or fetch is), and every line earns its place; code blocks are tight and directly executable.

5 / 5

Actionability

It provides copy-paste-ready, executable examples for the default async export, the `event` parameter, and `dtctl exec function` with concrete flags and payload, covering the common cases.

5 / 5

Workflow Clarity

The single-purpose flow (define contract → pick a reference → run via dtctl) is clearly sequenced with concrete commands; it is a 4 rather than 5 because there is no explicit verification step confirming a run succeeded or inspecting output/errors.

4 / 5

Progressive Disclosure

A concise overview links to four clearly-signaled, one-level-deep reference files via a table with explicit 'When to load' guidance, and all referenced paths resolve to real files; navigation is easy and content is appropriately split.

5 / 5

Total

19

/

20

Passed

Description

67%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.

The description is specific and well-differentiated but lacks an explicit 'Use when...' trigger clause, which caps completeness and limits trigger-term coverage. It reads as a capability inventory rather than activation guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when writing or running server-side JavaScript/TypeScript functions on the Dynatrace AppEngine runtime, calling /platform or external APIs, or using @dynatrace-sdk/* packages.'

Broaden trigger terms with user-facing synonyms (e.g. 'Dynatrace functions', 'server-side JS', 'AppEngine automation', 'dtctl exec function').

Keep the third-person capability list but lead with the activation trigger so Claude can match it to user intent.

DimensionReasoningScore

Specificity

The description names the domain and enumerates multiple concrete capabilities ('function contract, runtime limits, Web APIs, Node.js modules, fetch with credential vault, and the @dynatrace-sdk/* catalog'), giving comprehensive coverage.

5 / 5

Completeness

It clearly answers 'what' but provides no 'when' / 'Use when...' trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

It contains some natural terms ('JS runtime', 'fetch', 'Node.js modules', 'credential vault') but leans on technical jargon and omits common user-facing phrasing and synonyms; it is not a 4 because natural keyword coverage is incomplete.

3 / 5

Distinctiveness Conflict Risk

It targets a clearly distinct niche (Dynatrace server-side AppEngine JS runtime) with niche-specific terms, so overlap with other skills is minimal.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Dynatrace/dynatrace-for-ai
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.