wolverine-ai 6.6.2 → 7.0.0

package/wolverine-claw/skills/discord/SKILL.md

@@ -0,0 +1,369 @@
+---
+name: discord
+description: Use when you need to control Discord from Clawdbot via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, fetch permissions or member/role/channel info, or handle moderation actions in Discord DMs or channels.
+---
+
+# Discord Actions
+
+## Overview
+
+Use `discord` to manage messages, reactions, threads, polls, and moderation. You can disable groups via `discord.actions.*` (defaults to enabled, except roles/moderation). The tool uses the bot token configured for Clawdbot.
+
+## Inputs to collect
+
+- For reactions: `channelId`, `messageId`, and an `emoji`.
+- For stickers/polls/sendMessage: a `to` target (`channel:<id>` or `user:<id>`). Optional `content` text.
+- Polls also need a `question` plus 2–10 `answers`.
+- For media: `mediaUrl` with `file:///path` for local files or `https://...` for remote.
+- For emoji uploads: `guildId`, `name`, `mediaUrl`, optional `roleIds` (limit 256KB, PNG/JPG/GIF).
+- For sticker uploads: `guildId`, `name`, `description`, `tags`, `mediaUrl` (limit 512KB, PNG/APNG/Lottie JSON).
+
+Message context lines include `discord message id` and `channel` fields you can reuse directly.
+
+**Note:** `sendMessage` uses `to: "channel:<id>"` format, not `channelId`. Other actions like `react`, `readMessages`, `editMessage` use `channelId` directly.
+
+## Actions
+
+### React to a message
+
+```json
+{
+  "action": "react",
+  "channelId": "123",
+  "messageId": "456",
+  "emoji": "✅"
+}
+```
+
+### List reactions + users
+
+```json
+{
+  "action": "reactions",
+  "channelId": "123",
+  "messageId": "456",
+  "limit": 100
+}
+```
+
+### Send a sticker
+
+```json
+{
+  "action": "sticker",
+  "to": "channel:123",
+  "stickerIds": ["9876543210"],
+  "content": "Nice work!"
+}
+```
+
+- Up to 3 sticker IDs per message.
+- `to` can be `user:<id>` for DMs.
+
+### Upload a custom emoji
+
+```json
+{
+  "action": "emojiUpload",
+  "guildId": "999",
+  "name": "party_blob",
+  "mediaUrl": "file:///tmp/party.png",
+  "roleIds": ["222"]
+}
+```
+
+- Emoji images must be PNG/JPG/GIF and <= 256KB.
+- `roleIds` is optional; omit to make the emoji available to everyone.
+
+### Upload a sticker
+
+```json
+{
+  "action": "stickerUpload",
+  "guildId": "999",
+  "name": "clawdbot_wave",
+  "description": "Clawdbot waving hello",
+  "tags": "👋",
+  "mediaUrl": "file:///tmp/wave.png"
+}
+```
+
+- Stickers require `name`, `description`, and `tags`.
+- Uploads must be PNG/APNG/Lottie JSON and <= 512KB.
+
+### Create a poll
+
+```json
+{
+  "action": "poll",
+  "to": "channel:123",
+  "question": "Lunch?",
+  "answers": ["Pizza", "Sushi", "Salad"],
+  "allowMultiselect": false,
+  "durationHours": 24,
+  "content": "Vote now"
+}
+```
+
+- `durationHours` defaults to 24; max 32 days (768 hours).
+
+### Check bot permissions for a channel
+
+```json
+{
+  "action": "permissions",
+  "channelId": "123"
+}
+```
+
+## Ideas to try
+
+- React with ✅/⚠️ to mark status updates.
+- Post a quick poll for release decisions or meeting times.
+- Send celebratory stickers after successful deploys.
+- Upload new emojis/stickers for release moments.
+- Run weekly “priority check” polls in team channels.
+- DM stickers as acknowledgements when a user’s request is completed.
+
+## Action gating
+
+Use `discord.actions.*` to disable action groups:
+- `reactions` (react + reactions list + emojiList)
+- `stickers`, `polls`, `permissions`, `messages`, `threads`, `pins`, `search`
+- `emojiUploads`, `stickerUploads`
+- `memberInfo`, `roleInfo`, `channelInfo`, `voiceStatus`, `events`
+- `roles` (role add/remove, default `false`)
+- `moderation` (timeout/kick/ban, default `false`)
+### Read recent messages
+
+```json
+{
+  "action": "readMessages",
+  "channelId": "123",
+  "limit": 20
+}
+```
+
+### Send/edit/delete a message
+
+```json
+{
+  "action": "sendMessage",
+  "to": "channel:123",
+  "content": "Hello from Clawdbot"
+}
+```
+
+**With media attachment:**
+
+```json
+{
+  "action": "sendMessage",
+  "to": "channel:123",
+  "content": "Check out this audio!",
+  "mediaUrl": "file:///tmp/audio.mp3"
+}
+```
+
+- `to` uses format `channel:<id>` or `user:<id>` for DMs (not `channelId`!)
+- `mediaUrl` supports local files (`file:///path/to/file`) and remote URLs (`https://...`)
+- Optional `replyTo` with a message ID to reply to a specific message
+
+```json
+{
+  "action": "editMessage",
+  "channelId": "123",
+  "messageId": "456",
+  "content": "Fixed typo"
+}
+```
+
+```json
+{
+  "action": "deleteMessage",
+  "channelId": "123",
+  "messageId": "456"
+}
+```
+
+### Threads
+
+```json
+{
+  "action": "threadCreate",
+  "channelId": "123",
+  "name": "Bug triage",
+  "messageId": "456"
+}
+```
+
+```json
+{
+  "action": "threadList",
+  "guildId": "999"
+}
+```
+
+```json
+{
+  "action": "threadReply",
+  "channelId": "777",
+  "content": "Replying in thread"
+}
+```
+
+### Pins
+
+```json
+{
+  "action": "pinMessage",
+  "channelId": "123",
+  "messageId": "456"
+}
+```
+
+```json
+{
+  "action": "listPins",
+  "channelId": "123"
+}
+```
+
+### Search messages
+
+```json
+{
+  "action": "searchMessages",
+  "guildId": "999",
+  "content": "release notes",
+  "channelIds": ["123", "456"],
+  "limit": 10
+}
+```
+
+### Member + role info
+
+```json
+{
+  "action": "memberInfo",
+  "guildId": "999",
+  "userId": "111"
+}
+```
+
+```json
+{
+  "action": "roleInfo",
+  "guildId": "999"
+}
+```
+
+### List available custom emojis
+
+```json
+{
+  "action": "emojiList",
+  "guildId": "999"
+}
+```
+
+### Role changes (disabled by default)
+
+```json
+{
+  "action": "roleAdd",
+  "guildId": "999",
+  "userId": "111",
+  "roleId": "222"
+}
+```
+
+### Channel info
+
+```json
+{
+  "action": "channelInfo",
+  "channelId": "123"
+}
+```
+
+```json
+{
+  "action": "channelList",
+  "guildId": "999"
+}
+```
+
+### Voice status
+
+```json
+{
+  "action": "voiceStatus",
+  "guildId": "999",
+  "userId": "111"
+}
+```
+
+### Scheduled events
+
+```json
+{
+  "action": "eventList",
+  "guildId": "999"
+}
+```
+
+### Moderation (disabled by default)
+
+```json
+{
+  "action": "timeout",
+  "guildId": "999",
+  "userId": "111",
+  "durationMinutes": 10
+}
+```
+
+## Discord Writing Style Guide
+
+**Keep it conversational!** Discord is a chat platform, not documentation.
+
+### Do
+- Short, punchy messages (1-3 sentences ideal)
+- Multiple quick replies > one wall of text
+- Use emoji for tone/emphasis 🦞
+- Lowercase casual style is fine
+- Break up info into digestible chunks
+- Match the energy of the conversation
+
+### Don't
+- No markdown tables (Discord renders them as ugly raw `| text |`)
+- No `## Headers` for casual chat (use **bold** or CAPS for emphasis)
+- Avoid multi-paragraph essays
+- Don't over-explain simple things
+- Skip the "I'd be happy to help!" fluff
+
+### Formatting that works
+- **bold** for emphasis
+- `code` for technical terms
+- Lists for multiple items
+- > quotes for referencing
+- Wrap multiple links in `<>` to suppress embeds
+
+### Example transformations
+
+❌ Bad:
+```
+I'd be happy to help with that! Here's a comprehensive overview of the versioning strategies available:
+
+## Semantic Versioning
+Semver uses MAJOR.MINOR.PATCH format where...
+
+## Calendar Versioning
+CalVer uses date-based versions like...
+```
+
+✅ Good:
+```
+versioning options: semver (1.2.3), calver (2026.01.04), or yolo (`latest` forever). what fits your release cadence?
+```

