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.
69
62%
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-actorization/SKILL.mdSecurity
2 findings — 2 medium severity. This skill can be installed but you should review these findings before use.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Third-party content exposure detected (high risk: 0.90). The skill's required workflow (e.g., SKILL.md and references/js-ts-actorization.md) explicitly instructs running crawlers with a user-provided startUrl (see "apify run --input '{\"startUrl\": ...}'") and examples using PlaywrightCrawler's requestHandler that reads page content (e.g., page.title()), which means the agent will fetch and interpret arbitrary public web pages/URLs as part of its normal operation.
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
Direct money access detected (high risk: 1.00). The skill explicitly documents monetization and a charge API: it instructs configuring Pay Per Event monetization and shows code to charge users with `await Actor.charge('result')`. That is a specific, built-in function to bill/charge for events (i.e., move money), not a generic automation or API caller. Therefore it grants direct financial execution capability.
1a9f5ac
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.