CtrlK
BlogDocsLog inGet started
Tessl Logo

dt-app-notebooks

Work with Dynatrace notebooks - create, modify, query, and analyze notebook JSON including sections, DQL queries, and visualizations.

73

1.78x
Quality

74%

Does it follow best practices?

Impact

73%

1.78x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dt-app-notebooks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is well-structured, actionable, and efficiently progressive, with explicit validation in the update workflow. Tightening the rules bullets and verifying reference detail would push conciseness and workflow clarity to level 5.

DimensionReasoningScore

Conciseness

The body is efficient with no padding of concepts Claude already knows; the JSON example and visualization list earn their place, with only minor instances that could be trimmed.

4 / 5

Actionability

Concrete commands (dtctl get/apply), a complete notebook JSON example, and a mandatory ordering give mostly executable guidance with only minor gaps.

4 / 5

Workflow Clarity

Mandatory order plus explicit validation ("Validate ALL section queries before adding"; deploy runs validation automatically) and an overwrite-warning feedback note; minor checkpoint gaps in the references keep it from level 5.

4 / 5

Progressive Disclosure

A clear overview points to three real, one-level-deep references via a well-signaled 'When to Load' table; bulk detail is appropriately split into reference files.

5 / 5

Total

17

/

20

Passed

Description

70%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, distinct, and well-scoped to Dynatrace notebooks, but it lacks an explicit 'Use when...' trigger clause, which caps completeness. Adding a trigger clause would lift the completeness dimension.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when creating, modifying, querying, or analyzing Dynatrace notebooks or notebook JSON.'

Include a few natural synonyms or file references (e.g. '.json') to broaden trigger term coverage.

DimensionReasoningScore

Specificity

"create, modify, query, and analyze notebook JSON including sections, DQL queries, and visualizations" lists several specific concrete actions; not quite comprehensive level-5 coverage but clearly beyond a single action.

4 / 5

Completeness

The "what" is clear (create/modify/query/analyze notebook JSON), but there is no explicit "Use when..." trigger clause; per the rubric, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like "Dynatrace notebooks", "DQL queries", and "visualizations" are present and would be said by a user in this domain, but a few common variations or synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

"Dynatrace notebooks" with "DQL queries" carves out a clear niche with distinct triggers and minimal overlap with other skills.

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.