Name: scrape-itcloud
Rating: 61.6 (1 reviews)
Author: membranedev

scrape-itcloud

Scrape-It.Cloud integration. Manage Projects, Users, Organizations. Use when the user wants to interact with Scrape-It.Cloud data.

Quality

73%

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/scrape-itcloud/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 body is highly actionable with copy-paste commands and a solid sequenced workflow including polling feedback loops. Its main weakness is conciseness — an opening marketing paragraph and a few padded phrases add tokens Claude doesn't need — and slightly loose step numbering.

Suggestions

Cut the opening "Scrape-It.Cloud is a web scraping platform..." paragraph and other background filler; assume Claude knows what web scraping is.

Tighten the step numbering so the "Step 2" and "1b" references map to explicitly labeled numbered steps, removing the current ambiguity.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Scrape-It.Cloud is a web scraping platform that allows users to extract data from websites. It's used by businesses and individuals...") and a few phrases like "so you can focus on the integration logic rather than auth plumbing" are background/marketing filler Claude does not need, though the bulk is efficient commands.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) plus a complete options table, covering the common cases concretely.	5 / 5
Workflow Clarity	There is a clear sequence (install -> login -> connection ensure -> poll for READY/CLIENT_ACTION_REQUIRED -> search -> run) with explicit state handling and re-poll feedback loops, but numbering is loose ("Step 2" and "1b" appear without matching step labels), leaving minor gaps.	4 / 5
Progressive Disclosure	No bundle files exist, so structure is judged on the single self-contained file; it is well-organized into clear headed sections, though at ~140 lines the connection-state and proxy-options material could plausibly be split out, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

71%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 concise and gives a clear niche plus both a "what" and a "when," but its trigger phrasing is brand-heavy and lacks the natural synonyms a user would actually say. Specificity is good but the verb "manage" is generic.

Suggestions

Expand the trigger clause with natural user phrasings like "scrape a website," "web scraping," or "extract data from a site" rather than relying on the brand name.

Replace the generic verb "Manage" with concrete actions (e.g. "Create, list, and update Projects, Users, and Organizations") to sharpen specificity.

Dimension	Reasoning	Score
Specificity	"Manage Projects, Users, Organizations" names the domain and three concrete entity types, though "manage" is a generic verb rather than enumerated create/list/delete actions, leaving minor coverage gaps.	4 / 5
Completeness	It states both a clear "what" ("Manage Projects, Users, Organizations") and an explicit "Use when the user wants to interact with Scrape-It.Cloud data," though the "when" clause is somewhat generic.	4 / 5
Trigger Term Quality	The trigger relies on the brand name "Scrape-It.Cloud" and "interact with ... data," but lacks common natural phrasings users would say (e.g. "scrape a website," "web scraping," "extract data from a site") and any synonyms.	3 / 5
Distinctiveness Conflict Risk	Naming a specific branded product (Scrape-It.Cloud) gives it a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/scrape-itcloud/SKILL.md
Commit: f484c82

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