@11agents/cli 0.1.24 → 0.1.25

package/mobile-runtime/skills/android-publish-tiktok/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Android TikTok Publisher"
+  short_description: "Publish TikTok videos through the Android device-pool CLI"
+  default_prompt: "Use $android-publish-tiktok to publish a TikTok video from a managed Android device."

package/mobile-runtime/skills/android-publish-x/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: android-publish-x
+description: Publish X text, link, and image posts through the bundled 11agents mobile Android runtime. Use `11agents mobile publish-x`; do not expose raw ADB, automate engagement, or bypass platform checks.
+---
+
+# Android X Publishing
+
+## Required Inputs
+
+- Approved post type: `text`, `link`, or `image`.
+- Body/link/media fields required by the post type.
+- Target device or range, account id/account prefix when records need it, and live approval or dry-run intent.
+- Logged-in authorized X account.
+
+If approval, account access, content fields, or device readiness is missing, ask the user before publishing.
+
+## Workflow
+
+```bash
+11agents mobile doctor --json
+11agents mobile list-devices --health --json
+```
+
+Examples:
+
+```bash
+11agents mobile publish-x --device D03 --post-type text --body "post body" --json --task-id TASK_123
+11agents mobile publish-x --device D03 --post-type link --body "post body" --link-url "https://example.com" --json --task-id TASK_123
+11agents mobile publish-x --device D03 --post-type image --body "post body" --image "/path/image.jpg" --json --task-id TASK_123
+```
+
+Do not automate replies, follows, likes, reposts, random browsing, or DM actions from this skill.
+
+## Output
+
+Return publish status, record id, account/device, screenshot path, permalink or platform post id when available, duration, error or human action, and the data-collection handoff:
+
+```bash
+11agents mobile data collect --platform x --record-id <record_id> --json --task-id TASK_123
+```

package/mobile-runtime/skills/android-publish-x/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Android X Publisher"
+  short_description: "Publish X posts through Android devices"
+  default_prompt: "Use $android-publish-x to publish X content from a managed Android device."

package/mobile-runtime/skills/android-publish-xiaohongshu/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: android-publish-xiaohongshu
+description: Publish Xiaohongshu image and video notes through the bundled 11agents mobile Android runtime. Use `11agents mobile publish-xiaohongshu` and `11agents mobile copy-xiaohongshu-link`; do not expose raw ADB or bypass platform checks.
+---
+
+# Android Xiaohongshu Publishing
+
+## Required Inputs
+
+- Approved image/video note or structured publish package.
+- Title, caption/body, tags/topics when available, media paths, target device or range, account id/account prefix, and live approval or dry-run intent.
+- Logged-in authorized Xiaohongshu account and account lifecycle approval.
+
+If approval, account lifecycle, media/package path, text fields, or device readiness is missing, ask the user before publishing.
+
+## Workflow
+
+```bash
+11agents mobile doctor --json
+11agents mobile list-devices --health --json
+```
+
+Image/video note:
+
+```bash
+11agents mobile publish-xiaohongshu --device D03 --post-type image --image "/path/image.jpg" --title "title" --caption "body" --json --task-id TASK_123
+11agents mobile publish-xiaohongshu --device D03 --post-type video --video "/path/video.mp4" --title "title" --caption "body" --json --task-id TASK_123
+```
+
+Structured package:
+
+```bash
+11agents mobile publish-xiaohongshu --device D03 --publish-package "/path/publish_package.json" --json --task-id TASK_123
+```
+
+Link copy after publish, when requested:
+
+```bash
+11agents mobile copy-xiaohongshu-link --device D03 --record-id <record_id> --json --task-id TASK_123
+```
+
+Use `--confirm-no-disclosure-needed` only when the approved package/policy explicitly allows it. Stop on login, restriction, verification, disclosure ambiguity, or unexpected UI state.
+
+## Output
+
+Return publish status, record id, account/device, screenshot path, note link or platform post id when available, duration, error or human action, and the data-collection handoff:
+
+```bash
+11agents mobile data collect --platform xiaohongshu --record-id <record_id> --copy-link --json --task-id TASK_123
+```

