X Apify

Before installing or running this skill: - Expect to provide an APIFY_API_TOKEN (the SKILL.md and code require it). The registry summary shown to you currently omits this — confirm the platform metadata is updated or the skill will fail. - Review and confirm the default APIFY_ACTOR_ID and any per-run costs on Apify (actors cost credits; check the actor's pricing and your account limits). Running actors can incur charges. - Install 'requests' in the Python environment (pip install requests) or run in a contained environment (virtualenv/container). - Because the skill accepts an APIFY token, consider using a scoped or dedicated token and avoid putting secrets into VCS. The SKILL.md already warns about .env files; follow that guidance. - Verify the source repository / homepage (package.json points to a GitHub repo, but the registry summary lists none). Prefer skills with an accessible repository and issues tracker so you can inspect updates and provenance. - The code contains a changelog entry noting fixes for an arbitrary file write vulnerability in prior versions; ensure you are using the published patched version and consider reviewing the cache-related code if you have elevated security requirements. If these inconsistencies (missing declared env in registry, unknown source) worry you, treat the skill as untrusted until the publisher fixes the metadata or provides a verified upstream repository.