Name: scrapeninja
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

scrapeninja

ScrapeNinja integration. Manage Projects, Proxies, Users. Use when the user wants to interact with ScrapeNinja data.

Quality

68%

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/scrapeninja/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 executable Membrane CLI commands and a solid connection-state feedback loop. The main weaknesses are mild verbosity in the intro and a dangling 'Step 2' cross-reference.

Suggestions

Trim the opening paragraph's background on what web scraping is and who uses it; Claude already knows this.

Fix the 'skip to Step 2' references by labeling the steps (Step 1, Step 2) or removing the dangling cross-references.

Add a brief validation note for `membrane action run` (e.g. check the `output` field and handle non-READY/error states) since managing Projects/Proxies/Users can be mutating.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient CLI commands, but the opening paragraph explains what a web scraping API is and who uses it, and the 'Popular actions' section repeats the `action list` command already shown under 'Searching for actions'.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connect, poll, search actions, run actions, proxy requests) plus a flags table and explicit output-field guidance.	5 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-state sequence with a feedback loop for connection states (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the 'skip to Step 2' references point to unlabeled steps and there is no validation of action-run results.	4 / 5
Progressive Disclosure	The single file is well organized with clear section headers and no nested references, but at ~140 lines some detail (the connection-state handling, the proxy flags table) is inlined rather than split into one-level-deep reference files.	4 / 5
	Total	16 / 20 Passed

Description

62%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 answers both what and when with an explicit trigger clause and is anchored to a distinct brand niche. It is held back by the generic 'Manage' verb and thin trigger-term coverage.

Suggestions

Replace the generic 'Manage' with concrete verbs, e.g. 'Create, list, update, and delete ScrapeNinja Projects, Proxies, and Users'.

Broaden the trigger phrase to natural variations users say, e.g. 'Use when the user wants to scrape websites, rotate proxies, or manage ScrapeNinja projects, proxies, or users'.

Make the 'when' clause more specific by tying it to concrete ScrapeNinja tasks rather than the generic 'interact with ScrapeNinja data'.

Dimension	Reasoning	Score
Specificity	It names the domain ('ScrapeNinja integration') and three concrete objects ('Manage Projects, Proxies, Users'), but the single generic verb 'Manage' is not a set of distinct concrete actions, so coverage is not comprehensive.	3 / 5
Completeness	Both 'what' ('Manage Projects, Proxies, Users') and 'when' ('Use when the user wants to interact with ScrapeNinja data') are present, but the trigger phrase is generic rather than concrete.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with ScrapeNinja data' supplies the brand keyword but lacks natural variations or synonyms users might say, so it is only moderately covered.	3 / 5
Distinctiveness Conflict Risk	The ScrapeNinja brand name plus the specific Proxies/scraping entities give it a clear niche with minimal conflict risk, though 'Manage Projects, Users' could lightly overlap with general management skills.	4 / 5
	Total	14 / 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/scrapeninja/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.