Conciseness

The body is overwhelmingly imperative and dense — exact commands, do/don't lists, file paths — with no tutorial-style padding of concepts Claude already knows. Minor trimming is possible: the 'use apify run, not npm start' warning appears in both the Don't list and the Commands section, the local-storage-not-synced point is stated twice, and the 'What are Apify Actors?' intro is background explanation.

Actionability

Guidance is copy-paste ready throughout: exact scaffold commands per language ('apify create <actor-name> -t project_empty/ts_empty/python-empty'), dependency installs, authentication commands, the local INPUT.json path ('storage/key_value_stores/default/INPUT.json'), schema file locations, specific crawler classes with concurrency ranges ('HTTP (10-50), Browser (1-5)'), and even deprecated option names to avoid. All common workflow cases are covered.

Workflow Clarity

The Quick Start Workflow is a clearly sequenced 8-step path with an explicit validation checkpoint (step 7 'Test locally - Run apify run to verify functionality') before the deploy step, and the prerequisites section verifies CLI installation and login with remediation paths. It falls short of anchor 5 because no error-recovery loop is described (no 'if the local test fails, fix and re-run' guidance).

Progressive Disclosure

The body is a genuine overview: seven dedicated sections each signal one reference file (actor-json, input-schema, output-schema, dataset-schema, key-value-store-schema, logging, standby-mode), all seven files exist in references/, and the reference files contain no further nested links, so navigation is one level deep and easy to traverse.

Specificity

The description states concrete actions ('fill in the generatedBy property in the meta section of .actor/actor.json', 'Replace it with the tool and model you're currently using'), but these describe a one-off setup chore rather than the skill's capabilities — nothing about creating, testing, or deploying actors is stated. It is not entirely vague (anchor 1), but it names no domain capability, so it sits at 'actions are minimal or generic' relative to the skill's purpose.

Completeness

Both 'what does this skill do' and 'when should it be used' are entirely absent — the text is an instruction about filling in a metadata field. This matches anchor 1 ('missing both what and when') and is far below the anchor-3 cap that a missing 'Use when...' clause alone would impose.

Trigger Term Quality

The only keywords present are technical jargon ('generatedBy', '.actor/actor.json', 'AGENTS.md') plus one brand mention ('Apify') used in a monitoring context. No natural phrases a user would say when needing this skill (actor, scraper, crawler, deploy, Apify CLI) appear, matching the 'no natural keywords; only technical jargon' anchor.

Distinctiveness Conflict Risk

The text contains Apify-specific tokens so it is not fully generic (not anchor 1), but as a trigger description it points at config-editing/meta tasks rather than actor development, giving it high misfire risk. It neither describes the skill's niche nor provides triggers that would select it correctly.