CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/apify-actorization/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A well-structured, actionable skill body with a clear sequenced workflow, explicit validation checklists, and clean progressive disclosure into verified reference files. Main weaknesses are triplicated step lists (conciseness) and missing explicit error-recovery feedback loops.

Suggestions

Consolidate the Quick start, Actorization checklist, and Steps 1–9 sections to remove triplicated step listings and tighten token use.

Add an explicit error-recovery feedback loop in the test/deploy steps (e.g., 'if apify run fails, fix input/code and re-run before pushing').

Clearly mark cross-skill references (actor-readme.md, standby-mode.md) as external dependencies or move the needed guidance into this skill's own references.

DimensionReasoningScore

Conciseness

Mostly efficient and actionable, but the Quick start, Actorization checklist, and Steps 1–9 sections triplicate the same step sequence, adding redundancy that could be tightened; not a 2 because content is genuinely useful rather than padded with concepts Claude already knows.

3 / 5

Actionability

Concrete executable CLI commands throughout ('apify init', 'apify run --input', 'apify push', 'apify info', 'apify login') plus a quick-reference table with wrap snippets; full wrap code is one level deep in verified executable reference files, leaving minor gaps inline.

4 / 5

Workflow Clarity

Clear 9-step sequence with a pre-deployment checklist containing explicit validation (schema validation, Dockerfile build, 'apify run' success); not a 5 because no explicit error-recovery feedback loop ('if fails, fix and re-validate') is narrated.

4 / 5

Progressive Disclosure

Clear overview with four well-signaled, one-level-deep references (js-ts, python, cli, schemas-and-output) and content appropriately split; minor gap: cross-skill references (actor-readme.md, standby-mode.md) are not clearly signaled as external to this bundle.

4 / 5

Total

15

/

20

Passed

Description

87%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, specific description that clearly states both what the skill does and when to use it, with concrete technical detail per language and natural trigger phrases. Minor room to broaden trigger synonyms and add more distinct action verbs.

DimensionReasoningScore

Specificity

Lists several concrete actions with specific SDK patterns ('Actor.init/exit', 'async context manager', 'CLI wrapper') across JS/TS, Python, and any language; not a 5 because they are variants of one core 'actorize' action rather than multiple distinct actions.

4 / 5

Completeness

Explicitly answers WHAT ('Convert existing projects into Apify Actors... Actorize JS/TS, Python, or any language') and WHEN ('Use when migrating code to Apify, wrapping CLI tools as Actors, or adding Actor SDK') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ('migrating code to Apify', 'wrapping CLI tools as Actors', 'adding Actor SDK'); good coverage but missing some synonyms/variations a user might say.

4 / 5

Distinctiveness Conflict Risk

Clear Apify-specific niche with distinct triggers ('Apify Actors', 'Actor SDK', 'migrating code to Apify'); minimal conflict risk with other skills.

5 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
apify/agent-skills
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.