القائمة
Cross-channel messaging — routing rules, channel affinity, how to send messages on each channel, safety rules. Trigger keywords: message, send message, reply, respond, channel, routing, corvid_send_message.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Git workflows — branching, committing, worktrees, branch isolation, merge strategies. Trigger keywords: git, commit, branch, merge, rebase, worktree, pull, push, cherry-pick.
Testing — writing and running tests with bun:test, test patterns, validation. Trigger keywords: test, testing, unit test, integration test, bun test, spec, assertion.
Pre-commit verification — tsc type checking, test suite, spec invariant checks. Trigger keywords: verify, validate, check, tsc, typecheck, spec check, pre-commit.
Discord messaging — how to send and receive messages, bridge architecture, user identity, formatting. Trigger keywords: discord, discord message, discord reply, discord user, discord bridge, send discord.
Use this skill when you need to discover remote agents, fetch their capabilities via A2A Agent Cards, or invoke tasks on remote A2A-compatible agents. Triggers include "discover agent", "find agent", "agent card", "invoke remote agent", "send task to agent", "A2A", or any reference to inter-agent communication beyond simple messaging.
Use this skill when the user wants to find code symbols (functions, classes, types), trace references across a codebase, or navigate code structure. Triggers include "find function", "where is this defined", "find references", "symbol search", "code navigation", "what calls this", or any request to locate or trace code entities.
| name | messaging |
| description | Cross-channel messaging — routing rules, channel affinity, how to send messages on each channel, safety rules. Trigger keywords: message, send message, reply, respond, channel, routing, corvid_send_message. |
Rules and patterns for sending and receiving messages across all channels.
Different channels have different mechanisms. Not everything requires an MCP tool.
| Channel | How to send | Mechanism |
|---|---|---|
| Discord | Write text directly | Bridge auto-routes your response |
| Telegram | Write text directly | Bridge auto-routes your response |
| Web UI | Write text directly | WebSocket auto-routes your response |
| AlgoChat | corvid_send_message | MCP tool (on-chain transaction) |
Key insight: For Discord, Telegram, and Web UI — you just write your response as text. The bridges handle delivery automatically. You only need corvid_send_message for AlgoChat (on-chain messaging) or proactive outreach to a different agent.
Your text response is automatically routed back through the originating channel's bridge.
corvid_send_messagecorvid_send_message to reply to someone who just messaged you — just write textAlways respond via the same channel the message came from.
corvid_send_message)corvid_send_messageWhen mentioning/pinging users, each channel has its own syntax:
| Channel | Mention syntax | Example |
|---|---|---|
| Discord | <@DISCORD_ID> | <@181969874455756800> |
| Telegram | @username | @leif_algo |
| AlgoChat | Algorand address | ALGO... |
Critical: On Discord, @DisplayName does NOT work — only <@numeric_id> actually pings/notifies the user. Get the Discord ID from the incoming message metadata or via corvid_lookup_contact.
| Channel | Format | Limits |
|---|---|---|
| Discord | Markdown subset (no tables) | 2000 chars |
| Telegram | Markdown V2 | 4096 chars |
| AlgoChat | Plain text (ARC-69 metadata) | ~1000 chars |
| Web UI | Full Markdown | No hard limit |