Name: octoparse
Rating: 60 (1 reviews)
Author: membranedev

octoparse

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

Quality

70%

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

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 content is highly actionable with concrete CLI commands and a well-sequenced connection workflow, but it carries some verbosity and a dangling 'Step 2' reference that mildly hurt conciseness and workflow clarity.

Suggestions

Trim the opening background paragraph and the bare 'Octoparse Overview' bullet list, or replace them with a one-line summary of what Octoparse does.

Define 'Step 2' explicitly (e.g. add a numbered 'Step 2: Search for and run actions' heading) so the 'skip to Step 2' references resolve.

Add a final validation check after running actions (e.g. inspect the `output` field and handle non-READY/error states) to close the workflow loop.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient CLI guidance, but the opening background paragraph ('Octoparse is a web scraping tool...'), the bare 'Octoparse Overview' term list, and repeated `membrane action list` examples add padding that could be trimmed.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands for install, login, connection setup, action discovery/run, and proxy requests, plus a flags table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling/retry feedback loops, but the referenced 'Step 2' is never explicitly defined and there is no final success-validation step.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and no separate files needed for this single cohesive integration guide, though it exceeds the simple-skill line threshold that would warrant a 5.	4 / 5
	Total	16 / 20 Passed

Description

66%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 distinct and answers both 'what' and 'when', but its action language is generic and it misses the natural scraping/extraction trigger terms a user would actually say.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Extract and export web-scraped data, manage task records, and automate Octoparse workflows.'

Add natural trigger phrases such as 'web scraping', 'scrape data', or 'extract data from websites' to the 'Use when...' clause.

Make the 'when' clause more specific, e.g. 'Use when the user wants to scrape websites, manage Octoparse tasks, or export extracted data.'

Dimension	Reasoning	Score
Specificity	Names the domain ('Octoparse integration') and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete capabilities like web scraping or data extraction.	3 / 5
Completeness	States both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Octoparse data'), though the 'when' trigger could be more specific.	4 / 5
Trigger Term Quality	Includes the brand keyword 'Octoparse' plus generic terms ('data', 'records', 'workflows'), but omits natural phrases users would say such as 'web scraping', 'scrape', or 'extract data from websites'.	3 / 5
Distinctiveness Conflict Risk	Tied to a named product (Octoparse) with a brand-based trigger, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/octoparse/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.