Name: zyte-api
Rating: 56.8 (1 reviews)
Author: membranedev

zyte-api

Zyte API integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zyte API 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/zyte-api/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 strongly actionable, well-sequenced guide to driving Zyte API through the Membrane CLI, with executable commands and a clear connection state machine. Its main weaknesses are minor padding, a few empty/under-delivered sections (Overview bullets, Popular actions), and slightly inconsistent step labeling.

Suggestions

Trim opinion/padding lines such as the target-audience sentence and "so you can focus on the integration logic rather than auth plumbing" to keep the body lean.

Fill or remove the empty "Zyte API Overview" bullets and either list actual popular actions under "Popular actions" or rename the section to match its search-command content.

Normalize the connection walkthrough step numbering (label "Step 2" explicitly or drop the "1b" / "Skip to Step 2" references) so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and concrete guidance, but includes unnecessary commentary Claude does not need, e.g. "It's used by developers and data scientists who need reliable web scraping without managing infrastructure" and "so you can focus on the integration logic rather than auth plumbing"; this matches the mostly-efficient-with-some-unnecessary-explanation anchor, not a 4 because the padding is noticeable.	3 / 5
Actionability	Provides many copy-paste-ready commands (npm install, membrane login, connection ensure, action run with --input JSON) plus a thorough proxy-flags table; matches the mostly-executable anchor with minor gaps such as unsubstituted CONNECTION_ID placeholders and a "Popular actions" section that restates the search command without listing any actual actions; not a 5 because of those gaps.	4 / 5
Workflow Clarity	Sequences install -> auth -> connect -> search -> run with an explicit connection state machine (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling feedback loops for error recovery, matching the clear-sequence-with-most-checkpoints anchor; not a 5 because step labeling is inconsistent ("1b" and references to a "Step 2" that is not labeled) and action-run success is not explicitly validated.	4 / 5
Progressive Disclosure	Single well-organized SKILL.md with clear sections and no nested references (no bundle files exist), matching the good-structure anchor; not a 5 because the "Zyte API Overview" section is a list of empty bullets (Extraction, Account, Billing, etc.) and "Popular actions" promises content it does not deliver, which 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 covers both what the skill does and when to use it, scoped clearly to Zyte API, but relies on generic action verbs ("manage data, records, automate workflows") and omits natural trigger synonyms like scraping/extraction. It is functional but could be sharpened with concrete capabilities and richer trigger terms.

Suggestions

Replace generic verbs with concrete Zyte capabilities, e.g. "Extract structured data from websites, run extraction jobs, and manage account usage and billing via Zyte API."

Add natural trigger synonyms users actually say, such as "web scraping", "Scrapinghub", "extract data", or "Zyte API extraction".

Expand the 'Use when' clause with concrete triggers, e.g. "Use when the user wants to extract data from websites via Zyte API, run extraction jobs, or check Zyte usage and billing."

Dimension	Reasoning	Score
Specificity	Names the domain ("Zyte API integration") and lists multiple actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete, fitting the anchor that names the domain with 1-2 non-comprehensive actions; not a 2 because more than one action is given, not a 4 because no specific concrete capabilities (e.g. extraction, proxies) are stated.	3 / 5
Completeness	Explicitly states both what ("Zyte API integration. Manage data, records, and automate workflows.") and when ("Use when the user wants to interact with Zyte API data."), matching the anchor where both are present but the 'when' could be more specific; not a 5 because the trigger is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant natural terms ("Zyte API", "data", "records", "workflows") but misses common synonyms and variations users would say ("scraping", "Scrapinghub", "extraction", "web scraping"), matching the anchor for some relevant keywords with missing variations; not a 4 because natural-term coverage is thin.	3 / 5
Distinctiveness Conflict Risk	Scoped to a specific product ("Zyte API") with a trigger tied to that product ("interact with Zyte API data"), making it mostly distinct with minor overlap risk from the generic 'manage data' phrasing; not a 5 because the 'what' uses generic data-management language that could brush other data 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/zyte-api/SKILL.md
Commit: f484c82

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