[patrikbraborec]

Found during Devin plugin testing, verified against apify-cli source.

• Every apify init call now passes the Actor name as an argument (Quick start, checklist, Step 2). Without a name, apify init asks for one and hangs in agent sandboxes that have no terminal. In CLI 1.10.x, --yes doesn't skip that prompt (fix pending in fix(init): stop the name prompt looping when stdin is not a TTY apify-cli#1479), so the skill relies on the name argument alone.
• Removed the claim that apify init creates a Dockerfile. Without a Dockerfile, the platform builds on its default Node.js image, so a Python Actor builds cleanly and then fails at runtime. Creating a Dockerfile for the project's language is now an explicit step (Quick start, checklist, Step 2). The checklist item "Dockerfile is present and builds successfully" is unchanged.
• Dropped the list of files apify init creates. It had gone stale, which is how the Dockerfile claim got in, and the agent can see the files after running the command. Step 2 now notes only what isn't obvious: there's no Dockerfile.
• No other skill calls apify init (apify-actor-development uses apify create). Regenerated agents/AGENTS.md; no changes.