Name: apify
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

apify

Apify integration. Manage Actors, Datasets, KeyValueStores, RequestQueues, Tasks. Use when the user wants to interact with Apify data.

Quality

66%

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/apify/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 guide with a strong connection-state workflow, weakened mainly by some promotional padding and an oversized inline actions table.

Suggestions

Trim audience/marketing fluff such as the 'data scientists, marketers, and researchers' sentence and the 'focus on the integration logic' aside.

Move the 'Popular actions' table into a references file and keep only a brief pointer plus a few representative examples inline.

Add an explicit verification step after 'action run' (e.g., check the 'output' field for errors/status) to close the workflow feedback loop for run operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but includes unnecessary padding such as 'It's used by data scientists, marketers, and researchers for tasks like lead generation, market research, and content monitoring' and motivational prose like 'so you can focus on the integration logic rather than auth plumbing'.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request) plus a table of action keys, with only minor gaps such as placeholder values for actionId/input.	4 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit checkpoints and a feedback loop (poll --wait, READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR handling), though the action-running step lacks an explicit verification of the returned output.	4 / 5
Progressive Disclosure	No bundle files exist and the content is self-contained with well-organized section headers; the main gap is the large inline 'Popular actions' table that could live in a separate reference file.	4 / 5
	Total	15 / 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 cleanly identifies its niche and includes an explicit 'Use when' clause, but relies on a single generic action verb and a narrow trigger phrase, leaving it short of the strongest anchor examples.

Suggestions

Replace the single verb 'Manage' with several distinct concrete actions (e.g., 'Run Actors and Tasks, fetch Dataset items, read Key-Value Store records, queue Requests').

Broaden the trigger phrase to include natural user terms like 'web scraping', 'data extraction', or 'running Apify Actors' rather than only 'interact with Apify data'.

Dimension	Reasoning	Score
Specificity	It names the domain and several concrete resource types ('Manage Actors, Datasets, KeyValueStores, RequestQueues, Tasks') but the only action verb is the generic 'Manage', so it does not list multiple distinct concrete actions per the anchor 4/5 examples.	3 / 5
Completeness	It answers both 'what' (manage named Apify resources) and 'when' ('Use when the user wants to interact with Apify data'), but the 'when' clause is somewhat generic and could name more concrete trigger situations, so it falls short of the anchor 5 example.	4 / 5
Trigger Term Quality	The natural keyword 'Apify' and the trigger 'interact with Apify data' are present, but it misses common synonyms a user might say (web scraping, data extraction, running Actors) that the body itself references.	3 / 5
Distinctiveness Conflict Risk	'Apify integration' is a clear, branded niche with distinct triggers and minimal overlap 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/apify/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.