@acedatacloud/skills 2026.703.11 → 2026.703.13

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@acedatacloud/skills",
-  "version": "2026.703.11",
+  "version": "2026.703.13",
   "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/nano-banana-image/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: nano-banana-image
-description: Generate and edit AI images with NanoBanana (Gemini-based) via AceDataCloud API. Use when creating images from text prompts or editing existing images with text instructions. Supports nano-banana, nano-banana-2, and nano-banana-pro models.
+description: Generate and edit AI images with NanoBanana (Gemini-based) via AceDataCloud API. Use when creating images from text prompts or editing existing images with text instructions. Supports nano-banana, nano-banana-2, nano-banana-pro and their :official variants.
 license: Apache-2.0
 metadata:
   author: acedatacloud
@@ -31,6 +31,9 @@ curl -X POST https://api.acedata.cloud/nano-banana/images \
 | `nano-banana` | Standard image generation (default) |
 | `nano-banana-2` | Improved quality, second generation |
 | `nano-banana-pro` | Highest quality, most detailed output |
+| `nano-banana:official` | Official channel variant of `nano-banana` |
+| `nano-banana-2:official` | Official channel variant of `nano-banana-2` |
+| `nano-banana-pro:official` | Official channel variant of `nano-banana-pro` |
 
 ## Workflows
 
@@ -66,7 +69,7 @@ POST /nano-banana/images
 | Parameter | Values | Description |
 |-----------|--------|-------------|
 | `action` | `"generate"`, `"edit"` | Operation mode |
-| `model` | `"nano-banana"`, `"nano-banana-2"`, `"nano-banana-pro"` | Model to use |
+| `model` | `"nano-banana"`, `"nano-banana-2"`, `"nano-banana-pro"`, `"nano-banana:official"`, `"nano-banana-2:official"`, `"nano-banana-pro:official"` | Model to use |
 | `prompt` | string | Image description or editing instruction |
 | `image_urls` | array of strings | Source image URLs (required for edit action) |
 | `aspect_ratio` | `"1:1"`, `"3:2"`, `"2:3"`, `"16:9"`, `"9:16"`, `"4:3"`, `"3:4"` | Output aspect ratio |
@@ -78,6 +81,7 @@ POST /nano-banana/images
 - Editing does **NOT** require a mask — just describe the change in natural language
 - Editing uses the same `/nano-banana/images` endpoint with `action: "edit"` and `image_urls` array (not a separate `/edit` path)
 - `nano-banana-2` is the second-generation model; `nano-banana-pro` offers the highest quality
+- `:official` variants (e.g., `nano-banana:official`) route through the official channel
 - Task polling uses `id` (not `task_id`) in the `/nano-banana/tasks` request body
 - Aspect ratio uses colon notation (e.g., `"16:9"`) not pixel dimensions
 - The Gemini-based model excels at understanding complex, conversational editing instructions

