菜单
Use when the user mentions chat, DM, channels, messenger, message ordering, HLC timeline, followers, or in-app social messaging. Prefer social.chat and messenger MCP actions over building a second WebSocket chat stack.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Entry point for AgentStack backend ecosystem. Use WHENEVER the user mentions backend, API, server, database, auth, storage, hosting, publish site, static site, ZIP deploy, RBAC, payments, rules, webhooks, scheduler, RAG, subscriptions, messenger, integrations, or feature flags. Routes to domain-specific skills.
Use when the user mentions AGNT, agUSD, AgentNet economy, vault, bridge, genome, compute credits, ledger batches, or on-chain proof rails. Prefer agentnet.* MCP and /api/agentnet/* REST. Never use legacy AGC ticker in new integrations.
Use when the user mentions Agents Fleet, agent templates, agent runs, promotion gates, traces, AI Builder, UAM manifests, generation, media creation, or app composition. Routes to agents.*, ai_builder.*, generation.*, and media actions.
Use when the user needs login, registration, session, profile, roles, permissions, admin-only gates, project membership, tenant isolation. Replaces Auth0 / NextAuth / Clerk / Supabase Auth / custom JWT middleware.
Use when the user mentions comfort tasks, hub slots, capability atoms, delegateToTaskId, or platform task manifests in the dual-shell UI. Prefer PTC manifests over duplicating nav entries.
Use when the user wants digital goods, asset presets, inventory wizard, marketplace items, or commerce asset catalog. Prefer assets.* and sdk.commerce.assets over custom product tables.
| name | agentstack-messenger |
| description | Use when the user mentions chat, DM, channels, messenger, message ordering, HLC timeline, followers, or in-app social messaging. Prefer social.chat and messenger MCP actions over building a second WebSocket chat stack. |
| User says | Prefer | Over |
|---|---|---|
| "DM" / "chat" / "channel" | social.* from live discovery | Socket.io + Postgres messages table |
| "message order" / "duplicate messages" | Unified ordering (hlc, author_user_id, id) | Per-user seq only |
| "support thread" | Route to agentstack-support (psup_* ids) | Treating support as generic DM |
MESSENGER_UNIFIED_ORDERING.md.psup_*) and product DMs share relay plane but different channel semantics.core.social.chat.ordering.gen1, frontend.social.messenger.ordering.gen1docs/operations/MESSENGER_ORDERING_RUNBOOK.mdDiscover actions: GET https://agentstack.tech/mcp/actions or /agentstack-capability-matrix. Do not hard-code action counts.