Name: cisco-meraki
Rating: 60 (1 reviews)
Author: membranedev

cisco-meraki

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

Quality

70%

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-meraki/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.

The skill body is highly actionable with executable CLI commands and clear state-driven connection workflow, plus good section organization. Its main weaknesses are mild background over-explanation and the absence of explicit validation/error-recovery feedback loops for destructive actions.

Suggestions

Trim domain background prose such as the opening 'Cisco Meraki provides cloud-managed IT solutions...' paragraph that Claude already knows.

Add an explicit validate/retry feedback loop for destructive or batch actions (e.g. after 'Create Network' or 'Update Device', show how to verify the result via 'membrane action run get-network' and recover on error).

Consider moving the long 'Popular actions' table into a separate reference file and linking it from the body, so the overview stays lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with command tables and examples, but sections like 'Cisco Meraki provides cloud-managed IT solutions. It's used by network administrators...' explain domain background Claude already knows, and the agent-types and proxy-flag explanations add padding.	3 / 5
Actionability	Commands are concrete and copy-paste ready throughout, e.g. 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://meraki.cisco.com/" --json', and 'membrane action run <actionId> --connectionId=CONNECTION_ID --json', with a populated actions table.	5 / 5
Workflow Clarity	The connect->search->run->proxy flow is clearly sequenced with state-driven checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but there is no validate-after-run or error-recovery feedback loop for batch/destructive actions like create/update.	4 / 5
Progressive Disclosure	Content is well organized into overview, working-with, popular actions, and best-practices sections; the actions table and proxy table inline reasonable reference material, but the large actions table could arguably live in a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

65%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 clear and distinct, naming Cisco Meraki with an explicit 'Use when' trigger, so it answers both what and when. It is held back from the top anchors by generic action language ('data, records, workflows') rather than concrete Meraki operations.

Suggestions

Replace abstract verbs ('Manage data, records, and automate workflows') with concrete Meraki capabilities, e.g. 'List and manage networks, devices, VLANs, and switch ports'.

Add concrete trigger phrases users would naturally say, e.g. 'Use when the user mentions Meraki networks, devices, SSIDs, VLANs, or dashboard administration'.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' name the domain plus generic actions, but 'data' and 'records' are abstract rather than concrete Meraki operations; it does not enumerate specific Meraki actions like networks, devices, VLANs.	3 / 5
Completeness	It has a clear 'what' (Meraki integration that manages data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Cisco Meraki data'); the 'when' trigger is explicit but somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	'Cisco Meraki' plus 'interact with Cisco Meraki data' are natural user phrases with good coverage; it misses common synonyms or product-specific terms like 'Meraki dashboard', 'networks', or 'devices' that a user might say.	4 / 5
Distinctiveness Conflict Risk	'Cisco Meraki' is a clear niche with distinct triggers and low overlap risk against generic skills; the phrase 'Manage data, records' is somewhat generic but the Meraki qualifier keeps it mostly distinct.	4 / 5
	Total	15 / 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-meraki/SKILL.md
Commit: f484c82

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