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.

Quality

42%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/apify-actor-development/SKILL.md

Quality

Content

85%

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, highly actionable skill for Apify Actor development. Its main strength is the clear workflow with concrete commands, good progressive disclosure to reference files, and thorough security guidance. The primary weakness is some verbosity—the 'What are Apify Actors?' conceptual section and parts of the security section explain things Claude already knows, consuming tokens without adding operational value.

Suggestions

Remove or significantly trim the 'What are Apify Actors?' section—Claude already understands serverless programs, Docker containers, and JSON I/O. A single sentence like 'Actors are serverless Docker containers that accept JSON input and produce structured output to datasets/key-value stores' would suffice.

Condense the Security section by removing explanatory rationale (e.g., 'Typosquatting is a common supply-chain attack vector') and keeping only the actionable directives.

Dimension	Reasoning	Score
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 is thorough but verbose. However, most sections are reasonably efficient with good use of bullet points and code blocks.	2 / 3
Actionability	The skill provides concrete, executable CLI commands (apify create, apify run, apify push), specific file paths (storage/key_value_stores/default/INPUT.json), exact template flags (-t project_empty, -t ts_empty, -t python-empty), and clear installation commands. The guidance is copy-paste ready throughout.	3 / 3
Workflow Clarity	The Quick Start Workflow provides a clear 8-step sequence with explicit validation (step 7: test locally with apify run). The Prerequisites section has a clear authentication flow with fallback options. The local testing section includes important validation notes about local vs. cloud storage, preventing a common error. The setup flow includes verification steps (apify info, apify --help).	3 / 3
Progressive Disclosure	The skill is well-structured as an overview with clear one-level-deep references to specific topics: references/actor-json.md, references/input-schema.md, references/output-schema.md, references/dataset-schema.md, references/key-value-store-schema.md, references/logging.md, and references/standby-mode.md. Each reference is clearly signaled with a descriptive section header and link.	3 / 3
	Total	11 / 12 Passed

Description

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 directive about updating a metadata field in actor.json, rather than describing a skill's capabilities and when to use it. It fails on every dimension because it does not communicate what the skill does or when it should be selected.

Suggestions

Rewrite the description to clearly state what the skill does (e.g., 'Configures Apify actor metadata by populating the actor.json file with required properties').

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

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

Dimension	Reasoning	Score
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 a procedural instruction rather than a skill description, with no 'Use when...' clause or equivalent.	1 / 3
Trigger Term Quality	There are no natural user-facing trigger terms. Terms like 'generatedBy', 'actor.json', and 'meta section' are internal implementation details, not keywords a user would naturally use to invoke a skill.	1 / 3
Distinctiveness Conflict Risk	The description is not a proper skill description at all—it's a meta-instruction about filling in a JSON property. It provides no clear niche or distinct triggers that would help differentiate it from other skills.	1 / 3
	Total	4 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: be20b37

Reviewed: about 22 hours ago

Table of Contents

Discovery Implementation Validation

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.