@acedatacloud/skills 2026.703.6 → 2026.703.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@acedatacloud/skills",
-  "version": "2026.703.6",
+  "version": "2026.703.8",
   "description": "Agent Skills for AceDataCloud AI services — music, image, video generation, LLM chat, web search. Compatible with Claude Code, GitHub Copilot, Gemini CLI, OpenAI Codex, and 30+ AI coding agents.",
   "keywords": [
     "agent-skills",

package/skills/tgstat/SKILL.md

@@ -0,0 +1,110 @@
+---
+name: tgstat
+description: Search Telegram channels/chats and pull audience + engagement stats (subscribers, reach, ER/ERR) from TGStat via its Stat API. Use when the user wants to find Telegram channels to advertise in (esp. Russian-language / RU market), research competitor channels, or check a channel's reach/engagement before buying an ad placement.
+when_to_use: |
+  Trigger when the user wants to discover Telegram channels by keyword /
+  category / country / language, inspect a specific channel's subscriber
+  count, average post reach and engagement (ER / ERR) to judge ad value,
+  or check their TGStat API quota. This is a marketing-research /
+  ad-channel-selection tool — it does NOT post to Telegram (use the
+  `telegram` connector for reading/sending messages).
+connections: [tgstat]
+allowed_tools: [Bash]
+license: Apache-2.0
+metadata:
+  author: acedatacloud
+  version: "1.0"
+---
+
+Call the **TGStat Stat API** with `curl + jq`. The user's token is in
+`$TGSTAT_TOKEN` and is passed as the `token` query parameter on every request.
+Base URL: `https://api.tgstat.ru`.
+
+Responses are JSON shaped `{"status":"ok","response": ...}`. Errors come back as
+`{"status":"error","error":"<message>"}` — show the `error` verbatim. An invalid
+token or an inactive/expired API plan will surface here; tell the user to check
+their token / plan in the TGStat 个人中心 and re-connect the connector.
+
+**Always confirm the token + remaining quota first** (`usage/stat` is free and
+does not count against tariff quota):
+
+```bash
+curl -sS "https://api.tgstat.ru/usage/stat?token=$TGSTAT_TOKEN" \
+  | jq '.status, (.response[]? | {serviceKey, title, spentChannels, spentRequests, expiredAt})'
+```
+
+## Find channels to advertise in (the main workflow)
+
+`GET /channels/search` — at least one of `q` (keyword, min 3 chars) or
+`category` is required.
+
+Params: `q`, `category`, `country`, `language` (default `russian`),
+`peer_type` (`channel` | `chat` | `all`, default `channel`),
+`search_by_description` (`0`/`1`), `limit` (max 100).
+
+```bash
+# Russian-language AI/ChatGPT channels, biggest first.
+curl -sS "https://api.tgstat.ru/channels/search" \
+  --data-urlencode "token=$TGSTAT_TOKEN" \
+  --data-urlencode "q=нейросети" \
+  --data-urlencode "language=russian" \
+  --data-urlencode "peer_type=channel" \
+  --data-urlencode "limit=50" -G \
+  | jq '.response.items | sort_by(-.participants_count)
+        | .[] | {username, title, subs: .participants_count, ci_index, link}'
+```
+
+- Use `--data-urlencode ... -G` so Cyrillic / spaces in `q` are encoded correctly.
+- `ci_index` (индекс цитирования) is TGStat's citation/authority score — higher =
+  more reposted/mentioned elsewhere, a useful quality signal beyond raw subs.
+- Try several keywords (`ChatGPT`, `нейросети`, `AI`, `разработка`, `API`) and
+  merge results; TGStat matches title/username (add `search_by_description=1` to
+  also match the channel description).
+
+## Judge a channel's ad value
+
+`GET /channels/stat?channelId=<@username | t.me/username | tgstat id>` returns
+the numbers that actually matter for ad pricing:
+
+```bash
+curl -sS "https://api.tgstat.ru/channels/stat?token=$TGSTAT_TOKEN&channelId=@durov" \
+  | jq '.response | {
+      subs: .participants_count,
+      avg_post_reach,          # средний охват публикации
+      adv_reach_24h: .adv_post_reach_24h,   # рекламный охват за 24ч — key for CPM
+      er_percent, err_percent, err24_percent,
+      daily_reach, ci_index, posts_count
+    }'
+```
+
+- For **ad CPM estimation** use `adv_post_reach_24h` (average *advertising* reach
+  of a post over 24h), not raw subscriber count — subs are vanity, reach is what
+  the ad actually gets seen by.
+- Low `err_percent` / `err24_percent` relative to subs = inflated/dead audience →
+  skip it.
+- For a **chat** (not channel) the response instead has `dau`/`wau`/`mau` and
+  `messages_count_*` fields.
+
+`GET /channels/get?channelId=...` returns descriptive info (title, about,
+`category`, `country`, `language`, `participants_count`, `ci_index`) when you
+just need to identify/verify a channel rather than full stats.
+
+## Reference data
+
+`GET /database/categories?token=$TGSTAT_TOKEN` lists valid `category` values you
+can pass to `channels/search`. There are also `/database/countries` and
+`/database/languages`. (See the docs for the full parameter/response shape.)
+
+## Gotchas
+
+- **Plan gating:** `channels/search` needs a **Stat API tariff S or higher**;
+  `channels/stat` / `channels/get` work on all Stat tariffs. If a call returns an
+  access error, the user's plan doesn't cover that method.
+- **Quota:** each unique channel and each request counts against the monthly
+  tariff (visible via `usage/stat`). Don't loop over hundreds of channels
+  blindly — search, shortlist, then `stat` only the shortlist.
+- **`q` min length is 3 chars** → `{"error":"param q is too short"}`.
+- **Cyrillic:** always send `q` via `--data-urlencode` (or pre-URL-encode) so the
+  keyword isn't mangled.
+- TGStat is a Russian service; the API and billing are RU-side — availability and
+  payment are the account owner's responsibility.

package/skills/wordpress/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: wordpress
+description: Publish and manage posts on a self-hosted WordPress site via the WordPress REST API. Use when the user mentions WordPress, wp-admin, publishing / updating a blog post, managing categories or tags, or uploading media to their own WordPress site.
+when_to_use: |
+  Trigger when the user wants to do anything with their self-hosted
+  WordPress site: turn a chat conversation into a published or draft
+  post, update an existing post, list recent posts, create / list
+  categories and tags, or upload a media file for use inside a post.
+  This skill is for self-hosted WordPress (Application Password auth),
+  not WordPress.com.
+connections: [wordpress]
+allowed_tools: [Bash]
+license: Apache-2.0
+metadata:
+  author: acedatacloud
+  version: "1.0"
+---
+
+Drive the **WordPress REST API** (`/wp-json/wp/v2`) with `curl + jq`.
+
+The user's self-hosted WordPress credentials are injected as env vars:
+
+- `$WORDPRESS_SITE_URL` — site root, e.g. `https://blog.example.com`
+- `$WORDPRESS_USERNAME` — the WordPress login username
+- `$WORDPRESS_APP_PASSWORD` — an **Application Password** (WP 5.6+ core), NOT the
+  login password. Treat it like a secret — **never log or echo it.**
+
+Auth is HTTP Basic (`username:app_password`) over HTTPS. Set up a reusable base
+once, then every call reuses it:
+
+```bash
+# Normalize the site URL (strip a trailing slash) and build the API base.
+SITE="${WORDPRESS_SITE_URL%/}"
+API="$SITE/wp-json/wp/v2"
+# -u sends HTTP Basic auth; --fail-with-body surfaces the JSON error body on 4xx/5xx.
+WP=(curl -sS --fail-with-body -u "$WORDPRESS_USERNAME:$WORDPRESS_APP_PASSWORD")
+```
+
+Errors come back as `{"code": "...", "message": "...", "data": {"status": 401}}` —
+show `message` verbatim. Common codes:
+
+| HTTP | Meaning | What to tell the user |
+|------|---------|-----------------------|
+| 401 | `incorrect_password` / bad Basic auth | Application Password wrong or revoked → regenerate it and reconnect the WordPress connector |
+| 403 | `rest_cannot_create` / insufficient role | The user's role can't publish; needs Author/Editor/Admin, or Application Passwords are disabled on the site |
+| 404 | `rest_no_route` | REST API disabled or a security plugin blocks `/wp-json` → the user must re-enable it |
+| 400 | `rest_invalid_param` | Bad field (e.g. unknown category id) → fix and retry |
+
+> **`content` is HTML, not Markdown.** Convert Markdown to HTML first
+> (`pandoc -f markdown -t html`, or a simple converter). Raw Markdown renders literally.
+
+## Step 0 — verify the connection first
+
+```bash
+"${WP[@]}" "$API/users/me" | jq '{id, name, slug, roles: (.roles // [])}'
+```
+
+A 200 with your user object confirms the site URL, username, and Application
+Password all work. If this fails, stop and surface the error — don't attempt writes.
+
+## Publish or draft a post
+
+**Publishing is public and hard to undo — confirm with the user before using
+`status=publish`.** Default to `status=draft` and hand back the edit link.
+
+```bash
+jq -n --arg t "国内如何稳定调用 Claude API" \
+      --arg c "<p>正文 HTML……</p>" \
+      --arg s "draft" \
+  '{title:$t, content:$c, status:$s}' \
+| "${WP[@]}" -X POST "$API/posts" \
+    -H "Content-Type: application/json" -d @- \
+| jq '{id, status, link, edit: "\(env.WORDPRESS_SITE_URL)/wp-admin/post.php?action=edit&post=\(.id)"}'
+```
+
+With categories / tags / excerpt (ids come from the endpoints below):
+
+```bash
+jq -n --arg t "标题" --arg c "<p>正文</p>" --arg e "一句话摘要" \
+  '{title:$t, content:$c, excerpt:$e, status:"draft",
+    categories:[5], tags:[12,34]}' \
+| "${WP[@]}" -X POST "$API/posts" -H "Content-Type: application/json" -d @- \
+| jq '{id, status, link}'
+```
+
+- Publish an existing draft: `POST $API/posts/<id>` body `{"status":"publish"}`.
+- Update a post: `POST $API/posts/<id>` with any subset of fields (WP REST uses
+  POST, not PUT, for updates).
+- Delete (trash) a post: `"${WP[@]}" -X DELETE "$API/posts/<id>"`.
+
+## List / read posts
+
+```bash
+"${WP[@]}" "$API/posts?per_page=10&status=publish,draft&_fields=id,title,status,link,date" \
+  | jq '.[] | {id, title: .title.rendered, status, link, date}'
+```
+
+Paginate with `&page=2`; the total page count is in the `X-WP-TotalPages`
+response header (add `-D -` to see headers).
+
+## Categories & tags (get or create ids)
+
+```bash
+# List existing
+"${WP[@]}" "$API/categories?per_page=100&_fields=id,name,slug" | jq '.[] | {id, name}'
+"${WP[@]}" "$API/tags?per_page=100&_fields=id,name,slug"       | jq '.[] | {id, name}'
+
+# Create one (returns its id)
+jq -n --arg n "AI 教程" '{name:$n}' \
+| "${WP[@]}" -X POST "$API/categories" -H "Content-Type: application/json" -d @- \
+| jq '{id, name}'
+```
+
+Creating a term that already exists returns
+`{"code":"term_exists", ... "data":{"status":400,"term_id":<id>}}` — reuse
+`.data.term_id` instead of failing.
+
+## Upload media (featured image / in-body image)
+
+```bash
+FILE="./cover.png"
+NAME="$(basename "$FILE")"
+MEDIA_ID=$("${WP[@]}" -X POST "$API/media" \
+  -H "Content-Disposition: attachment; filename=\"$NAME\"" \
+  -H "Content-Type: image/png" \
+  --data-binary @"$FILE" | jq -r '.id')
+echo "media id=$MEDIA_ID"
+# Attach as the post's featured image:
+#   add  "featured_media": <MEDIA_ID>  to the post body.
+```
+
+## Gotchas
+
+- **HTTPS + Application Passwords are required.** On plain `http://`, WordPress
+  disables Application Passwords → every call 401s. Tell the user to enable HTTPS.
+- **A security plugin / host may block `/wp-json`** (Wordfence, "disable REST
+  API" plugins, some managed hosts). Symptom: 404 `rest_no_route` or an HTML
+  login page instead of JSON. The user must allow REST API access.
+- **The Application Password contains spaces** (e.g. `abcd efgh ijkl mnop`).
+  Keep them — `curl -u` handles the spaces fine; don't strip them.
+- **Never publish silently.** Even if the user says "post it", prefer creating a
+  draft and returning the `wp-admin` edit link unless they explicitly asked to
+  go live.