package/skills/vk/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: vk
+description: Publish posts to your VK (ВКонтакте) profile or community wall and read your own recent posts, via the official VK API (wall.post / wall.get). Use when the user wants to post to VK, cross-post an article for a Russian-speaking audience, or list their own recent VK wall posts with engagement. Auth uses a VK access token (community access key recommended).
+when_to_use: |
+  Trigger when the user wants to publish content to their VK wall or community,
+  or review their own recent VK posts. VK's user-token OAuth flows were disabled
+  in June 2024, so the connector stores a long-lived **community access key**
+  (VK community → Manage → Settings → API usage, with the `wall` right). Posting
+  to a community wall uses a negative owner_id + from_group=1. Confirm the post
+  text with the user before publishing.
+connections: [vk]
+allowed_tools: [Bash]
+license: Apache-2.0
+metadata:
+  author: acedatacloud
+  version: "1.0"
+---
+
+Call the **VK API** with `curl + jq`. The token is injected as `$VK_ACCESS_TOKEN`
+and is passed in the `Authorization: Bearer` header. **Every** VK API call also
+requires the `v` (API version) query parameter — use `v=5.199`. Base URL:
+`https://api.vk.com/method/<method>`.
+
+VK always returns HTTP 200; success is `{"response": ...}` and failure is
+`{"error":{"error_code":<n>,"error_msg":"<detail>"}}` — always check for `.error`
+and show `error_msg` verbatim. Common codes: `5` = auth failed (token wrong or
+revoked → user must re-connect the VK connector), `214` = access to adding post
+denied (the token lacks the `wall` right — a community access key with `wall` is
+required), `15`/`203` = access denied to that owner.
+
+## Step 1 — identify who you can post as
+
+A **community access key** posts on the community wall: `owner_id` must be the
+**negative** community id and you pass `from_group=1`. Resolve the community id
+from the token:
+
+```bash
+curl -sS "https://api.vk.com/method/groups.getById?v=5.199" \
+  -H "Authorization: Bearer $VK_ACCESS_TOKEN" \
+  | jq '.response, .error'
+```
+
+Take the group `id` (e.g. `123456`) → `owner_id` is `-123456`. (For a personal
+user token, `owner_id` is your positive user id from `users.get`, and you omit
+`from_group`.)
+
+## Post to the wall
+
+**Confirm the message text with the user before posting.** The post must have
+text and/or attachments.
+
+```bash
+OWNER_ID="-123456"   # negative = community; from_group=1 posts as the community
+MSG="Пример поста через VK API. #ai"
+curl -sS -G "https://api.vk.com/method/wall.post" \
+  -H "Authorization: Bearer $VK_ACCESS_TOKEN" \
+  --data-urlencode "v=5.199" \
+  --data-urlencode "owner_id=$OWNER_ID" \
+  --data-urlencode "from_group=1" \
+  --data-urlencode "message=$MSG" \
+  | jq '.response, .error'
+```
+
+Success returns `{"response":{"post_id":<id>}}`. The public URL is
+`https://vk.com/wall<OWNER_ID>_<post_id>` (e.g. `https://vk.com/wall-123456_17`).
+
+- Hashtags (`#tag`) and plain URLs in `message` are rendered/clickable natively —
+  no facet/offset handling needed (unlike Bluesky).
+- Attach media/links with `attachments` (comma-separated), format
+  `{type}{owner_id}_{media_id}` (e.g. `photo-123456_789`) or a single external
+  URL. Only **one** link may be attached; more than one link → error 222.
+- `publish_date` (Unix timestamp) schedules a deferred post.
+- Always send Cyrillic `message` via `--data-urlencode` so it isn't mangled.
+
+## List my recent wall posts + engagement
+
+```bash
+OWNER_ID="-123456"
+curl -sS -G "https://api.vk.com/method/wall.get" \
+  -H "Authorization: Bearer $VK_ACCESS_TOKEN" \
+  --data-urlencode "v=5.199" \
+  --data-urlencode "owner_id=$OWNER_ID" \
+  --data-urlencode "count=20" \
+  | jq '.error, (.response.items[]? | {id,
+        text,
+        likes: .likes.count,
+        reposts: .reposts.count,
+        comments: .comments.count,
+        views: .views.count,
+        date})'
+```
+
+`count` max 100. Combine `owner_id` + a post `id` to build the URL
+`https://vk.com/wall<owner_id>_<id>`.
+
+## Delete a post
+
+```bash
+OWNER_ID="-123456"; POST_ID="17"
+curl -sS -G "https://api.vk.com/method/wall.delete" \
+  -H "Authorization: Bearer $VK_ACCESS_TOKEN" \
+  --data-urlencode "v=5.199" \
+  --data-urlencode "owner_id=$OWNER_ID" \
+  --data-urlencode "post_id=$POST_ID" \
+  | jq '.response, .error'
+```
+
+## Gotchas
+
+- **`v` is mandatory** on every call — omitting it returns an error.
+- **User tokens can't be freshly minted via OAuth** (Implicit / Authorization
+  Code flows for user tokens were disabled 2024-06); use a **community access
+  key** (unlimited lifetime, created in the community's API settings) with the
+  `wall` right.
+- Posting as the community requires both `owner_id` negative **and**
+  `from_group=1`.
+- Rate/anti-spam: repeated identical posts or too-frequent posting can hit codes
+  like `214`/`219` — space posts out.