Name: parsehub
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

parsehub

ParseHub integration. Manage Projects. Use when the user wants to interact with ParseHub data.

Quality

64%

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/parsehub/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 is a well-structured, actionable CLI integration guide with a clear state-driven workflow and good sectioning. Its main weakness is conciseness: a few introductory and best-practice paragraphs explain context Claude already knows.

Suggestions

Trim the opening paragraph that describes who uses ParseHub and what it extracts; Claude does not need the market context to run the integration.

Cut editorial filler such as 'so you can focus on the integration logic rather than auth plumbing' and restate the 'Discover before you build' best practice as a terse directive.

Replace 'Use action names and parameters as needed' with a concrete one-line example showing how to map an intent query to an action run command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the intro explaining ParseHub's user base ('data analysts, marketers, and researchers') and phrases like 'so you can focus on the integration logic rather than auth plumbing' add unnecessary padding Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands for every stage (install, login, connection ensure, action list/run, request proxy) plus a flags table, but leaves minor gaps such as unresolved placeholders (CONNECTION_ID, actionId) and the vague directive 'Use action names and parameters as needed.'	4 / 5
Workflow Clarity	The install -> authenticate -> connect -> poll-for-ready -> search -> run sequence is clear and includes state-machine checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) with a re-poll feedback loop, though a couple of validation transitions are implicit rather than spelled out.	4 / 5
Progressive Disclosure	All content is inline with no bundle files, but it is organized into well-labeled sections (Overview, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references, fitting the 'good structure, content appropriately placed' anchor.	4 / 5
	Total	15 / 20 Passed

Description

61%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 pairs a 'what' with an explicit 'Use when...' trigger and is highly distinct thanks to the named ParseHub app, but its capability list is thin and generic. Expanding 'Manage Projects' into concrete actions would lift the weakest dimension.

Suggestions

Replace the generic 'Manage Projects' with 2-3 concrete actions, e.g. 'Create and run ParseHub projects, fetch run results, and manage schedules.'

Add natural trigger synonyms/examples to the 'when' clause, such as 'Use when the user mentions ParseHub projects, web scraping runs, or exporting scraped data.'

Dimension	Reasoning	Score
Specificity	The phrase 'Manage Projects' names the domain but offers only a single, generic action with no second concrete capability, matching the 'actions are minimal or generic' anchor rather than the 1-2 concrete actions needed for a 3.	2 / 5
Completeness	It states a 'what' ('ParseHub integration. Manage Projects.') and an explicit 'when' ('Use when the user wants to interact with ParseHub data'), but the 'when' is somewhat generic rather than listing concrete trigger phrases, so it sits at the 'both present, when could be more specific' anchor.	4 / 5
Trigger Term Quality	'ParseHub' and 'ParseHub data' are natural terms a user would say, but the description lacks synonyms, file extensions, or related variations, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'ParseHub integration' names a specific external app with a clear niche and distinct triggers, giving minimal overlap risk with other skills.	5 / 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/parsehub/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.