Name: zenscrape
Rating: 55.2 (1 reviews)
Author: membranedev

zenscrape

Zenscrape integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zenscrape 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/zenscrape/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 is a well-structured, actionable CLI integration guide with a clear connection-state workflow and feedback loop, held back by some marketing-style padding and placeholder-only action examples rather than a concrete end-to-end walkthrough.

Suggestions

Trim the opening audience/marketing paragraph and promotional phrases ("fastest way to get a connection") to assume Claude's competence.

Add one concrete end-to-end example showing discovery through `membrane action list` to a real `membrane action run` with a Zenscrape-specific actionId and sample input/output.

Label the workflow steps explicitly (Step 1 connection, Step 2 search/run actions) so the "skip to Step 2" reference resolves to a real heading.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening "used by data scientists, researchers, and businesses" framing and promotional phrases like "This is the fastest way to get a connection" are padding Claude does not need.	3 / 5
Actionability	Concrete, executable commands cover the common cases (install, login, connect, poll, search actions, run actions, proxy), but examples rely on placeholders (<actionId>, CONNECTION_ID, QUERY) with no end-to-end run against a real Zenscrape action.	4 / 5
Workflow Clarity	The connection-readiness flow is clearly sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop, but the "skip to Step 2" reference points at a step that is not explicitly labeled.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections with no nested references and an external docs link, but at ~140 lines all CLI reference detail (proxy options, connection states) is inlined rather than split into a reference file.	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 answers both what the skill does and when to use it in third person, but its actions are generic rather than reflecting Zenscrape's actual scraping capabilities and it omits the natural scraping trigger terms a user would say.

Suggestions

Replace generic verbs with concrete Zenscrape actions, e.g. "Scrape web pages, handle CAPTCHAs and proxies, and extract structured data via the Zenscrape API."

Add natural trigger phrases users would say, such as "Use when the user wants to scrape a website, bypass CAPTCHAs/proxies, or extract web data with Zenscrape."

Drop the vague "Manage data, records, and automate workflows" phrasing, which does not describe anything Zenscrape-specific.

Dimension	Reasoning	Score
Specificity	It names the domain ("Zenscrape integration") but the actions are generic ("Manage data, records, and automate workflows") rather than concrete Zenscrape-specific operations like scraping, proxy handling, or CAPTCHA solving.	2 / 5
Completeness	Both "what" (Zenscrape integration; manage data, records, workflows) and "when" ("Use when the user wants to interact with Zenscrape data") are present, though the "when" clause is generic rather than listing concrete triggers.	4 / 5
Trigger Term Quality	The product name "Zenscrape" is a natural trigger, but the description misses common scraping phrases users would actually say ("scrape a website", "web scraping", "extract data from a site").	3 / 5
Distinctiveness Conflict Risk	The named product "Zenscrape" gives it a clear niche with low conflict risk, but the generic action phrasing ("manage data, records") leaves minor overlap with general data-management skills.	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/zenscrape/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.