CtrlK
BlogDocsLog inGet started
Tessl Logo

simplescraper

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

55

Quality

62%

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

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 a lean, highly actionable CLI integration guide with concrete commands and a well-sequenced connection-readiness workflow including feedback loops. Its main weaknesses are minor marketing-style padding and a lack of explicit post-run validation.

Suggestions

Trim non-executable padding such as the audience description ('used by marketers, researchers, and analysts...') and the 'so you can focus on the integration logic' phrasing.

Add an explicit validation step after running actions (e.g. check the 'output' field and handle error states) to close the workflow's feedback loop.

Consider moving the proxy flag reference table into a small reference file so the main body stays a concise overview.

DimensionReasoningScore

Conciseness

The body is mostly command-focused and efficient, but includes unnecessary padding such as the 'used by marketers, researchers, and analysts...' sentence and the 'so you can focus on the integration logic rather than auth plumbing' phrasing that could be trimmed.

3 / 5

Actionability

It provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure, action list/run, request/proxy) with concrete flags and JSON examples.

5 / 5

Workflow Clarity

There is a clear sequence (install → auth → connect → poll for ready → search → run/proxy) with explicit state-based feedback loops for connection readiness, though post-action validation is only implied.

4 / 5

Progressive Disclosure

The single SKILL.md is well organized into clear sections with no nested references and an appropriate external docs link; minor gaps are the inlined proxy flag table and popular-actions content that could optionally live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

50%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 has an explicit 'Use when' clause and a clear domain anchor, but its action language is generic and omits the scraping/extraction vocabulary that would make it concrete and triggerable. It is adequate but could be sharpened with Simplescraper-specific verbs and natural scraping terms.

Suggestions

Replace generic verbs with concrete Simplescraper actions, e.g. 'Scrape websites, extract data, and monitor pages for changes.'

Add natural user-facing trigger terms like 'web scraping', 'extract data from a website', or 'scrape a site' alongside the brand name.

Tighten the 'Use when' clause to specific scenarios such as 'Use when the user wants to scrape a website or extract structured data using Simplescraper.'

DimensionReasoningScore

Specificity

It names the domain (Simplescraper) but the listed actions ('Manage data, records, and automate workflows') are generic and never mention the tool's actual scraping capabilities, so it reads as minimal/generic rather than concrete.

2 / 5

Completeness

Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Simplescraper data') are present, though the trigger could be more specific.

4 / 5

Trigger Term Quality

The only natural keyword is the brand name 'Simplescraper' plus the generic 'data'; it is missing the natural scraping phrases a user would actually say ('scrape', 'extract data', 'web scraping').

2 / 5

Distinctiveness Conflict Risk

The brand-anchored trigger ('interact with Simplescraper data') makes it mostly distinct, though the generic action verbs create minor overlap risk with other data-management skills.

4 / 5

Total

12

/

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.