Work with Dynatrace notebooks - create, modify, query, and analyze notebook JSON including sections, DQL queries, visualizations, markdown documentation, and analytics workflows. Supports notebook creation from scratch, section-based updates, data extraction from Document Store, structure analysis, investigation workflows, and collaborative documentation.
71
58%
Does it follow best practices?
Impact
89%
1.28xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/dt-app-notebooks/SKILL.mdCreate investigation notebook from scratch
Version field set to 7
0%
100%
Default timeframe present
100%
100%
Starts with markdown section
100%
100%
No state.result objects
100%
100%
Unique section UUIDs
100%
100%
Markdown between queries
100%
100%
Relative timeframes used
80%
100%
Queries have limit clause
25%
37%
Descriptive field names
100%
100%
Visualization matches data type
100%
100%
autoSelectVisualization false
0%
100%
Query .dql files present
100%
100%
Validate script uses jq
100%
100%
querySettings maxResultRecords
0%
100%
Extend existing notebook with new sections
Backup file created
100%
100%
No state.result in updated notebook
0%
0%
New sections have unique UUIDs
0%
100%
OOMKill DQL section uses lineChart
100%
100%
Standalone query file present
100%
100%
New DQL section has limit clause
0%
0%
Summary markdown section added
100%
100%
Narrative markdown between DQL sections
0%
0%
verify.sh uses jq for ID uniqueness
100%
100%
New section has querySettings
100%
100%
autoSelectVisualization false on new section
100%
100%
Version still 7
100%
100%
Build a reusable DQL query library notebook
Version field is 7
0%
100%
defaultTimeframe present
0%
100%
Starts with markdown section
100%
100%
Category header pattern
100%
100%
Explanatory markdown after each query
55%
100%
No state.result objects
100%
100%
Unique section UUIDs
100%
100%
Queries have limit clause
0%
100%
Descriptive field names in queries
100%
100%
Standalone .dql files present
100%
100%
build.sh uses jq for validation
100%
100%
Visualization types varied
100%
100%
autoSelectVisualization false
0%
100%
4991356
Table of Contents
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.