package/mobile-runtime/skills/android-publish-xiaohongshu/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Android Xiaohongshu Publisher"
+  short_description: "Publish Xiaohongshu notes through the Android device-pool CLI"
+  default_prompt: "Use $android-publish-xiaohongshu to publish Xiaohongshu content from a managed Android device."

package/mobile-runtime/skills/mobile-publish-data-collection/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: mobile-publish-data-collection
+description: Use when a mobile publish agent needs to recover post-publish data from Android publish records and feed review learning back to channel agents
+---
+
+# Mobile Publish Data Recovery
+
+## Required Inputs
+- Installed `@11agents/cli` with `11agents mobile setup` completed.
+- Optional `ELEVENAGENTS_MOBILE_HOME` and platform API tokens or export paths provided by the user.
+- Record ids, platform post ids, permalinks, account ids, and target metric windows.
+
+If records, platform post id/permalink, or analytics access is missing, ask the user before claiming metrics are available. When paths are absent, default to `~/.11agents/mobile/data/publish_records.jsonl` and `~/.11agents/mobile/data/video_metrics.jsonl`.
+
+## Process
+1. Verify the runtime and publish records:
+
+```bash
+11agents mobile doctor --json
+11agents mobile list-publish-records --json --task-id TASK_ID
+```
+
+2. Read bundled command guidance when exact metrics commands or record update syntax are needed:
+
+```bash
+11agents mobile skills show android-group-control-cli
+```
+
+3. Prefer platform API or existing local collector commands over screenshots for metrics.
+4. Run high-level metrics commands only:
+
+```bash
+11agents mobile data collect --platform reddit --record-id <record_id> --json --task-id TASK_ID
+11agents mobile data collect --platform instagram --record-id <record_id> --json --task-id TASK_ID
+11agents mobile data collect --platform tiktok --scope account --device Dxx --json --task-id TASK_ID
+11agents mobile data collect --platform tiktok --scope video --device Dxx --record-id <record_id> --json --task-id TASK_ID
+11agents mobile data collect --platform xiaohongshu --record-id <record_id> --copy-link --json --task-id TASK_ID
+11agents mobile data collect --platform x --record-id <record_id> --json --task-id TASK_ID
+11agents mobile data collect --platform facebook --record-id <record_id> --json --task-id TASK_ID
+11agents mobile list-metrics --json --task-id TASK_ID
+```
+
+5. Treat X, Facebook, and unsupported platform collectors that return `missing_access` as a valid recovery status. Ask for the relevant API token, analytics export, or manual values, then append with `11agents mobile add-metrics`.
+6. If platform metrics are unavailable, record the missing access and ask for the relevant token/export instead of inventing numbers.
+7. Summarize metrics by platform, account, device, content type, creative pattern, and issue/task id.
+8. Write reusable learning as `agent_memory_delta` for channel agents.
+
+## Output
+Return recovered links/metrics, missing analytics access, record ids covered, data freshness, run log path, notable performance patterns, and follow-up tasks for planning.

