apify-cli 1.10.1-runtime.2 → 1.10.1-runtime.4

package/dist/actor.js

@@ -1,3 +1,3 @@
 #!/usr/bin/env node
-import{i as e,r as t,t as n}from"./_register-BR_AsLVT.js";t(`Actor`);for(let e of n)e.registerCommand(`actor`);await e(`actor`);export{};
+import{i as e,r as t,t as n}from"./_register-bessLnS2.js";t(`Actor`);for(let e of n)e.registerCommand(`actor`);await e(`actor`);export{};
 //# sourceMappingURL=actor.js.map

package/dist/apify.js

@@ -1,3 +1,3 @@
 #!/usr/bin/env node
-import{i as e,n as t,r as n}from"./_register-BR_AsLVT.js";n(`Apify`);for(let e of t)e.registerCommand(`apify`);await e(`apify`);export{};
+import{i as e,n as t,r as n}from"./_register-bessLnS2.js";n(`Apify`);for(let e of t)e.registerCommand(`apify`);await e(`apify`);export{};
 //# sourceMappingURL=apify.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "apify-cli",
-  "version": "1.10.1-runtime.2",
+  "version": "1.10.1-runtime.4",
   "description": "Apify command-line interface (CLI) helps you manage the Apify cloud platform and develop, build, and deploy Apify Actors.",
   "exports": "./dist/index.js",
   "type": "module",

package/skills/apify/SKILL.md

@@ -91,6 +91,8 @@ apify key-value-stores keys <storeId> --json
 
 `apify runtime` runs a self-contained local Apify platform as a container on Docker or Podman. Use it to develop and test Actors against a platform-compatible API without touching the user's cloud account. It ships on the `runtime` npm dist-tag, not on `latest`.
 
+This section covers only how to *get* a runtime. Once you have one, **run `apify runtime skill --install`** (or `apify runtime skill` to read it now) — the runtime ships its own Agent Skill on how to use it. That skill lives in the runtime image, so it always matches the runtime you actually have; read it rather than reconstructing it from memory.
+
 **Prerequisite: Docker or Podman.** One of them must be installed and running before any `apify runtime` command works; the CLI does not install either. It uses the first engine found on PATH (Docker before Podman); `APIFY_CONTAINER_ENGINE=podman` forces Podman.
 
 With Podman, the API socket must be served: check with `podman info --format '{{.Host.RemoteSocket.Exists}}'` (must print `true`). If it does not, run `systemctl --user enable --now podman.socket` (rootless) or `sudo systemctl enable --now podman.socket` (rootful); without systemd, `podman system service --time=0 &`. On macOS/Windows, `podman machine start` first. Rootful and rootless Podman both work.
@@ -139,6 +141,7 @@ export APIFY_DISABLE_KEYRING=1
 
 $APIFY runtime install
 $APIFY runtime start --detach --data-dir ./runtime-data   # omit --detach to run in the foreground (Ctrl+C stops it)
+$APIFY runtime skill --install                            # install the runtime's own skill, then follow it
 $APIFY login --token local-dev-token                      # the runtime accepts any token
 $APIFY actors ls --json                                   # now talks to the local runtime
 $APIFY runtime stop