Name: webscraperio
Rating: 60 (1 reviews)
Author: membranedev

webscraperio

WebScraper.IO integration. Manage data, records, and automate workflows. Use when the user wants to interact with WebScraper.IO 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/webscraperio/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 content is highly actionable with executable Membrane CLI commands and a clear connection workflow featuring state checkpoints. It would benefit from trimming the marketing intro and redundant action-list section, and from labeling the referenced "Step 2".

Suggestions

Cut the introductory marketing paragraph ("Web Scraper.IO is a cloud-based web scraping tool...") — Claude does not need the product pitch, only the integration mechanics.

Remove or merge the redundant "Popular actions" section, which repeats the `membrane action list` command already shown under "Searching for actions".

Label the "Searching for actions" / "Running actions" sections as "Step 2" (and the connection section as "Step 1") so the inline "skip to Step 2" references resolve clearly.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the marketing-style intro ("Web Scraper.IO is a cloud-based web scraping tool... used by businesses and individuals") and the redundant "Popular actions" section repeating the action-list command are unnecessary padding that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready `membrane` commands for login, connection ensure, polling, action list/run, and proxy requests, plus a concrete flag table and JSON input examples covering the common cases.	5 / 5
Workflow Clarity	The connect→wait→search→run flow is sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but "Step 2" is referenced without a correspondingly labeled section, leaving a minor gap.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized with clear section headers and an inlined flag table; content is appropriately placed with only minor organization gaps given the length.	4 / 5
	Total	16 / 20 Passed

Description

66%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 successfully pairs a what with an explicit Use-when trigger and is anchored to a distinct branded product. Its main weaknesses are generic action verbs and a limited set of natural trigger terms.

Suggestions

Replace generic verbs ("Manage data, records") with concrete WebScraper.IO capabilities such as "create scraping sitemaps, run scrapes, schedule crawls, and export extracted records".

Add natural trigger synonyms users would actually say, e.g. "Use when the user wants to scrape a website, extract web data, or run a WebScraper.IO sitemap/crawl."

Tighten the when clause to reference concrete intents (scraping, scheduling crawls, exporting scraped data) rather than the vague "interact with WebScraper.IO data".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the WebScraper.IO domain plus a couple of actions, but the actions are generic rather than concrete (e.g. no "extract", "schedule", "scrape" specifics), fitting the 1-2-concrete-actions anchor.	3 / 5
Completeness	It states both the what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with WebScraper.IO data"), but the when clause is somewhat generic and could be more specific, matching the both-present-but-when-could-be-sharper anchor.	4 / 5
Trigger Term Quality	The trigger relies on the brand name "WebScraper.IO" and the generic word "data"; it omits natural user phrases like "web scraping", "scrape a website", or "extract data from a site", matching the some-keywords-but-missing-synonyms anchor.	3 / 5
Distinctiveness Conflict Risk	The named, branded product "WebScraper.IO" creates a clear niche with distinct triggers and minimal risk of conflicting with other skills.	5 / 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/webscraperio/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.