CtrlK
BlogDocsLog inGet started
Tessl Logo

apify-actor-development

Important: Before you begin, fill in the generatedBy property in the meta section of .actor/actor.json. Replace it with the tool and model you're currently using, such as "Claude Code with Claude Sonnet 4.5". This helps Apify monitor and improve AGENTS.md for specific AI tools and models.

41

Quality

41%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

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

The SKILL.md body is a well-structured, actionable overview: it provides concrete CLI commands and file paths, a numbered quick-start workflow with a test-before-deploy checkpoint, and cleanly delegates detailed schema/logging/standby docs to real one-level reference files. It is efficient with only minor conceptual padding and lacks an explicit deploy-time validation feedback loop.

DimensionReasoningScore

Conciseness

The body is largely efficient — terse command blocks ('apify run', 'apify push'), bullet-form Do/Don't lists, and pointed security notes — but contains minor padding such as the "What are Apify Actors?" conceptual explanation and repeated reiteration of the local-storage-not-synced caveat that could be trimmed.

4 / 5

Actionability

Most guidance is concrete and executable: exact CLI commands, template flags ('apify create <actor-name> -t ts_empty'), file paths ('storage/key_value_stores/default/INPUT.json'), and concrete concurrency ranges; minor gaps exist where schema configuration is delegated to references without an inline starter example.

4 / 5

Workflow Clarity

The Quick Start Workflow gives a clearly numbered 8-step sequence with a 'Test locally' checkpoint before 'Deploy', and the body repeatedly flags validation (input validation, sanitize crawled data, npm audit); it stops short of an explicit validate→fix→retry feedback loop for the deploy step, so it sits just below the top anchor.

4 / 5

Progressive Disclosure

The body is a clean overview that offloads detailed material to seven real, one-level-deep reference files (actor-json.md, input-schema.md, output-schema.md, dataset-schema.md, key-value-store-schema.md, logging.md, standby-mode.md), each linked with clear signaling, so navigation is easy and content is appropriately split.

5 / 5

Total

17

/

20

Passed

Description

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

The frontmatter description does not describe the skill at all — it is a one-time setup instruction to populate the generatedBy field, with no statement of capabilities or trigger conditions. This makes it ineffective for skill selection and matches the worst anchor for completeness and specificity.

Suggestions

Rewrite the description to state the skill's purpose and trigger, e.g. "Create, modify, and debug Apify Actor projects: choose templates, wire input/output schemas, implement runtime logic, and deploy with the apify CLI. Use when the user needs to build or troubleshoot an Apify Actor."

Move the generatedBy setup instruction out of the description field and into the Prerequisites & Setup section of the body, since it is a one-time administrative step rather than a capability statement.

Add natural trigger keywords such as 'Apify Actor', 'apify create', 'web scraping actor', and 'apify push' so the skill surfaces when users describe actor-development tasks.

DimensionReasoningScore

Specificity

The description states only "fill in the generatedBy property in the meta section of .actor/actor.json" and "Replace it with the tool and model you're currently using" — a single admin setup instruction, with no concrete actions describing the skill's actual capabilities (creating, modifying, debugging actors).

1 / 5

Completeness

Neither 'what does this skill do' nor 'when should Claude use it' is present; the text is solely a pre-begin setup directive, so it fails the minimal completeness bar and the missing 'Use when...' clause caps it at this level.

1 / 5

Trigger Term Quality

There are no natural user trigger terms (e.g. 'Apify Actor', 'scraping', 'create actor'); the only nouns are 'generatedBy property', 'meta section', and 'AGENTS.md', which are technical jargon a user would never say when they need this skill.

1 / 5

Distinctiveness Conflict Risk

It mentions '.actor/actor.json', 'generatedBy', and 'AGENTS.md', which are Apify-specific markers giving it a narrow niche, but because it conveys no capability or trigger, it would not be selected for actor-development tasks — broad overlap risk with any project-setup skill, just below the midpoint.

2 / 5

Total

5

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/agentic-awesome-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.