Name: dynatrace-api
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

dynatrace-api

Dynatrace API integration. Manage Organizations. Use when the user wants to interact with Dynatrace API data.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dynatrace-api/SKILL.md

Quality

Content

68%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 highly actionable with copy-paste-ready Membrane CLI commands and a clear connect-to-run workflow with state feedback loops. Its main weaknesses are some conceptual padding at the top, and missing validation/confirmation guidance for the destructive actions it advertises.

Suggestions

Trim the opening paragraph and the 'Dynatrace API Overview' bullet list, which explain concepts Claude already knows and duplicate the 'Popular actions' table.

Add an explicit validation/confirmation step before running destructive actions such as 'Delete Entity Tags' or 'Close Problem' (e.g., list-then-confirm) to lift the workflow-clarity cap.

Consider moving the full action catalog and proxy flag reference into a separate reference file referenced from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening paragraph explaining what the Dynatrace API is and the redundant 'Dynatrace API Overview' section list add unnecessary explanation Claude largely already knows; not score 2 because the bulk is tight command reference, not score 4 because the padding is clearly trimmable.	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases (install, login, connection ensure, action list/run, request proxy) with concrete flags and JSON examples; meets the anchor for fully executable guidance.	5 / 5
Workflow Clarity	The connect-to-run sequence is clear with state feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and re-polling), but destructive actions like 'Delete Entity Tags' and 'Close Problem' are listed with no validation or confirmation guidance before execution, triggering the destructive-operation cap at 3.	3 / 5
Progressive Disclosure	Good section structure with clear headers and easy navigation; no bundle files exist so all content is single-file, with the full action catalog and proxy flag tables inlined rather than split into reference files; not score 5 because reference-like material could be offloaded, not score 3 because organization is solid and references are not buried.	4 / 5
	Total	15 / 20 Passed

Description

73%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 clearly names the Dynatrace API niche and includes an explicit 'Use when' trigger, giving strong distinctiveness and completeness. It is held back by listing only one concrete capability and by limited synonym coverage in its trigger terms.

Suggestions

Add 2-3 more concrete capabilities (e.g., query metrics, list problems, manage entity tags) so the 'what' is comprehensive rather than a single action.

Broaden trigger terms with natural synonyms users might say, such as 'Dynatrace problems', 'Dynatrace metrics', or 'APM monitoring'.

Make the 'when' clause more specific about the kinds of Dynatrace tasks covered (problems, metrics, entities, events) rather than generic 'Dynatrace API data'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Dynatrace API integration') and one concrete action ('Manage Organizations'), matching the anchor for 1-2 concrete actions without comprehensive coverage; not score 2 because an explicit action is named, not score 4 because only one action is listed.	3 / 5
Completeness	Has both a 'what' ('Dynatrace API integration. Manage Organizations.') and an explicit 'when' ('Use when the user wants to interact with Dynatrace API data'); not score 5 because the 'when' is somewhat generic, not score 3 because the trigger clause is explicit rather than weakly implied.	4 / 5
Trigger Term Quality	Includes natural user-facing terms ('Dynatrace API', 'Dynatrace API data', 'Organizations') with good coverage; not score 5 because synonyms and product-name variations are limited, not score 3 because the core terms users would actually say are present.	4 / 5
Distinctiveness Conflict Risk	Dynatrace is a specific APM platform with a distinct niche and 'Dynatrace' as a clear trigger, giving minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/dynatrace-api/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.