@11agents/cli 0.1.36 → 0.1.37

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

@@ -36,6 +36,8 @@ Use `--range`, `--parallel`, and `--max-concurrency N` only when the approved pl
 
 Successful live publish is only confirmed after the CLI taps the publish button and verifies TikTok publish completion. After writing the publish record, the CLI force-stops TikTok and captures `after-app-close.png` in the run artifacts.
 
+When the agent environment contains `ELEVENAGENTS_PUBLISH_DINGTALK_WEBHOOK`, the CLI sends a DingTalk notification after status `published`; `ELEVENAGENTS_PUBLISH_DINGTALK_SECRET` is optional. TikTok notification content does not show a link.
+
 ## Output
 
 Return publish status, record id, account/device, screenshot path, permalink or platform post id when available, duration, error action, and the data-collection handoff:

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

@@ -35,6 +35,8 @@ Structured package:
 
 Successful live publish is only confirmed after the CLI taps the final publish button, waits without tapping while Xiaohongshu shows upload/progress state, closes and relaunches Xiaohongshu, then opens the "我" page, opens the note whose title matches the expected title or the first visible profile note as a verified fallback, and verifies the detail page against the expected title/body. The CLI recovers the note link by default for live publish; use `--no-copy-link-after-publish` only when link recovery is explicitly not wanted. After writing the publish record, the CLI force-stops Xiaohongshu and captures `after-app-close.png` in the run artifacts. If that evidence does not match, treat the result as `failed`; do not claim publish success from the publish button tap alone.
 
+When the agent environment contains `ELEVENAGENTS_PUBLISH_DINGTALK_WEBHOOK`, the CLI sends a DingTalk notification after status `published`; `ELEVENAGENTS_PUBLISH_DINGTALK_SECRET` is optional. The Xiaohongshu notification includes the recovered link when available and still sends if the link was not recovered.
+
 Link copy after publish or during the recovery skill:
 
 ```bash

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

@@ -8,7 +8,7 @@ description: Use when a mobile publish agent needs to prepare or dry-run `11agen
 ## 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`.
+- Optional placeholders: `ELEVENAGENTS_MOBILE_HOME`, `ELEVENAGENTS_MOBILE_DEFAULT_DEVICE`, `ELEVENAGENTS_MOBILE_DEFAULT_RANGE`, `ELEVENAGENTS_MOBILE_DEFAULT_MAX_CONCURRENCY`, `ELEVENAGENTS_PUBLISH_DINGTALK_WEBHOOK`, and `ELEVENAGENTS_PUBLISH_DINGTALK_SECRET`.
 - 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.
@@ -51,7 +51,8 @@ If mobile setup, device online status, media path, app login readiness, or appro
 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 `failed`; surface screenshot and error instead of repeated retries.
+14. Do not run custom DingTalk webhook scripts after Xiaohongshu or TikTok publish. When the agent environment contains `ELEVENAGENTS_PUBLISH_DINGTALK_WEBHOOK`, the CLI sends the publish-success notification automatically; `ELEVENAGENTS_PUBLISH_DINGTALK_SECRET` is optional for signed robots.
+15. Stop on `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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@11agents/cli",
-  "version": "0.1.36",
+  "version": "0.1.37",
   "description": "11agents local runtime and telemetry CLI",
   "type": "module",
   "bin": {

package/src/commands/mobile.js

@@ -99,8 +99,9 @@ Runtime:
   Python/device-control code is bundled with @11agents/cli.
   Mutable runtime state lives in ~/.11agents/mobile by default.
   Every command writes logs under ~/.11agents/mobile/runs/<task_id>/log.
-  Publish-success DingTalk notification is enabled by ELEVENAGENTS_PUBLISH_DINGTALK_WEBHOOK
-  and optional ELEVENAGENTS_PUBLISH_DINGTALK_SECRET.`)
+  Xiaohongshu/TikTok publish-success DingTalk notification is enabled by
+  ELEVENAGENTS_PUBLISH_DINGTALK_WEBHOOK and optional
+  ELEVENAGENTS_PUBLISH_DINGTALK_SECRET.`)
 }
 
 function mobileHome(flags = {}, env = process.env) {
@@ -597,11 +598,10 @@ async function notifyMobilePublishSuccess({ command, context, parsed, env = proc
   const config = dingTalkConfig(env)
   if (!config.webhook || !Array.isArray(parsed)) return
   const platform = platformFromMobileCommand(command)
-  if (!platform) return
+  if (!shouldNotifyPublishPlatform(platform)) return
   for (const row of parsed) {
     if (!isPublishedResult(row)) continue
     const link = publishResultLink(row)
-    if (!link) continue
     const content = buildPublishNotificationContent({
       platform,
       task: context.taskTitle || context.taskId,
@@ -623,8 +623,20 @@ async function notifyMobilePublishSuccess({ command, context, parsed, env = proc
 
 function dingTalkConfig(env = process.env) {
   return {
-    webhook: env.ELEVENAGENTS_PUBLISH_DINGTALK_WEBHOOK || env.ELEVENAGENTS_DINGTALK_WEBHOOK || '',
-    secret: env.ELEVENAGENTS_PUBLISH_DINGTALK_SECRET || env.ELEVENAGENTS_DINGTALK_SECRET || '',
+    webhook: env.ELEVENAGENTS_PUBLISH_DINGTALK_WEBHOOK
+      || env.ELEVENAGENTS_DINGTALK_WEBHOOK
+      || env.GTM_DINGTALK_WEBHOOK
+      || env.DINGTALK_WEBHOOK
+      || '',
+    secret: env.ELEVENAGENTS_PUBLISH_DINGTALK_SECRET
+      || env.ELEVENAGENTS_PUBLISH_DINGTALK_KEY
+      || env.ELEVENAGENTS_DINGTALK_SECRET
+      || env.ELEVENAGENTS_DINGTALK_KEY
+      || env.GTM_DINGTALK_SECRET
+      || env.GTM_DINGTALK_KEY
+      || env.DINGTALK_SECRET
+      || env.DINGTALK_KEY
+      || '',
   }
 }
 
@@ -644,6 +656,10 @@ function isPublishedResult(row) {
   return row && typeof row === 'object' && row.status === 'published'
 }
 
+function shouldNotifyPublishPlatform(platform) {
+  return platform === 'xiaohongshu' || platform === 'tiktok'
+}
+
 function publishResultLink(row) {
   return String(
     row.platform_permalink
@@ -658,7 +674,9 @@ function buildPublishNotificationContent({ platform, task, deviceId = '', link }
   const label = platformLabel(platform)
   const taskText = String(task || 'task').trim()
   const deviceText = deviceId ? `（设备 ${deviceId}）` : ''
-  return `${label} ${taskText}${deviceText}已发布，链接：${link}`
+  if (platform === 'tiktok') return `${label} ${taskText}${deviceText}已发布`
+  const linkText = String(link || '').trim() || '未回收'
+  return `${label} ${taskText}${deviceText}已发布，链接：${linkText}`
 }
 
 function platformLabel(platform) {
@@ -831,6 +849,7 @@ export const mobileInternals = {
   parseRawArgs,
   platformFromMobileCommand,
   publishResultLink,
+  shouldNotifyPublishPlatform,
   signedDingTalkUrl,
   stripWrapperFlags,
   taskIdFrom,