CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apify-actor-development

Create, modify, debug, and deploy Apify Actors, and write their input and output schemas. Use when building an Actor from scratch, changing or troubleshooting Actor code, generating or updating .actor schema files, or pushing an Actor to the Apify platform. To wrap an existing non-Actor project, use apify-actorization instead.

Quality

97%

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

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

Excellent content: dense and token-efficient, fully executable commands and code in both language ecosystems, a validated multi-step workflow with explicit completion criteria, and clean one-level progressive disclosure into real reference files. No dimension shows a meaningful weakness.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout: the opening defines only the Apify-specific Actor concept, the template table packs decision guidance into a few lines, and every justification (e.g., "It censors tokens and credentials; console.log and print do not") is a single clause earning its place. Nothing explains concepts Claude already knows.

5 / 5

Actionability

Guidance is copy-paste ready: full CLI commands with flags (apify create -t, apify push, apify call --input-file), a template-selection table, and complete code snippets for the aborting handler, proxy configuration, and event charging in both JS/TS and Python. The common cases are covered with specific, executable examples.

5 / 5

Workflow Clarity

The nine-step workflow is clearly sequenced with explicit validation checkpoints: nearly every step has a "Done when..." criterion, schema validation is delegated to `apify validate-schema` passing, local testing requires SUCCEEDED status and schema-matching output items, and deployment is gated on user confirmation. Build failures have a stated feedback path (get-actor-build-log).

5 / 5

Progressive Disclosure

The SKILL.md body is an overview with well-signaled, one-level-deep references (input-schema.md, output-schemas.md, actor-json.md, actor-readme.md, logging.md, standby-mode.md), all of which exist in references/. Content is appropriately split — details like full schema authoring and standby configuration live in the reference files, not inline.

5 / 5

Total

20

/

20

Passed

Description

92%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: concrete capabilities, an explicit trigger clause with natural phrasing, and clear boundary guidance against a sibling skill. The only weakness is slightly incomplete keyword coverage (crawl/scrape and deploy-related synonyms users might use for Actors).

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Create, modify, debug, and deploy Apify Actors, and write their input and output schemas" — giving comprehensive coverage of the skill's capabilities within its domain. It matches the anchor for multiple specific concrete actions rather than the level-4 anchor with coverage gaps.

5 / 5

Completeness

It clearly answers "what" (create, modify, debug, deploy Actors; write input and output schemas) and "when" via an explicit "Use when..." clause enumerating concrete triggers. This matches the anchor for explicitly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Phrases like "building an Actor from scratch", "changing or troubleshooting Actor code", "pushing an Actor to the Apify platform", and ".actor schema files" mirror what users would naturally say. A few natural synonyms are missing (e.g., crawl/scrape terminology for Actors, "deploy" as a user verb), keeping it just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The Apify Actor niche is distinct with specific triggers, and it even disambiguates the boundary case: "To wrap an existing non-Actor project, use apify-actorization instead." Minimal conflict risk with other skills.

5 / 5

Total

19

/

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-actor-development/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.