package/mobile-runtime/skills/mobile-publish-device-health/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: mobile-publish-device-health
+description: Use when a mobile publish agent needs to inspect Android device pool health, account state, or human handoff needs
+---
+
+# Mobile Publish Device Health
+
+## Required Inputs
+- Installed `@11agents/cli` with `11agents mobile setup` completed.
+- Optional `ELEVENAGENTS_MOBILE_HOME`. Account/device registries live under `~/.11agents/mobile/data` by default.
+- Target device id, range, platform, app package expectations, and health-check intent. Account id is optional unless the user asks to validate a specific account.
+
+If mobile setup, device data, or target device information is missing, ask the user before reporting device readiness. Missing `accounts.csv` must not make an ADB-online device unavailable; report it only as missing account registry metadata.
+
+## Process
+1. Verify the bundled runtime.
+2. Verify ADB and device registry with high-level commands:
+
+```bash
+11agents mobile doctor --json
+11agents mobile list-adb
+11agents mobile list-devices --health --json
+```
+
+3. Select target devices only from current health output where the managed device is active and online.
+4. If account inventory was requested and `~/.11agents/mobile/data/accounts.csv` exists, check account binding through documented local commands or records. If devices are already logged in and no account registry was requested, verify app/login readiness from device state instead of requiring account metadata.
+5. Capture screenshots through high-level CLI when a device/account needs human attention:
+
+```bash
+11agents mobile screenshot Dxx --task-id TASK_ID
+```
+
+6. Use controlled Appium and ADB-state helpers when a device needs deeper inspection:
+
+```bash
+11agents mobile ensure-appium --device Dxx --json --task-id TASK_ID
+11agents mobile dump-ui Dxx --task-id TASK_ID
+11agents mobile launch Dxx <android.package.name> --task-id TASK_ID
+```
+
+7. `tap`, `keyevent`, and `input-text` are allowed only through `11agents mobile` for explicit diagnostics, documented recovery steps, or human handoff assistance. Do not run raw `adb shell`.
+8. Do not return `needs_human` only for camera, microphone, gallery/media, or notification permission prompts when the publish CLI can auto-grant or tap allow for publish-required permissions.
+9. Return `needs_human` for login prompts, captcha, account restrictions, verification challenges, or unexpected app states that are not permission prompts.
+10. Do not retry blindly after a restricted or unknown state; preserve screenshot evidence and stop.
+
+## Output
+Return device availability, online status, app readiness, optional account-registry notes, screenshot paths, run log path, blocked devices/accounts, and the exact human action needed. Keep ADB/device availability separate from account metadata availability.

package/mobile-runtime/skills/mobile-publish-execution/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: mobile-publish-execution
+description: Use when a mobile publish agent needs to prepare or dry-run `11agents mobile` publishing commands
+---
+
+# Mobile Publish Execution
+
+## Required Inputs
+- Approved execution plan or dry-run request.
+- Installed `@11agents/cli` and completed `11agents mobile setup`.
+- Optional placeholders: `ELEVENAGENTS_MOBILE_HOME`, `ELEVENAGENTS_MOBILE_DEFAULT_DEVICE`, `ELEVENAGENTS_MOBILE_DEFAULT_RANGE`, and `ELEVENAGENTS_MOBILE_DEFAULT_MAX_CONCURRENCY`.
+- Media files, captions/titles/body/link fields, target device or range, optional account id/account prefix, and dry-run/live mode.
+
+If mobile setup, device online status, media path, app login readiness, or approval status is missing, ask the user before running commands. Missing account CSV alone is not a blocker when the target app is already logged in on the device.
+
+## Process
+1. Verify the bundled runtime:
+
+```bash
+11agents mobile doctor --json
+```
+
+2. Read bundled command guidance when exact syntax is needed:
+
+```bash
+11agents mobile skills show android-group-control-cli
+```
+
+3. Verify prerequisites with controlled CLI commands:
+
+```bash
+11agents mobile list-adb
+11agents mobile list-devices --health --json
+```
+
+4. Use controlled ADB/Appium utility commands when needed for diagnosis, screenshots, UI state capture, app launch, or human handoff support:
+
+```bash
+11agents mobile ensure-appium --device Dxx --json
+11agents mobile screenshot Dxx
+11agents mobile dump-ui Dxx
+11agents mobile launch Dxx <android.package.name>
+```
+
+5. Use `tap`, `keyevent`, and `input-text` only as explicit, traceable `11agents mobile` steps for diagnostics or a documented recovery path; do not expose raw `adb shell` or arbitrary Appium scripts.
+6. Validate every local media path before a publish command. The path must be reachable from the runtime machine that controls the Android devices.
+7. Validate the selected platform command supports the requested post type and text fields.
+8. If no explicit `--account-id` is provided, rely on the command's `--account-prefix` fallback account id for publish records when supported.
+9. Use `--dry-run` only for preview/test requests; do not add it to explicit live-publish requests.
+10. Do not stop solely for Android camera, microphone, gallery/media, notification, Reels public-sharing, or Xiaohongshu disclosure prompts when the CLI policy handles them for explicit live publish. Let the CLI return `needs_human` when it cannot safely continue.
+11. Use `11agents mobile publish-tiktok`, `publish-instagram`, `publish-facebook`, `publish-reddit`, `publish-x`, and `publish-xiaohongshu`.
+12. Prefer `--json` and parse status, duration, record id, screenshot path, permalink, platform post id, and error.
+13. Pass `--task-id <task_id>` so logs land at `~/.11agents/mobile/runs/<task_id>/log`.
+14. Stop on `needs_human` or `failed`; surface screenshot and error instead of repeated retries.
+
+## Output
+Return readiness status, dry-run result or execution preparation summary, device/app health notes, optional account-registry notes, command family selected, exact safe `11agents mobile` command shape, log path, and missing env placeholders.