package/wolverine-claw/skills/discord/_meta.json

@@ -0,0 +1,6 @@
+{
+  "ownerId": "kn70pywhg0fyz996kpa8xj89s57yhv26",
+  "slug": "discord",
+  "version": "1.0.1",
+  "publishedAt": 1767574303488
+}

package/wolverine-claw/skills/telegram/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: telegram
+description: OpenClaw skill for designing Telegram Bot API workflows and command-driven conversations using direct HTTPS requests (no SDKs).
+---
+
+# Telegram Bot Skill (Advanced)
+
+## Purpose
+Provide a clean, production-oriented guide for building Telegram bot workflows via the Bot API, focusing on command UX, update handling, and safe operations using plain HTTPS.
+
+## Best fit
+- You want a command-first bot that behaves professionally.
+- You need a reliable update flow (webhook or polling).
+- You prefer direct HTTP calls instead of libraries.
+
+## Not a fit
+- You require a full SDK or framework integration.
+- You need complex media uploads and streaming in-process.
+
+## Quick orientation
+- Read `references/telegram-bot-api.md` for endpoints, update types, and request patterns.
+- Read `references/telegram-commands-playbook.md` for command UX and messaging style.
+- Read `references/telegram-update-routing.md` for update normalization and routing rules.
+- Read `references/telegram-request-templates.md` for HTTP payload templates.
+- Keep this SKILL.md short and use references for details.
+
+## Required inputs
+- Bot token and base API URL.
+- Update strategy: webhook or long polling.
+- Command list and conversation tone.
+- Allowed update types and rate-limit posture.
+
+## Expected output
+- A clear command design, update flow plan, and operational checklist.
+
+## Operational notes
+- Prefer strict command routing: `/start`, `/help`, `/settings`, `/status`.
+- Always validate incoming update payloads and chat context.
+- Handle 429s with backoff and avoid message bursts.
+
+## Security notes
+- Never log tokens.
+- Use webhooks with a secret token header when possible.

