Name: dt-app-notebooks
Rating: 78.4 (1 reviews)
Author: Dynatrace

dt-app-notebooks

Work with Dynatrace notebooks - create, modify, query, and analyze notebook JSON. Derives from the dt-app-dashboards skill with notebook-specific differences documented here.

1.26x

Quality

66%

Does it follow best practices?

Impact

100%

1.26x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/dt-app-notebooks/SKILL.md

Quality

Discovery

32%

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 identifies the domain (Dynatrace notebooks) and lists basic actions but lacks an explicit 'Use when...' clause, which is a significant gap for skill selection. The reference to deriving from another skill adds confusion rather than clarity and introduces overlap risk. The trigger terms are adequate but could be expanded with more natural user language variations.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'Use when the user asks about Dynatrace notebooks, creating or editing notebook JSON, querying notebook data, or analyzing DT notebook configurations.'

Remove or clarify the 'derives from dt-app-dashboards' reference — instead, explicitly state how this skill differs (e.g., 'Handles notebook-specific structures like sections, tiles, and DQL queries, distinct from dashboard JSON').

Include more natural trigger keywords users might say, such as 'DT notebook', 'notebook tiles', 'notebook sections', 'DQL', or 'Dynatrace notebook JSON'.

Dimension	Reasoning	Score
Specificity	Names the domain (Dynatrace notebooks) and lists some actions (create, modify, query, analyze notebook JSON), but the reference to 'derives from dt-app-dashboards skill' is internal jargon rather than concrete capability detail.	2 / 3
Completeness	Describes what it does (work with Dynatrace notebooks) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also only moderately detailed, placing this at 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'Dynatrace', 'notebooks', 'notebook JSON', but misses common user variations such as 'DT notebook', '.json', 'notebook sections', 'DQL queries in notebooks', or other natural phrases a user might say.	2 / 3
Distinctiveness Conflict Risk	Mentioning 'Dynatrace notebooks' provides some distinctiveness, but the explicit reference to deriving from 'dt-app-dashboards' suggests significant overlap with that skill, creating potential conflict risk.	2 / 3
	Total	7 / 12 Passed

Implementation

100%

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

This is an exceptionally well-crafted skill that leverages a delta/inheritance pattern against the dashboard skill, keeping content focused on notebook-specific differences. The comparison tables, concrete JSON examples, exact CLI commands, and clear mandatory workflow with validation checkpoints make it highly actionable and efficient. The 'What Does NOT Apply' section is a particularly smart inclusion that prevents Claude from incorrectly carrying over dashboard concepts.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It assumes Claude knows what notebooks and dashboards are, avoids explaining basic concepts, and focuses entirely on the structural differences and specific workflows. The comparison tables are an excellent space-efficient way to convey mappings.	3 / 3
Actionability	Provides concrete JSON structure, exact CLI commands for validation and deployment, specific field paths for query/visualization mapping, and executable command examples. The mandatory workflow steps are copy-paste ready with real commands.	3 / 3
Workflow Clarity	The mandatory create/update workflow is clearly sequenced with explicit validation checkpoints (validate queries before adding, deploy via script that validates first, download-before-update pattern). The feedback loop is implicit in the deploy script blocking on errors, and the dry-run option is documented.	3 / 3
Progressive Disclosure	The skill is structured as a delta document referencing the base `dt-app-dashboards` skill, which is excellent progressive disclosure. It clearly signals what to follow from the parent skill and what differs. Related skills are listed at the bottom. The content is appropriately scoped without being monolithic.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Dynatrace/dynatrace-for-ai
Commit: 7cbe1ef

Reviewed: 15 days ago

Table of Contents

Discovery Implementation Validation

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.