CtrlK
BlogDocsLog inGet started
Tessl Logo

scrapingbee

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

61

Quality

72%

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/scrapingbee/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 copy-paste-ready Membrane CLI commands and a clear, well-sequenced workflow including connection-state feedback loops. Minor conciseness padding and a few organization/numbering gaps keep it just below the top level.

DimensionReasoningScore

Conciseness

The body is mostly lean and command-driven with only minor padding (e.g. "so you can focus on the integration logic rather than auth plumbing" and the marketing-style intro), so it is efficient with small trimmable instances rather than fully lean.

4 / 5

Actionability

It provides copy-paste-ready executable commands throughout (login, connection ensure, action run, request) with a complete flag table, covering the common ScrapingBee integration cases.

5 / 5

Workflow Clarity

A clear install→login→connect→poll→search→run sequence exists with feedback loops (poll until READY, retry after CLIENT_ACTION_REQUIRED), but the dangling "skip to Step 2" reference with no labeled Step 2 and no verification of action results leaves minor gaps.

4 / 5

Progressive Disclosure

The single file is well-organized into clearly labeled sections with no external references, but at over 50 lines some inlineable detail (clientAction states, the proxy options table) could be split out, so it is good but not exemplary.

4 / 5

Total

17

/

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 correctly includes both a what and a Use-when clause and benefits from a distinctive brand name, but it is thin on concrete actions and natural trigger synonyms. Tightening the action verbs and adding user-facing keywords would lift the weaker dimensions.

Suggestions

Replace the generic "Manage Projects, Users" with specific verbs, e.g. "List, create, and update ScrapingBee Projects and Users" to improve specificity.

Add natural trigger keywords and synonyms users actually say, such as "web scraping", "scrape a URL", or "extract data from websites", to broaden trigger-term coverage.

Make the Use-when clause more concrete by listing triggering phrases, e.g. "Use when the user wants to scrape a website, rotate proxies, or manage ScrapingBee projects and users."

DimensionReasoningScore

Specificity

"Manage Projects, Users" names the ScrapingBee domain and two actions, but "Manage" is generic and the coverage is not comprehensive, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

It answers both "what" ("Manage Projects, Users") and "when" ("Use when the user wants to interact with ScrapingBee data"), but the trigger clause is generic rather than listing concrete trigger phrases, so it stops short of a 5.

4 / 5

Trigger Term Quality

The only natural keyword is "ScrapingBee" (repeated); common variations users would say like "web scraping", "scrape", or "extract data" are missing, so keyword coverage has gaps.

3 / 5

Distinctiveness Conflict Risk

"ScrapingBee" is a distinctive named brand giving a clear niche with minimal conflict risk, but the generic "interact with ScrapingBee data" trigger keeps it just below the top anchor.

4 / 5

Total

14

/

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.