CtrlK
BlogDocsLog inGet started
Tessl Logo

webscrapingai

WebScraping.AI integration. Manage data, records, and automate workflows. Use when the user wants to interact with WebScraping.AI data.

53

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/webscrapingai/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 solid, command-heavy integration guide with a well-structured connection workflow and validation via state polling. It loses points for introductory padding, placeholder-only examples, and a monolithic single-file structure with no progressive disclosure.

Suggestions

Trim the introductory paragraph explaining what WebScraping.AI is and the auth-plumbing commentary, since Claude can infer these.

Add one fully worked end-to-end example with concrete (or clearly sample) values rather than only placeholder-laden commands.

Move the proxy options table and agent-type detail into a reference file and link to it one level deep to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly command-driven and efficient, but includes unnecessary introductory explanation ("WebScraping.AI is a web scraping platform that allows users to extract data...") and commentary Claude could infer ("so you can focus on the integration logic rather than auth plumbing").

3 / 5

Actionability

It provides concrete, runnable commands throughout (install, login, connection ensure, action list/run, request) with real flags and a proxy-options table; minor gaps are the unfilled placeholders (CONNECTION_ID, <actionId>) and no fully worked end-to-end example with concrete values.

4 / 5

Workflow Clarity

The connection flow is clearly sequenced with an explicit state machine (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling checkpoints, though the action-running section is less structured.

4 / 5

Progressive Disclosure

Sections are organized, but the skill is a single ~146-line file with no bundle references, and content that could be split (the proxy options table, agent-type detail) is inlined; navigation across files is absent.

3 / 5

Total

14

/

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 is anchored to a distinct product niche and includes an explicit 'Use when' trigger, but its action verbs are generic and it lacks concrete trigger phrases users would naturally say. Tightening the capability list and trigger wording would lift it from adequate to strong.

Suggestions

Replace the generic action list ('Manage data, records, and automate workflows') with concrete WebScraping.AI capabilities such as scraping pages, extracting structured data, and scheduling recurring scrape jobs.

Add natural trigger phrases users would actually say (e.g., 'scrape a website,' 'extract data from a URL,' 'schedule a recurring scrape') alongside the product name.

Sharpen the 'Use when' clause to name the specific intents (scraping, extraction, scheduling) rather than the generic 'interact with WebScraping.AI data.'

DimensionReasoningScore

Specificity

The description names the domain ("WebScraping.AI integration") but the actions — "Manage data, records, and automate workflows" — are minimal and generic rather than concrete capabilities like scraping, extraction, or scheduling.

2 / 5

Completeness

It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with WebScraping.AI data"), though the when clause is generic and could be more specific.

4 / 5

Trigger Term Quality

It includes the natural product-name keyword "WebScraping.AI" and "interact with ... data," but misses common variations or concrete phrases users would actually say (e.g., "scrape a site," "extract data from a URL").

3 / 5

Distinctiveness Conflict Risk

The WebScraping.AI product anchor gives it a clear niche with minimal conflict risk, though the generic "manage data / automate workflows" phrasing leaves minor overlap with other data-integration skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.