CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apify-actorization

Convert existing projects into Apify Actors - serverless cloud programs. Actorize JavaScript/TypeScript (SDK with Actor.init/exit), Python (async context manager), or any language (CLI wrapper). Use when migrating code to Apify, wrapping CLI tools as Actors, or adding Actor SDK to existing projects.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A well-structured, highly actionable body: the 9-step workflow carries explicit validation checkpoints and error recovery, and detailed per-language guidance is properly offloaded to real reference files. The main flaws are the verbatim repetition of the telemetry flag in every command block and a README-guidelines reference that points outside the bundle to a non-existent path.

Suggestions

State the '--user-agent apify-agent-skills/apify-actorization' requirement once in the telemetry section and show it in a single example command instead of repeating it in every code block.

Consolidate the 'Actorization checklist' and 'Pre-deployment checklist', which repeat overlapping items (schemas, validate-schema, apify run, README) into one tracked checklist.

Replace the dangling 'skills/apify-actor-development/references/actor-readme.md' reference with either the required README structure inlined briefly or a working relative path within this bundle.

DimensionReasoningScore

Conciseness

Mostly efficient with no explanation of concepts Claude already knows, but the '--user-agent apify-agent-skills/apify-actorization' flag is repeated verbatim in roughly ten code blocks (a single instruction plus one example would do), and the 'Actorization checklist' overlaps the 'Pre-deployment checklist'. Minor trimmable padding, matching anchor 4 rather than 5.

4 / 5

Actionability

Copy-paste-ready commands throughout: 'apify init <actor-name>', "apify run --input '{\"startUrl\": \"https://example.com\", \"maxItems\": 10}'", 'apify validate-schema', plus concrete Dockerfile base images ('apify/actor-python', 'apify/actor-node') and a quick-reference table of SDK lifecycle calls per language.

5 / 5

Workflow Clarity

A 9-step checklist maps to dedicated sections in order, with explicit validation checkpoints ('apify info # Should return your username', validate-schema, local 'apify run' test, pre-deployment checklist) and error-recovery guidance (headless APIFY_TOKEN fallback, passing the actor name to avoid hanging in non-interactive shells). This matches the anchor-5 example's validate-then-proceed pattern.

5 / 5

Progressive Disclosure

Language-specific detail is appropriately split into four real, one-level-deep reference files, each clearly signaled ('See [js-ts-actorization.md](references/js-ts-actorization.md)'). However, the body points to 'skills/apify-actor-development/references/actor-readme.md', a cross-skill path that does not resolve within this bundle, leaving one dangling navigation target.

4 / 5

Total

18

/

20

Passed

Description

88%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.

A strong description that clearly states what the skill does across all language paths and gives an explicit 'Use when' clause with three concrete triggers. Trigger synonyms are good but not exhaustive, and the SDK-integration trigger has minor overlap with a sibling Apify development skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with comprehensive coverage: 'Convert existing projects into Apify Actors', 'Actorize JavaScript/TypeScript (SDK with Actor.init/exit), Python (async context manager), or any language (CLI wrapper)' — every major conversion path is named with its specific mechanism.

5 / 5

Completeness

Explicitly answers both: what ('Convert existing projects into Apify Actors - serverless cloud programs' with per-language methods) and when ('Use when migrating code to Apify, wrapping CLI tools as Actors, or adding Actor SDK to existing projects'). Third person voice is used correctly.

5 / 5

Trigger Term Quality

'migrating code to Apify', 'wrapping CLI tools as Actors', and 'adding Actor SDK' are phrases users would naturally say, but common variations like 'deploy to Apify' or 'Apify platform' are missing. Good coverage without full synonym breadth.

4 / 5

Distinctiveness Conflict Risk

Clear Apify-specific niche with distinct migration/wrapping triggers, but 'adding Actor SDK to existing projects' slightly overlaps the sibling apify-actor-development skill's territory. Mostly distinct with minor overlap risk against that closely related skill.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

apify/agent-skills

Path

skills/apify-actorization/SKILL.md

Reviewed

Table of Contents

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.