Name: outscraper
Rating: 51.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

outscraper

Outscraper integration. Manage Organizations. Use when the user wants to interact with Outscraper data.

Quality

56%

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/outscraper/SKILL.md

Quality

Content

56%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 action-rich with executable Membrane CLI commands and a well-handled connection state machine, but it is bloated by a massive inlined action enumeration that should be split into a reference file. Workflow and actionability are solid; conciseness and progressive disclosure are the weak points.

Suggestions

Move the ~140-item "Outscraper Overview" action catalog into a separate reference file (e.g. references/actions.md) and keep only a concise categorized summary in SKILL.md.

Add one fully worked end-to-end example showing a real action invocation and its JSON output to lift actionability from concrete to copy-paste-complete.

Trim the opening paragraph that explains what Outscraper is and collapse the duplicated "Popular actions" section, which repeats the action-list command already shown above.

Dimension	Reasoning	Score
Conciseness	The body inlines a ~140-entry enumeration of "Find Company By ..." actions that is heavily padded with near-duplicate items, plus an explanatory opener about what Outscraper is; this is noticeably verbose with padded sections, fitting the score-2 anchor rather than a 3 because the padding is substantial.	2 / 5
Actionability	It provides concrete, executable CLI commands throughout (install, login, connection ensure/get, action list/run, request proxy) with a flag table; it is mostly executable and copy-paste ready, but lacks a fully worked end-to-end example with real values and output, keeping it at 4 rather than 5.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-and-retry feedback loop, but there is no validation step for action results and steps are spread across sections, leaving minor gaps that cap it at 4.	4 / 5
Progressive Disclosure	There is section-level structure, but the ~140-line action catalog is inlined content that clearly belongs in a separate reference file and no bundle/reference files are signaled, matching the score-3 anchor of structure with content that should be separate kept inline; it is not a 2 because headers do provide reasonable organization.	3 / 5
	Total	13 / 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 provides an explicit trigger clause and a distinct brand niche, but its capability statement is thin and generic ("Manage Organizations") and lacks concrete action detail or natural task synonyms. It is adequate but underspecified for what the skill actually does.

Suggestions

Replace the generic "Manage Organizations" with concrete capabilities, e.g. "Scrape Google Search, Maps, Reviews, and social-media data via Outscraper APIs."

Broaden trigger terms with natural synonyms users say, such as "scrape search results", "SERP data", "Google Maps reviews", or "lead generation".

Tighten the "when" clause to name specific intents, e.g. "Use when the user wants to scrape SERP, Maps, app-store, or social-media data from Outscraper."

Dimension	Reasoning	Score
Specificity	The description names the domain ("Outscraper integration") and a single generic action ("Manage Organizations") with no concrete scraping capabilities, matching the anchor that names the domain but has minimal/generic actions; it is not a 3 because no concrete actions are enumerated, and not a 1 because a domain and an action are named.	2 / 5
Completeness	Both a "what" ("Outscraper integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with Outscraper data.") are present; the trigger clause is explicit so it is not capped at 3, but the "what" is vague and the "when" could be more specific, so it stops at 4 rather than 5.	4 / 5
Trigger Term Quality	It includes the strong brand keyword "Outscraper" and "interact with Outscraper data", but lacks common variations or synonyms for the underlying tasks (scraping, SERP, reviews, etc.); some relevant keywords are present but coverage is incomplete, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	The brand "Outscraper" gives it a clear niche with distinct triggers and low conflict risk, but the generic phrase "Manage Organizations" introduces minor overlap with organization-management skills, placing it at 4 rather than a fully distinct 5.	4 / 5
	Total	13 / 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/outscraper/SKILL.md
Commit: f484c82

Reviewed: 5 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.