Name: instana
Rating: 50.4 (1 reviews)
Author: membranedev

instana

Instana integration. Manage data, records, and automate workflows. Use when the user wants to interact with Instana data.

Quality

55%

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/instana/SKILL.md

Quality

Content

48%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 operational core is genuinely useful with executable commands and a clear connection workflow, but it is buried under an enormous, largely irrelevant entity enumeration that wrecks token efficiency and should be moved to a reference file. Trimming that list would lift both conciseness and progressive disclosure.

Suggestions

Remove or move the ~290-line entity bullet list to a references file (e.g. references/entities.md) and replace it with a one-line pointer; drop entries unrelated to Instana (Metaverse, Blockchain, Robotics, etc.) entirely.

Add a brief validation/verification step after running an action (e.g. check the `output` field and handle non-2xx/error states) to strengthen workflow checkpoints.

Tighten the Best Practices section so it stays lean and assumes Claude's competence rather than restating CLI behavior already covered above.

Dimension	Reasoning	Score
Conciseness	The body leads with ~290 lines of bullet-pointed entity names ("Dashboard", "Metaverse", "Blockchain", "Quantum Computing", "Robotics"), much of it irrelevant to Instana, which is severe padding that crowds the context window; this matches the 'severely verbose; heavily padded' anchor despite the otherwise reasonable operational sections.	1 / 5
Actionability	It provides concrete, copy-pasteable commands for the common cases (npm install, membrane login, connection ensure, action list/run, request proxy) with flag tables and JSON examples, fitting 'mostly executable guidance; concrete code with minor gaps' rather than the fully exhaustive anchor 5.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced (install -> auth -> connection ensure -> poll until READY -> handle CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR -> search -> run) with explicit state-based checkpoints and an error-recovery loop, matching 'clear sequence with most checkpoints present' with only minor gaps.	4 / 5
Progressive Disclosure	There are no bundle files and the huge entity list is inlined directly in SKILL.md where it belongs in a separate reference file, but the operational sections have reasonable structure, landing on 'some structure but content that should be separate is inline' rather than the minimal-structure anchor 2.	3 / 5
	Total	12 / 20 Passed

Description

62%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 in proper third person and explicitly includes a 'Use when' trigger, covering both what and when. Its main weakness is generic action language and thin trigger-term coverage beyond the product name.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Instana capabilities (e.g., query metrics, inspect traces, manage alerts and dashboards).

Expand the trigger phrase with natural user language and synonyms, e.g. "Use when the user wants to query Instana metrics, investigate traces, or manage Instana alerts and dashboards."

Add file/extension or API hints where relevant to strengthen trigger-term quality and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (Instana) and a few actions ("Manage data, records, and automate workflows"), but the actions are generic and not comprehensive, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor rather than the more specific anchor above.	3 / 5
Completeness	It has both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Instana data"), but the 'when' is generic and could be more specific, fitting anchor 4 rather than the concrete-trigger anchor 5.	4 / 5
Trigger Term Quality	The primary natural keyword is the product name "Instana" and the phrase "interact with Instana data", but it lacks synonyms or common variations users might say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The "Instana integration" niche is distinct and the product name is an unlikely conflict trigger, but the generic action verbs ("manage data", "records") leave minor overlap risk with adjacent observability skills, so it sits at anchor 4 rather than 5.	4 / 5
	Total	14 / 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/instana/SKILL.md
Commit: f484c82

Reviewed: 5 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.