Name: wp-maps
Rating: 55.2 (1 reviews)
Author: membranedev

wp-maps

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

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/wp-maps/SKILL.md

Quality

Content

67%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 content delivers concrete, executable Membrane CLI guidance with a sensible connection-readiness workflow and feedback loops. It would benefit from trimming redundant/explanatory prose, fixing the dangling "Step 2" reference, and adding result validation after action runs.

Suggestions

Remove the redundant "Popular actions" section (it repeats the `membrane action list` command already shown under "Searching for actions") and trim the intro/aside explaining concepts Claude can infer.

Fix the dangling "skip to Step 2" reference by labeling the next section as Step 2 or rewording the pointer to the actual "Searching for actions" section.

Add a validation/inspection step after `membrane action run` (e.g. checking the `output` field or re-querying) so the workflow has an explicit checkpoint for destructive or batch actions.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the intro explaining what WP Maps is and who uses it, the "focus on integration logic rather than auth plumbing" aside, and a redundant "Popular actions" section repeating the search command add unnecessary tokens.	3 / 5
Actionability	Copy-paste-ready `membrane` commands with `--json`, JSON input passing, and a proxy flag table give mostly executable guidance, with minor gaps where placeholders (CONNECTION_ID, actionId) are used instead of a fully concrete end-to-end example.	4 / 5
Workflow Clarity	A clear sequence (install, authenticate, connect, poll readiness, search, run/proxy) includes feedback loops on connection state (READY/CLIENT_ACTION_REQUIRED/re-poll), but "skip to Step 2" references a missing Step 2 header and there is no result validation after running actions.	4 / 5
Progressive Disclosure	The single file is well-organized with clear section headers and a signaled external docs link, and no bundle files are needed; at over 50 lines with some splittable content (proxy flags, agent types) it is good but not a model 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly includes an explicit "Use when..." trigger and names the WP Maps niche, but its capability claims are generic boilerplate rather than concrete WP Maps actions. Tightening the action list to real WP Maps capabilities would lift specificity and distinctiveness.

Suggestions

Replace generic boilerplate ("Manage data, records, and automate workflows") with concrete WP Maps actions such as creating maps, adding markers, managing categories, and embedding maps.

Expand the trigger clause with natural user phrases like "maps", "markers", "embed a map", or "WordPress maps" to improve trigger-term coverage.

Make the "when" clause more specific, e.g. "Use when the user wants to create or edit WP Maps maps, add markers, or embed maps on a WordPress site."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" are generic abstract actions rather than concrete WP Maps capabilities (maps, markers, categories), matching the anchor that names the domain but with minimal/generic actions.	2 / 5
Completeness	It provides both a "what" ("WP Maps integration. Manage data, records, and automate workflows.") and an explicit "Use when the user wants to interact with WP Maps data" trigger, but the "what" is generic and the "when" could be more specific.	4 / 5
Trigger Term Quality	"WP Maps" and "WP Maps data" are natural product-name keywords a user would say, but common variations like "maps", "markers", or "embed map" are missing, matching the some-relevant-keywords anchor.	3 / 5
Distinctiveness Conflict Risk	"WP Maps" names a specific product niche with a distinct trigger, but the "Manage data, records, and automate workflows" phrasing is boilerplate shared across Membrane integration skills, creating minor overlap risk.	4 / 5
	Total	13 / 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/wp-maps/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.