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

Blog Docs Log in Get started

scraptio

Scraptio integration. Manage Organizations. Use when the user wants to interact with Scraptio 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/scraptio/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 body delivers concrete, executable Membrane/Scraptio commands with a solid connection-state feedback loop and clear sectioning. Its main weaknesses are a duplicated action-discovery section, a broken "Step 2" reference, and minor filler that could be trimmed.

Suggestions

Remove the duplicate "Popular actions" section that restates the `membrane action list --intent=QUERY` example already given under "Searching for actions".

Fix the broken step numbering: either relabel the connect subsections as 1/2 or replace "skip to Step 2" with an explicit link to the "Searching for actions" section.

Trim filler (e.g. "so you can focus on the integration logic rather than auth plumbing") and resolve the `membrane` vs `npx @membranehq/cli` invocation inconsistency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes filler ("so you can focus on the integration logic rather than auth plumbing"), a redundant duplicate of the action-list example under "Popular actions", and the vague line "Use action names and parameters as needed".	3 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection, action search/run, and proxy with a full options table, but mixes `membrane` and `npx @membranehq/cli` invocations and relies on unexplained placeholders (CONNECTION_ID, QUERY, <agentType>), leaving minor gaps.	4 / 5
Workflow Clarity	The connect step has an explicit polling/feedback loop (BUILDING -> poll until READY; CLIENT_ACTION_REQUIRED -> user acts -> poll again), but the sequence is weakened by a dangling "skip to Step 2" reference and a "1b" heading with no labeled "1"/"Step 2".	4 / 5
Progressive Disclosure	No bundle files exist and none are needed; the single file is organized into clear sections (Overview, Working with Scraptio, Best practices) with inline content appropriately placed, though the duplicated action-list section and dangling step references are minor organization gaps.	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 correctly includes both a capability statement and an explicit "Use when" trigger, and the Scraptio brand gives it reasonable distinctiveness. It is weakened by minimal concrete actions and a lack of task-oriented synonyms (scrape, extract, automate) that a user would actually say.

Suggestions

Replace the generic "Manage Organizations" with the concrete Scraptio capabilities the body documents (e.g. create and run scrapes, manage extraction rules, schedule runs, review scraped data).

Expand the trigger clause with natural task phrases users say, e.g. "Use when the user wants to scrape a website, set up extraction rules, schedule scrapes, or review scraped data in Scraptio."

Mirror the body's actual feature set (Scrape, Extraction Rules, Schedule, Notification, Scraped Data, Integration) so the description does not under-sell the skill.

Dimension	Reasoning	Score
Specificity	Names the domain ("Scraptio integration") and one concrete action ("Manage Organizations"), with the rest generic ("interact with Scraptio data"), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Provides both a "what" ("Scraptio integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with Scraptio data"), but the trigger guidance is generic rather than concrete, matching the anchor where 'when' could be more specific.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Scraptio", "Organizations", "Scraptio data") but omits the natural task-oriented synonyms a user would say (scrape, scraping, automation, extract), fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Tying every trigger to the named product "Scraptio" gives it a clear niche with mostly-distinct triggers, though generic phrasing like "Manage Organizations" carries minor overlap risk with org-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/scraptio/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.