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

58%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/apify-actorization/SKILL.md

Quality

Content

77%

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 guide with strong actionability and clear workflow sequencing. The 8-step process with checklists and validation points makes it easy to follow. Main weaknesses are moderate verbosity (some sections like 'When to Use' and 'Limitations' add little value) and unverifiable progressive disclosure references since no bundle files were provided.

Suggestions

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

Move the 'Monetization', 'MCP Tools', and 'Resources' sections into a separate reference file to keep the main skill focused on the core actorization workflow.

Ensure the referenced files (references/js-ts-actorization.md, references/python-actorization.md, etc.) are included in the bundle to support the progressive disclosure structure.

Dimension	Reasoning	Score
Conciseness	The skill is generally well-structured but includes some unnecessary content like the 'When to Use This Skill' section (Claude can infer this), the 'Limitations' boilerplate at the end, and some explanatory text that could be trimmed. The prerequisites section explaining how to log in is somewhat verbose but arguably necessary for a multi-step workflow.	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, and specific file paths. The checklist format makes it immediately actionable, and the inline input examples are copy-paste ready.	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 main.py) is an important guardrail. Schema validation against @apify/json_schemas provides explicit validation checkpoints.	3 / 3
Progressive Disclosure	The skill references language-specific files (references/js-ts-actorization.md, references/python-actorization.md, references/cli-actorization.md, references/schemas-and-output.md) which is good progressive disclosure design, but no bundle files were provided, so we cannot verify these references exist. The main file itself is fairly long (~150 lines) with some content (monetization, MCP tools, resources) that could potentially be in separate reference files.	2 / 3
	Total	10 / 12 Passed

Description

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 actor conversion) and explains the concept of Actors well, giving it strong distinctiveness. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. The description reads more like a definition than actionable selection guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to convert existing code into an Apify Actor, deploy a scraper to Apify, or package software as a serverless application on the Apify platform.'

Include more natural trigger terms users might say, such as 'web scraper', 'crawler', 'Apify SDK', 'deploy to Apify', 'actor template', or 'convert to actor'.

List more specific concrete actions the skill performs, such as 'generates Dockerfile, creates input schema, configures actor.json, sets up Apify SDK integration'.

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 'scaffold Dockerfile', 'generate input schema', 'configure storage', etc.	2 / 3
Completeness	The description answers 'what does this do' (converts software into Apify-compatible actors) but completely lacks a 'Use when...' clause or any 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 some relevant keywords like 'Apify', 'Actors', 'serverless', 'Docker images', 'JSON input', but misses common user-facing terms like 'web scraper', 'crawler', 'Apify SDK', 'actor migration', or 'deploy to Apify'. 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 'actorization', making it very unlikely to conflict with other skills. The niche of converting software to Apify Actors is distinct and well-defined.	3 / 3
	Total	8 / 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: be20b37

Reviewed: 1 day 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.