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.

42

Quality

42%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/apify-actor-development/SKILL.md

The canonical home for this skill is apify-actor-development in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

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 skill with excellent progressive disclosure and actionability. The workflow is clearly sequenced with validation checkpoints, and references to detailed documentation are well-organized. The main weakness is some verbosity, particularly the 'What are Apify Actors?' conceptual section and the extensive security guidance, which could be trimmed since Claude already understands these concepts.

Suggestions

Remove or significantly condense the 'What are Apify Actors?' section — Claude already understands serverless programs, Docker containers, and JSON I/O. A single sentence would suffice.

Consolidate the security section into a concise checklist rather than detailed explanations of why each practice matters (e.g., explaining what typosquatting is).

DimensionReasoningScore

Conciseness

The skill contains some unnecessary explanations (e.g., 'What are Apify Actors?' section explains concepts Claude already knows like Docker containers and serverless programs). The security section, while important, is quite verbose. However, much of the content is practical and actionable, preventing a score of 1.

2 / 3

Actionability

The skill provides concrete, executable CLI commands throughout (apify create, apify run, apify push, npm install, etc.), specific file paths for configuration, and clear template selection commands for each language. The local testing section gives exact file paths for INPUT.json.

3 / 3

Workflow Clarity

The Quick Start Workflow provides a clear 8-step sequence from project creation through deployment. The prerequisites section has explicit validation checkpoints (verify CLI installed, check login status, authenticate). The local testing section includes important caveats about local vs. cloud storage that prevent common errors.

3 / 3

Progressive Disclosure

Excellent progressive disclosure with the main SKILL.md serving as an overview and clearly signaled one-level-deep references to separate files for actor-json.md, input-schema.md, output-schema.md, dataset-schema.md, key-value-store-schema.md, logging.md, and standby-mode.md. Navigation is clear and well-organized.

3 / 3

Total

11

/

12

Passed

Description

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

This is not a functional skill description. It reads as an internal instruction or preamble telling the agent to update a metadata field, rather than describing what the skill does or when it should be selected. It fails on every dimension of the rubric.

Suggestions

Rewrite the description to clearly state what the skill does (e.g., 'Configures Apify actor metadata by populating the .actor/actor.json file with tool and model information').

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when setting up an Apify actor, configuring actor.json, or initializing actor metadata').

Remove the instructional/imperative tone ('Important: Before you begin...') and replace with a third-person declarative description of capabilities.

DimensionReasoningScore

Specificity

The description does not describe any concrete actions or capabilities of a skill. It is an instruction about filling in a metadata property, not a description of what the skill does.

1 / 3

Completeness

The description fails to answer both 'what does this do' and 'when should Claude use it'. It reads as an internal instruction rather than a skill description, with no 'Use when...' clause or equivalent.

1 / 3

Trigger Term Quality

There are no natural user-facing keywords or trigger terms. Terms like 'generatedBy', 'actor.json', and 'meta section' are internal implementation details, not things a user would naturally say when seeking help.

1 / 3

Distinctiveness Conflict Risk

The description is not a proper skill description at all—it's a procedural instruction. It provides no clear niche or distinct triggers that would help differentiate it from other skills.

1 / 3

Total

4

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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