AC apify-actorization
Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output.
Actorization converts existing software into reusable serverless applications compatible with the Apify platform.
As a process C 60/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "date_added"
Process rating: all ten parameters 60/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 58 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1621 tokens
- 100Running it twice. Mutating operations check current state
- low 15 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 262: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 58 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.