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.
53
42%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/apify-actor-development/SKILL.mdQuality
Discovery
0%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 is an internal instruction telling the user/agent to fill in a metadata field. It completely fails to describe any capability, provide trigger terms, or indicate when the skill should be selected. It would be unusable in a skill selection context.
Suggestions
Rewrite the description to explain what the skill actually does (e.g., 'Configures Apify actor metadata by populating the .actor/actor.json file with tool and model information').
Add a 'Use when...' clause with explicit trigger terms such as 'Apify actor setup', 'actor.json configuration', 'generatedBy metadata', or 'Apify project initialization'.
Remove the instructional/imperative tone ('Before you begin...') and replace with a third-person declarative description of the skill's capabilities and purpose.
| 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 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/technical jargon that users would never 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 |
Implementation
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, comprehensive skill for Apify Actor development. Its greatest strengths are the clear workflow sequencing, excellent progressive disclosure with well-organized references, and highly actionable CLI commands and file paths. The main weakness is moderate verbosity—the 'What are Apify Actors?' conceptual section and some of the security/best practices content could be trimmed since Claude likely knows these general concepts.
Suggestions
Remove or significantly condense the 'What are Apify Actors?' section—Claude doesn't need a conceptual explanation of serverless programs, Docker containers, or the UNIX philosophy.
Trim the Security section to focus on Apify-specific concerns (e.g., APIFY_TOKEN handling, crawled data sanitization) rather than general security advice like 'review dependencies before installing' which Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity. The 'What are Apify Actors?' section explains concepts Claude likely already knows. Some sections like the Security best practices are thorough but could be more concise. However, most content is relevant and not excessively padded. | 2 / 3 |
Actionability | The skill provides concrete, executable commands throughout (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 CLI commands. The Quick Start Workflow gives copy-paste ready steps. | 3 / 3 |
Workflow Clarity | The Quick Start Workflow provides a clear 8-step sequence from project creation through deployment. Prerequisites are explicitly marked as MANDATORY with verification steps (apify info, apify --help). The local testing section includes important validation notes about local vs. cloud storage. Authentication has a clear decision tree with fallback options. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure pattern. The main skill provides a concise overview with clear one-level-deep references to detailed documentation: references/actor-json.md, references/input-schema.md, references/output-schema.md, references/dataset-schema.md, references/logging.md, references/standby-mode.md. Each reference is clearly signaled with descriptive text. | 3 / 3 |
Total | 11 / 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.
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
1a9f5ac
- 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.