apify-actorization

Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output.

Quality

62%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/apify-actorization/SKILL.md

Quality

Discovery

40%

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 clearly identifies a specific niche (Apify platform actorization) and explains the concept of Actors well, giving it strong distinctiveness. However, it lacks explicit trigger guidance ('Use when...') and doesn't enumerate specific concrete actions the skill performs, weakening its utility for skill selection. Adding trigger terms and a 'Use when' clause would significantly improve it.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to convert code into an Apify Actor, deploy to Apify, create a web scraper or automation on the Apify platform.'

List specific concrete actions the skill performs, such as 'scaffolds Actor projects, configures Dockerfile and input schema, integrates Apify SDK, handles storage and dataset output.'

Include natural trigger terms users might say, such as 'Apify Actor', 'web scraping', 'crawlee', 'deploy actor', 'Apify SDK', or 'serverless scraper'.

Dimension	Reasoning	Score
Specificity	The description names the domain (converting software to serverless apps on Apify) and describes the general concept of Actors (Docker images, JSON input/output), but doesn't list multiple specific concrete actions like scaffolding, configuring, deploying, or testing.	2 / 3
Completeness	The description explains what actorization is (the 'what'), but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'Apify', 'Actors', 'serverless', 'Docker images', and 'JSON input/output', but misses common user variations like 'deploy to Apify', 'create an actor', 'web scraper', 'Apify SDK', or 'crawlee'. The term 'actorization' is domain-specific jargon that users may not naturally use.	2 / 3
Distinctiveness Conflict Risk	The description is highly specific to the Apify platform and the concept of Actors, making it very unlikely to conflict with other skills. The niche of converting software into Apify-compatible serverless applications is quite distinct.	3 / 3
	Total	8 / 12 Passed

Implementation

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured actorization skill with excellent workflow clarity and progressive disclosure. The content is highly actionable with concrete commands and checklists throughout. Minor conciseness issues exist with some sections that could be trimmed (When to Use, Limitations boilerplate, Monetization) but overall the skill is effective and well-organized.

Suggestions

Remove or significantly trim the 'When to Use This Skill' section—Claude can infer applicability from the description and content.

Consider moving the 'Monetization' section to a reference file since it's optional and adds ~10 lines to the main skill body.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some unnecessary content like the 'When to Use This Skill' section (Claude can infer this), the 'Limitations' boilerplate at the end, and the 'Monetization' section which adds bulk. The prerequisites section explaining how to install and login is somewhat verbose for what Claude already knows about CLI tools.	2 / 3
Actionability	The skill provides concrete, executable commands throughout (apify init, apify run with specific flags, apify push), a quick reference table with exact SDK calls per language, and specific file paths for configuration. The commands are copy-paste ready and the checklist items are specific and verifiable.	3 / 3
Workflow Clarity	The 8-step workflow is clearly sequenced with an explicit checklist for tracking progress. There's a pre-deployment validation checklist that serves as a comprehensive verification step, and the instruction to always use 'apify run' (not npm start/python) acts as a guardrail. Schema validation against @apify/json_schemas provides explicit validation checkpoints.	3 / 3
Progressive Disclosure	Excellent progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to language-specific guides (js-ts-actorization.md, python-actorization.md, cli-actorization.md) and schema configuration (schemas-and-output.md). The quick reference table provides just enough inline detail while deferring comprehensive guidance to reference files.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 1a9f5ac

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