Name: cisco-appdynamics
Rating: 61.6 (1 reviews)
Author: membranedev

cisco-appdynamics

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

Quality

73%

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

Quality

Content

75%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.

A highly actionable CLI integration skill with concrete commands, clear connection-state checkpoints, and good section structure. Its main weakness is mild verbosity in the introductory prose and some over-explanation of the AppDynamics product itself.

Suggestions

Trim the opening paragraph that explains what AppDynamics is; Claude already knows it is an APM platform — keep only the integration-relevant framing.

Fix the dangling 'skip to Step 2' reference by either adding a numbered 'Step 2' header or rewording to 'skip to Searching for actions'.

Consider moving the proxy flag table and CLIENT_ACTION_REQUIRED state details into a reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but the opening paragraph over-explains what AppDynamics is and the prose intros ('This skill uses the Membrane CLI...', 'Membrane handles authentication...') add mild padding Claude does not need.	3 / 5
Actionability	Fully executable, copy-paste-ready membrane commands cover install, login (incl. headless), connection ensure/wait, action list/run, and proxy requests, plus a flag table for common options.	5 / 5
Workflow Clarity	Clear sequence (install → login → ensure connection → wait for READY → search actions → run) with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR); step numbering is slightly loose ('skip to Step 2' with no matching Step 2 header).	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no nested references; there are no bundle files to link to, and the inline content (proxy flag table, state handling) is reasonably placed, though the proxy reference could live in a separate file.	4 / 5
	Total	16 / 20 Passed

Description

71%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.

A solid description that clearly identifies the AppDynamics niche and includes an explicit 'Use when' trigger clause. The main weakness is that the listed capabilities are somewhat generic rather than tied to AppDynamics-specific actions.

Suggestions

Replace generic verbs ('Manage data, records') with AppDynamics-specific actions, e.g. 'Query application health rules, business transactions, and metric data'.

Expand the 'when' clause with concrete trigger phrases users would say, such as 'Use when the user wants to query AppDynamics metrics, health rules, events, or business transactions'.

Add a common synonym or abbreviation (e.g. 'APM') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete AppDynamics-specific operations.	3 / 5
Completeness	Both 'what' (integration, manage data/records, automate workflows) and 'when' ('Use when the user wants to interact with Cisco AppDynamics data') are present; the 'when' is explicit but could list more concrete trigger phrases.	4 / 5
Trigger Term Quality	'Cisco AppDynamics' is a strong, natural trigger term and is repeated, but a few common variations (e.g. 'APM', 'monitoring') are absent.	4 / 5
Distinctiveness Conflict Risk	'Cisco AppDynamics integration' carves a clear niche with distinct triggers and minimal risk of firing for unrelated 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/cisco-appdynamics/SKILL.md
Commit: f484c82

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