package/wolverine-claw/skills/telegram/_meta.json

@@ -0,0 +1,6 @@
+{
+  "ownerId": "kn7ehv4at8yekzag31spcarxm180bev0",
+  "slug": "telegram",
+  "version": "1.0.1",
+  "publishedAt": 1770028389996
+}

package/wolverine-claw/skills/telegram/references/telegram-bot-api.md

@@ -0,0 +1,63 @@
+# Telegram Bot API Field Notes
+
+## 1) Base URL and request style
+- Base format: `https://api.telegram.org/bot<token>/<method>`
+- Use GET or POST with JSON or form-encoded payloads.
+- File uploads use `multipart/form-data` and `attach://` references.
+
+## 2) Updates and delivery models
+### Long polling
+- `getUpdates` delivers updates with an `offset` cursor and `timeout`.
+
+### Webhook
+- `setWebhook` switches the bot to webhook mode.
+- Webhook URLs must be HTTPS. Check the official docs for port restrictions.
+
+### Update types (examples)
+- `message`, `edited_message`, `channel_post`, `edited_channel_post`
+- `inline_query`, `chosen_inline_result`, `callback_query`
+- `shipping_query`, `pre_checkout_query`, `poll`, `poll_answer`
+
+Use `allowed_updates` to limit which updates you receive.
+
+## 3) High-traffic-safe patterns
+- Use `allowed_updates` to reduce noise.
+- Keep handlers idempotent (Telegram may retry).
+- Return quickly from webhooks; process heavy work async.
+
+## 4) Common methods (non-exhaustive)
+- `getMe`, `getUpdates`, `setWebhook`
+- `sendMessage`, `editMessageText`, `deleteMessage`
+- `sendPhoto`, `sendDocument`, `sendChatAction`
+- `answerCallbackQuery`, `answerInlineQuery`
+
+## 5) Common fields (non-exhaustive)
+### sendMessage
+- `chat_id`, `text`, `parse_mode`
+- `entities`, `disable_web_page_preview`
+- `reply_markup` (inline keyboard, reply keyboard)
+
+### reply_markup (inline keyboard)
+- `inline_keyboard`: array of button rows
+- Buttons can contain `text` + `callback_data` or `url`
+
+### callback_query
+- `id`, `from`, `message`, `data`
+
+### sendChatAction
+- `action`: `typing`, `upload_photo`, `upload_document`, `upload_video`, `choose_sticker`
+
+## 6) Command UX checklist
+- `/start`: greet, explain features, and show main commands.
+- `/help`: include short examples and support contact.
+- `/settings`: show toggles with inline keyboards.
+- `/status`: show recent job results or queue size.
+
+## 7) Error handling
+- `429`: back off and retry.
+- `400`: validate chat_id, message length, and formatting.
+- `403`: bot blocked or chat not accessible.
+
+## 8) Reference links
+- https://core.telegram.org/bots/api
+- https://core.telegram.org/bots/faq

