Name: scrapingant
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

scrapingant

ScrapingAnt integration. Manage Usages, Invoices. Use when the user wants to interact with ScrapingAnt data.

Quality

65%

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/scrapingant/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 highly actionable with concrete CLI commands and a sensible workflow including a connection-state feedback loop, but it carries some unnecessary explanatory prose and has a small numbering inconsistency in the connection steps.

Suggestions

Cut the introductory paragraph describing what ScrapingAnt is and who uses it; Claude can infer this, and it competes with context tokens.

Fix the broken step navigation: replace "skip to Step 2" with a concrete heading reference and renumber the "1b" block so the install/auth/connect sequence is unambiguous.

Expand or remove the near-empty "Popular actions" section so it either lists representative actions or simply folds into "Searching for actions".

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but the introductory paragraph ("ScrapingAnt is a web scraping API... used by developers and data scientists... market research, SEO monitoring") and phrases like "so you can focus on the integration logic rather than auth plumbing" explain context Claude can infer.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action listing/running, and proxying, plus a flags table; minor gaps are the generic CONNECTION_ID placeholders and the thin "Popular actions" section.	4 / 5
Workflow Clarity	There is a clear sequence (install → auth → connect → search → run) with a polling feedback loop for connection state (BUILDING / CLIENT_ACTION_REQUIRED / READY), though step references are slightly broken ("skip to Step 2" with no labeled Step 2, and a "1b" that disrupts the numbering).	4 / 5
Progressive Disclosure	No bundle files exist and none are needed for this CLI-driven skill; the body is organized into clearly headed sections (Overview, Working with ScrapingAnt, Best practices) with only minor organization gaps in the sparse "Popular actions" section.	4 / 5
	Total	15 / 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 is brand-specific and answers both what and when, but the action list is thin and the trigger terms lean on the product name rather than the natural language a user would actually say.

Suggestions

Add the core capability to the action list, e.g. "Create scraping tasks and retrieve results, manage Usages and Invoices" to raise specificity.

Include natural trigger phrases users would say, such as "web scraping", "extract data from a website", or "ScrapingAnt API", not just the brand name.

Tighten the "Use when" clause to reference concrete intents (e.g. "Use when scraping web pages or managing ScrapingAnt account usage and invoices").

Dimension	Reasoning	Score
Specificity	"Manage Usages, Invoices" names the domain plus two actions, but "Manage" is generic and the coverage is not comprehensive (no mention of scraping tasks/results, the core capability).	3 / 5
Completeness	It has both a "what" ("Manage Usages, Invoices") and an explicit "Use when..." trigger ("Use when the user wants to interact with ScrapingAnt data"), though the "when" could be more specific.	4 / 5
Trigger Term Quality	"ScrapingAnt", "Usages", and "Invoices" are relevant keywords, but common natural variations a user would say ("web scraping", "extract data", "scrape a website") are missing.	3 / 5
Distinctiveness Conflict Risk	"ScrapingAnt integration" is a clear brand-specific niche with minimal conflict risk, though the generic trigger "interact with ScrapingAnt data" leaves minor overlap with adjacent scraping 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/scrapingant/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.