--- name: lark-push description: Use when the user asks to send Feishu or Lark push notifications, code completion notices, daily reports, weekly reports, release summaries, or progress updates to a configured group chat. metadata: author: kedoupi version: "1.5.0" requires: bins: ["lark-cli"] --- # Lark Push Send concise Feishu / Lark messages through `lark-cli`. Default output is a Card 2.0 interactive card; use `--format markdown` for plain formatted text. ## Prerequisites (agents: check these first) If anything is missing, **tell the user how to install it** — do not assume Node or `lark-cli` exist. Run the built-in checklist: ```bash bash /scripts/lark-push doctor ``` | Need | Why | If missing | | --- | --- | --- | | **Node.js + npm** | `npx skills add …`; typical way to install `lark-cli` | Install LTS from https://nodejs.org/ or `brew install node` | | **lark-cli** | Actually send messages to Feishu/Lark | `npm install -g @larksuite/cli` then `lark-cli config init` / `auth status` | | **python3** | Default Card 2.0 (`--format card`) | `brew install python3`, or use `--format markdown` | | **Skill config** | Target chat id | `bash /scripts/lark-push init --chat-id oc_xxx` | Suggested order for a new machine: ```bash # 1) Node (if needed) # https://nodejs.org/ or brew install node # 2) Install this skill npx skills add kedoupi/lark-push-skill -g --all # 3) Feishu CLI npm install -g @larksuite/cli lark-cli config init --help LARKSUITE_CLI_NO_UPDATE_NOTIFIER=1 LARKSUITE_CLI_NO_SKILLS_NOTIFIER=1 \ lark-cli auth status --json --verify # 4) Skill chat config bash /scripts/lark-push init --chat-id oc_xxxxxxxx # 5) Verify bash /scripts/lark-push doctor ``` On macOS, if `lark-cli` reports **keychain access blocked** inside an Agent, run once in **Terminal.app**: ```bash lark-cli config keychain-downgrade ``` ## Locating the helper The skill may be installed via symlink or copy. Resolve the real path: ```bash # Common locations: # Canonical / symlink source: ~/.agents/skills/lark-push/ # Claude: ~/.claude/skills/lark-push/ # Codex: ~/.codex/skills/lark-push/ # Project: ./.agents/skills/lark-push/ ``` The script uses `pwd -P` internally, so symlinks resolve to the real directory and share one durable config. ## Onboarding (install ≠ configure) **Do not** demand `chat-id` merely because the skill was installed. Ask when the user wants a **real send** (or environment check) and config is missing. | When | Agent action | | --- | --- | | User only asks how to install / preview | `doctor` / `--dry-run`; no secrets required for dry-run | | User wants to **send** and chat id missing | Paste `init` block; wait for `oc_…` or approval to run init | | User runs `doctor` | Checklist ends with copy-paste setup if config missing | ```bash # After: npx skills add kedoupi/lark-push-skill -g --all bash ~/.agents/skills/lark-push/scripts/lark-push doctor # Configure target chat (recommended path): bash ~/.agents/skills/lark-push/scripts/lark-push init --chat-id 'oc_YOUR_CHAT_ID' # → ~/.config/kedoupi/lark-push/config.env ``` Never put chat config only inside the skill package; never edit the user’s shell rc for this. ## Config One-time after install (or when first sending): ```bash bash /scripts/lark-push init --chat-id oc_xxxxxxxx ``` Config is stored under **`~/.config/kedoupi/lark-push/`** by default (survives `npx skills update`). See the [online docs](https://github.com/kedoupi/lark-push-skill#readme) for load order and legacy paths. Inspect: ```bash bash /scripts/lark-push doctor bash /scripts/lark-push config-path bash /scripts/lark-push which-config ``` ## Safety Messages are visible in the group. Before sending a real message, confirm: - recipient group or person (`chat-id`) - message content - sending identity (`bot` / `user`) If the user runs the helper script directly, that invocation is the approval. For previews, use `--dry-run` (local only — does **not** call `lark-cli` or touch the keychain). ## Usage ```bash # Environment check (print install hints if something is missing) bash /scripts/lark-push doctor # Preview (local; no network / no keychain) bash /scripts/lark-push --dry-run --kind code --title "Task done" --body "Implementation finished." # Markdown list body (leading '-' is valid) bash /scripts/lark-push --dry-run --kind daily --title "Daily" --body "- shipped A - blocked on B" # Daily report from stdin cat daily.md | bash /scripts/lark-push --kind daily --title "Daily report" # Weekly report from file bash /scripts/lark-push --kind weekly --title "Weekly report" --from-file weekly.md # One-off chat override bash /scripts/lark-push --chat-id oc_other --kind notice --title "Heads up" --body "..." ``` ## Message kinds | Kind | Use for | | --- | --- | | `code` | code completion, test result, PR/release status | | `daily` | daily standup report | | `weekly` | weekly report | | `release` | deployment or launch note | | `notice` | general message | ## Output formats | Format | Use for | | --- | --- | | `card` | default; polished Feishu Card 2.0 (requires `python3`) | | `markdown` | lightweight text post | ## Templates Code update body: ```text Done: - Verification: - Risks / next: - ``` Daily / weekly templates: `templates/daily.md`, `templates/weekly.md`. ## Key CLI options ```text doctor [--strict-auth] # environment checklist + install hints --kind --format --title --body --from-file --chat-id --as --idempotency-key # max 50 chars --dry-run # local preview only --no-context ``` Full reference: `bash /scripts/lark-push --help` or see the [online docs](https://github.com/kedoupi/lark-push-skill#readme). ## Optional: git post-commit hook Prefer a **symlink** (not a copy) so the hook always runs the latest helper (the hook locates the helper via known install paths under `~/.agents`, `~/.claude`, `~/.codex`, `~/.grok`): ```bash ln -sf ~/.agents/skills/lark-push/scripts/git-post-commit-lark-push \ .git/hooks/post-commit ``` Disable without removing the hook: ```bash export LARK_PUSH_GIT_HOOK=0 ``` ## Troubleshooting ```bash bash /scripts/lark-push doctor ``` If send fails: 1. Run `doctor` and fix any `[FAIL]` lines (Node, lark-cli, python3, chat id) 2. Confirm durable config: `bash /scripts/lark-push which-config` 3. Confirm the bot is in the target group and can send messages 4. Confirm `lark-cli` auth / scopes: ```bash LARKSUITE_CLI_NO_UPDATE_NOTIFIER=1 LARKSUITE_CLI_NO_SKILLS_NOTIFIER=1 \ lark-cli auth status --json --verify ```