package/wolverine-claw/skills/telegram/references/telegram-commands-playbook.md

@@ -0,0 +1,26 @@
+# Telegram Command Playbook
+
+## Command set (professional baseline)
+- `/start`: greet, set expectations, and show main actions.
+- `/help`: short help + examples.
+- `/status`: show last job result, queue length, or uptime.
+- `/settings`: show toggles via inline keyboard.
+- `/about`: short bot description and support contact.
+
+## Command UX patterns
+- Acknowledge fast, then do heavy work asynchronously.
+- Prefer short replies with a single call-to-action.
+- Always include “what next?” in `/start` and `/help`.
+
+## Inline keyboard patterns
+- Use stable callback_data names (e.g., `settings:notifications:on`).
+- Keep callbacks idempotent.
+
+## Message style guidelines
+- Use MarkdownV2 or HTML consistently; avoid mixing.
+- If using MarkdownV2, escape reserved characters.
+- Keep single message length under safe limits; split when needed.
+
+## Examples (short)
+- `/start` reply: “Hi! I can publish posts and send alerts. Try /help.”
+- `/status` reply: “Queue: 2 jobs. Last run: success 2m ago.”

package/wolverine-claw/skills/telegram/references/telegram-request-templates.md

@@ -0,0 +1,42 @@
+# Telegram Request Templates (HTTP)
+
+## sendMessage
+POST `/sendMessage`
+```json
+{
+  "chat_id": 123456789,
+  "text": "Hello",
+  "parse_mode": "HTML",
+  "disable_web_page_preview": true
+}
+```
+
+## editMessageText
+POST `/editMessageText`
+```json
+{
+  "chat_id": 123456789,
+  "message_id": 42,
+  "text": "Updated",
+  "parse_mode": "HTML"
+}
+```
+
+## answerCallbackQuery
+POST `/answerCallbackQuery`
+```json
+{
+  "callback_query_id": "1234567890",
+  "text": "Saved"
+}
+```
+
+## setWebhook
+POST `/setWebhook`
+```json
+{
+  "url": "https://example.com/telegram/webhook",
+  "secret_token": "your-secret",
+  "allowed_updates": ["message","callback_query"]
+}
+```

package/wolverine-claw/skills/telegram/references/telegram-update-routing.md

@@ -0,0 +1,23 @@
+# Telegram Update Routing
+
+## Update normalization
+- Normalize inbound updates to a single envelope:
+  - `update_id`, `chat_id`, `user_id`, `message_id`, `text`, `callback_data`, `type`
+- This makes routing logic consistent across message types.
+
+## Routing rules
+- If `callback_query` exists, handle callbacks first.
+- Else if `message.text` starts with `/`, treat as command.
+- Else fall back to default handler (help or menu).
+
+## Safe defaults
+- Unknown command: reply with `/help` guidance.
+- Unknown callback: answerCallbackQuery with a short notice.
+
+## Idempotency
+- Keep a cache of processed `update_id` in case of retries.
+- Ensure handlers can be safely re-run.
+
+## Error handling
+- On 429: backoff and retry with jitter.
+- On 400: validate payload length and parse mode.