package/mobile-runtime/skills/mobile-publish-records/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: mobile-publish-records
+description: Use when a mobile publish agent needs to inspect, update, or reconcile Android publish records
+---
+
+# Mobile Publish Records
+
+## Required Inputs
+- Installed `@11agents/cli` with `11agents mobile setup` completed.
+- Optional `ELEVENAGENTS_MOBILE_HOME`; records live under `~/.11agents/mobile/data/publish_records.jsonl` by default.
+- Publish result JSON, record id, platform, account id, device id, screenshot path, permalink/platform post id, and status update intent.
+
+If record path, record id, publish result, or update intent is missing, ask the user before modifying records. When no custom mobile home is configured, default to `~/.11agents/mobile/data/publish_records.jsonl`.
+
+## Process
+1. Verify the mobile runtime and resolve the records path.
+2. List current records before reconciling:
+
+```bash
+11agents mobile list-publish-records --json --task-id TASK_ID
+```
+
+3. Update records only through high-level local commands such as `11agents mobile update-publish-record`.
+4. Preserve screenshot paths, errors, `needs_human` reasons, duration, account/device, media path, platform post id, permalink, and command family.
+5. For Reddit permalink lookup, avoid marking app-level success as failed only because public lookup lacks a matching username.
+6. Hand successful records to Mobile Publish Data Recovery.
+
+## Output
+Return record ids touched, status changes, permalink/post id updates, screenshot evidence, unresolved human handoffs, run log path, and data-recovery next step.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@11agents/cli",
-  "version": "0.1.24",
+  "version": "0.1.25",
   "description": "11agents local runtime and telemetry CLI",
   "type": "module",
   "bin": {
@@ -11,11 +11,14 @@
     "bin/",
     "src/",
     "!src/**/*.test.js",
+    "mobile-runtime/",
+    "scripts/",
     "examples/",
     "specs/",
     "README.md"
   ],
   "scripts": {
+    "postinstall": "node scripts/mobile-postinstall.js",
     "test": "node --test src/*.test.js src/commands/*.test.js"
   },
   "engines": {

package/scripts/mobile-postinstall.js

@@ -0,0 +1,26 @@
+#!/usr/bin/env node
+import { spawnSync } from 'node:child_process'
+
+const requested = process.env.ELEVENAGENTS_INSTALL_MOBILE === '1'
+const required = process.env.ELEVENAGENTS_REQUIRE_MOBILE === '1'
+
+if (!requested && !required) {
+  process.stderr.write('11agents mobile runtime: run `11agents mobile setup` on Android publishing machines.\n')
+  process.exit(0)
+}
+
+const result = spawnSync(process.execPath, [
+  new URL('../bin/11agents.js', import.meta.url).pathname,
+  'mobile',
+  'setup',
+  '--json',
+  '--quiet',
+], {
+  stdio: 'inherit',
+  env: process.env,
+})
+
+if (result.status && required) process.exit(result.status)
+if (result.status) {
+  process.stderr.write('11agents mobile runtime setup failed; rerun `11agents mobile setup` after installing Python, npm, Android SDK, and ADB.\n')
+}