Name: zenserp
Rating: 52 (1 reviews)
Author: membranedev

zenserp

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

Quality

58%

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/zenserp/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 body is a solid, actionable integration guide with concrete CLI commands and a well-handled connection-state feedback loop. Its main weaknesses are mild verbosity in introductory prose and slightly loose step numbering that prevents the workflow from being fully crisp.

Suggestions

Trim the intro paragraph and the 'so you can focus on the integration logic rather than auth plumbing' line — Claude does not need Zenserp defined or motivational framing.

Replace the loose 'skip to Step 2' / '1b' references with a clearly numbered Step 1 / Step 2 sequence so the connection flow is unambiguous.

Consolidate the duplicated action-listing commands in 'Searching for actions' and 'Popular actions' to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands throughout, but includes unnecessary explanation Claude does not need ('so you can focus on the integration logic rather than auth plumbing') and an introductory paragraph defining Zenserp, fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than the level-4 anchor which has only minor trimmable instances.	3 / 5
Actionability	It provides concrete, executable commands for every step (install, login, connection ensure, action list/run, request) with flag tables and --json usage, with only minor gaps from inherent placeholders (CONNECTION_ID, actionId), matching the 'mostly executable guidance; concrete code or commands with minor gaps' anchor and not level 5 which requires copy-paste-ready coverage of common cases.	4 / 5
Workflow Clarity	The connection workflow has an explicit validation feedback loop — poll until READY, with branch handling for CLIENT_ACTION_REQUIRED and CONFIGURATION_ERROR and re-polling after user action — fitting the 'clear sequence with most checkpoints present' anchor; it stays at 4 rather than 5 because of loose numbering ('skip to Step 2' with no Step 1/Step 2 labels, an orphaned '1b' subsection).	4 / 5
Progressive Disclosure	The single file is well-organized into clear sections with no nested or buried references, and it appropriately delegates action/API discovery to the CLI rather than inlining a catalog, matching the 'good structure; most content appropriately placed' anchor; it does not reach 5 because the content is a flat single file over 50 lines with no one-level-deep reference structure, so the simple-skill exception does not apply.	4 / 5
	Total	15 / 20 Passed

Description

48%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 benefits from a specific product name that gives it a clear trigger and distinctiveness, but the capability statement is generic Membrane boilerplate that fails to convey what Zenserp actually does or surface the natural SERP-related terms users would say.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Zenserp capabilities, e.g. 'Extract search rankings, ads, and featured snippets from search engine results pages.'

Expand the trigger clause to include natural synonyms users say, e.g. 'Use when the user wants SERP data, search rankings, or search results from Zenserp.'

Tie the 'when' more tightly to Zenserp-specific tasks rather than the generic 'interact with Zenserp data'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Zenserp integration') but the actions are generic boilerplate — 'Manage data, records, and automate workflows' — with no concrete Zenserp capabilities such as extracting rankings, ads, or featured snippets, matching the 'names the domain but actions are minimal or generic' anchor rather than the level-3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It has an explicit 'Use when the user wants to interact with Zenserp data' trigger, but the 'what' is vague boilerplate identical across Membrane skills rather than a clear statement of the skill's concrete function, so it does not rise to the level-4 anchor which assumes a clearer 'what'.	3 / 5
Trigger Term Quality	It surfaces the primary natural keyword a user would say ('Zenserp', 'Zenserp data') but omits common variations and synonyms a user might actually voice ('SERP', 'search rankings', 'search results', 'ads', 'featured snippets'), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The product name 'Zenserp' provides a clear, specific trigger that makes it mostly distinct from other skills, with only minor overlap risk from the generic 'manage data, records, and automate workflows' phrasing, matching the 'mostly distinct; minor overlap risk' anchor and not the level-5 anchor whose triggers are equally concrete but more comprehensive.	4 / 5
	Total	12 / 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/zenserp/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.