package/wolverine-claw/skills/twitter-post/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: twitter-post
+description: Post tweets to Twitter/X via the official API v2 (OAuth 1.0a). Use when the user asks to tweet, post to Twitter/X, send a thread, reply to a tweet, or quote tweet. Supports single tweets, threads, replies, and quote tweets with automatic character weight validation.
+---
+
+# Twitter Post
+
+Post tweets via the official Twitter/X API v2 using OAuth 1.0a authentication.
+
+## Prerequisites
+
+Four environment variables must be set. Obtain them from [developer.x.com](https://developer.x.com):
+
+```
+TWITTER_CONSUMER_KEY=<API Key>
+TWITTER_CONSUMER_SECRET=<API Key Secret>
+TWITTER_ACCESS_TOKEN=<Access Token>
+TWITTER_ACCESS_TOKEN_SECRET=<Access Token Secret>
+```
+
+Optional:
+- `HTTPS_PROXY` — HTTP proxy URL (e.g. `http://127.0.0.1:7897`) for regions that need it
+- `TWITTER_DRY_RUN=1` — validate and print without posting
+
+## Setup
+
+Store credentials as env vars. Recommended: add to the OpenClaw instance config or export in shell profile. **Never hardcode keys in SKILL.md or scripts.**
+
+If the user hasn't set up OAuth yet, guide them:
+
+1. Go to [developer.x.com](https://developer.x.com) → Dashboard → Create App
+2. Set **App permissions** to **Read and Write**
+3. Go to **Keys and tokens** tab
+4. Copy API Key, API Key Secret
+5. Generate Access Token and Access Token Secret (ensure Read+Write scope)
+6. If the portal only shows Read, use PIN-based OAuth flow:
+   - Call `POST /oauth/request_token` with `oauth_callback=oob`
+   - User opens `https://api.twitter.com/oauth/authorize?oauth_token=<token>`
+   - User provides the PIN code
+   - Call `POST /oauth/access_token` with the PIN as `oauth_verifier`
+
+## Usage
+
+All commands via `exec`. Script path: `scripts/tweet.js` (relative to this skill directory).
+
+### Single tweet
+
+```bash
+node scripts/tweet.js "Your tweet content here"
+```
+
+### Reply to a tweet
+
+```bash
+node scripts/tweet.js --reply-to 1234567890 "Reply text"
+```
+
+### Quote tweet
+
+```bash
+node scripts/tweet.js --quote 1234567890 "Your commentary"
+```
+
+### Thread (multiple tweets)
+
+```bash
+node scripts/tweet.js --thread "First tweet" "Second tweet" "Third tweet"
+```
+
+### Output
+
+JSON to stdout:
+
+```json
+{"ok":true,"id":"123456789","url":"https://x.com/i/status/123456789","remaining":"99","limit":"100"}
+```
+
+On error: `{"ok":false,"error":"..."}`
+
+## Character Limits
+
+- Max 280 weighted characters per tweet
+- CJK characters (Chinese/Japanese/Korean) count as **2** each
+- URLs count as **23** each regardless of length
+- Script auto-validates before posting; rejects if over limit
+
+## Rate Limits
+
+- **100 tweets / 15 min** per user (OAuth 1.0a)
+- **3,000 tweets / month** on Basic plan ($200/mo)
+- Check `remaining` field in output to monitor quota
+
+## Tips
+
+- For content from Notion/database: fetch the text first, then pipe to `tweet.js`
+- For cron-based auto-posting: use `exec` with env vars set, parse JSON output to confirm success
+- Thread mode posts sequentially; each tweet auto-replies to the previous one
+- Combine `--thread` with `--reply-to` to attach a thread under an existing tweet

package/wolverine-claw/skills/twitter-post/_meta.json

@@ -0,0 +1,6 @@
+{
+  "ownerId": "kn71sy0jgf8rh8t0kdz031jtx581a61b",
+  "slug": "twitter-post",
+  "version": "1.0.0",
+  "publishedAt": 1771382112380
+}