dingtalk-pingo 0.1.0 → 0.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dingtalk-pingo",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Send text and Markdown messages from your terminal, scripts, or AI coding agents to your phone through a DingTalk robot.",
   "keywords": [
     "dingtalk",

package/skills/pingo/SKILL.md

@@ -45,8 +45,8 @@ pingo send --message "x" --json                       # machine-readable result
 ## Three usage patterns
 
 1. **Send now.** The user asks for an immediate message (e.g. a
-   screenshot description or a quick status). Send it right away and
-   report the result.
+   screenshot or a quick status). Send it right away and report the
+   result.
 2. **Send once when the current task finishes.** The user asks to be
    notified "when done". This is a one-time promise scoped to the
    current session, not a persistent background job: if you exit or your
@@ -65,16 +65,48 @@ pingo send --message "x" --json                       # machine-readable result
 - Never put secrets, access tokens, card numbers, or long raw logs in a
   message body.
 
-## Screenshots and images
+## Screenshots, images and videos
 
-The `pingo` CLI does not currently support sending images — sending an
-image is not supported yet. If the user asks to send a screenshot:
+`pingo` can attach local images and one mp4 video to a message:
 
-1. You may capture the screenshot with whatever tooling you already have
-   and inspect or describe its contents.
-2. Send a text/Markdown description instead of the image.
-3. Clearly tell the user that the image itself was **not sent** — image
-   support is not implemented yet. Do not imply the picture went through.
+```bash
+pingo send --title "Checkout page" --message "Current layout after the fix" --image ./shot.png
+pingo send --message "Repro recording" --video ./repro.mp4 [--cover ./frame.jpg]
+```
+
+- `--image` accepts png / jpg / gif / bmp, up to 5 images, each up to 10 MiB.
+  The file content must match its extension.
+- `--video` accepts one `.mp4` up to 19 MiB. It is sent as a separate video
+  message right after the main message. Without `--cover`, Pingo grabs a frame
+  with `ffmpeg` if it is installed, otherwise it generates a plain cover.
+- `--image` and `--video` do not replace the text: always pass `--message` or
+  `--markdown` with a short explanation.
+
+To send a screenshot: capture it with whatever tooling you already have, save
+it to a file, then pass the file with `--image`.
+
+**Before sending any screenshot or recording, check it for sensitive
+content** — secrets, access tokens, passwords, customer data, private
+messages, or anything else visible on screen that should not leave the
+machine. A screenshot can capture far more than intended. If you are not
+sure it is safe, ask the user first instead of sending it.
+
+## Links and cards
+
+- Add buttons with `--link "Text=https://..."` (up to 3, http(s) only), for
+  example a PR, a CI log or a deployment URL.
+- If the user's config has a card template (`card.templateId`), messages are
+  sent as cards automatically: the sender (machine, agent, project) is shown at
+  the top. You do not need to choose a format; if the card is rejected, Pingo
+  falls back to Markdown on its own and says so in its output.
+- Card-only extras: `--date "<text>"` sets the card's time line, and
+  `--chart <file.json>` adds a chart (`type` is `lineChart`, `histogram` or
+  `pieChart`; `data` is a non-empty array). Both only work with cards, not
+  Markdown/text.
+- For tabular data, put a Markdown table in `--message` or `--markdown`
+  (`| a | b |` rows with a `| :- | -: |` separator row).
+- `pingo send --json` returns a `cardId` for card messages. One-off sends do not
+  need it; `pingo-follow` uses it to update a card in place.
 
 ## Handling failures
 
@@ -84,6 +116,9 @@ image is not supported yet. If the user asks to send a screenshot:
 - Exit code `6` means the result is unknown — the message **may have
   already been sent**. Do not retry; tell the user to check their phone
   instead.
+- A send with images or a video can be partly delivered: the output (and
+  `--json` `sent` / `failed`) lists what went out and what did not. Do not
+  resend the parts that were already sent; tell the user what is missing.
 - If sending keeps failing, suggest the user run `pingo doctor` to check
   configuration, permissions, and whether a token can be obtained.
 

package/skills/pingo-follow/SKILL.md

@@ -81,6 +81,25 @@ Before sending, ask:
 - Do not let a general "avoid repeat notifications" habit suppress a
   genuinely new request for human approval — those always go through.
 
+## One card per followed task
+
+When the user's Pingo config sends cards, keep a followed task to a single
+card where it makes sense:
+
+1. The first time something is worth notifying, send it with
+   `pingo send --json ...` and keep the returned `cardId` in this
+   conversation (never write it to a file).
+2. For later progress milestones of the same task, update that card in place
+   instead of sending another message:
+   `pingo update <cardId> --type info --title "Tests passing" --message "..."`.
+   `--message` / `--markdown` replace the whole body, so pass the full text.
+3. **Always send a new message** (not an update) when the user's approval or
+   decision is needed (`--action-required`) and for the final completion
+   report — these must reach the user's phone as a fresh notification.
+4. If `pingo send --json` returned no `cardId` (the message fell back to
+   Markdown or text), keep sending new messages as usual.
+5. If `pingo update` fails, report it; do not silently send a duplicate.
+
 ## Turning it off and session boundaries
 
 - Turning follow off stops proactive notifications for the current