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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/apify-actorization/SKILL.md

The canonical home for this skill is apify-actorization in sickn33/antigravity-awesome-skills

Quality

Content

85%Scale 1-3

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 progressive disclosure and workflow clarity. The 8-step process is clearly sequenced with checklists, and language-specific details are properly delegated to reference files. Minor conciseness issues exist with the 'When to Use This Skill' section and monetization content that could be trimmed or moved to a reference file.

Suggestions

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

Move the 'Monetization (Optional)' section to a reference file since it's tangential to the core actorization workflow.

Dimension	Reasoning	Score
Conciseness	Generally efficient but includes some unnecessary content like the 'When to Use This Skill' section (Claude can infer this), the monetization section which is tangential, and some explanatory text that could be trimmed. The prerequisites section explaining how to log in is somewhat verbose.	2 / 3
Actionability	Provides concrete, executable commands throughout (apify init, apify run with specific flags, apify push). The quick reference table gives copy-paste ready SDK patterns, and test commands include realistic example input JSON.	3 / 3
Workflow Clarity	Clear 8-step sequential workflow with an explicit checklist for tracking progress. Includes a pre-deployment validation checklist that serves as a comprehensive verification step before the destructive 'push' operation. The 'Important' callout about using apify run instead of direct execution is a valuable guardrail.	3 / 3
Progressive Disclosure	Excellent structure with a concise overview and quick reference table in the main file, with language-specific details properly delegated to one-level-deep reference files (js-ts-actorization.md, python-actorization.md, cli-actorization.md, schemas-and-output.md). Navigation is clear and well-signaled.	3 / 3
	Total	11 / 12 Passed

Description

40%Scale 1-3

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 establishes a clear niche around Apify platform actorization, which makes it distinctive. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. The specificity of concrete actions could also be improved by listing more granular tasks the skill performs.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to deploy code to Apify, create an Actor, convert a script into a serverless application, or mentions the Apify platform.'

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

List more specific concrete actions, e.g., 'Scaffolds Actor project structure, generates Dockerfile, defines input/output schemas, configures Apify storage, and packages code for deployment.'

Dimension	Reasoning	Score
Specificity	The description names the domain (Apify platform, serverless applications) and describes the general action (converts existing software into reusable serverless applications), but doesn't list multiple specific concrete actions like scaffolding Dockerfiles, defining input schemas, configuring storage, etc.	2 / 3
Completeness	The description answers 'what does this do' reasonably well 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', 'Actor', 'serverless', 'Docker', and 'JSON input/output', but misses common user variations like 'deploy to Apify', 'create an actor', 'Apify SDK', 'web scraper', 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' as Docker-packaged serverless programs, making it very unlikely to conflict with other skills. The niche is clearly 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/apify-actorization/SKILL.md
Commit: 0159794

Reviewed: about 8 hours 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.