菜单
Reply to a member request that was addressed to your handle. Use this skill when another member triggered your turn through a member request and your output is the reply they are waiting on.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/juliakrivchikova/AccordAgents-desktop-app --skill app-chat-reply命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Safely issue and verify AccordAgents macOS beta releases. Use when asked to prepare, run, resume, troubleshoot, or document `npm run release:beta`, publish a beta tag, or validate beta DMG, ZIP, signing, notarization, and update-feed artifacts.
Coordinate a reusable multi-agent implementation workflow for feature or bug delivery. Use when the user wants a manager participant to understand a requirement, confirm scope, run a blind-draft accord for the implementation plan, delegate implementation in a separate worktree, require Electron desktop QA when relevant, run a blind-draft accord for required fixes from independent review, coordinate fixes, optionally open a user-check instance, and prepare delivery to main.
Facilitate a skeptical multi-member AccordAgents discussion that ends in one agreed resolution approved by every selected member. Use only when User explicitly wants an accord, multi-member consensus, cross-checking by named members, or a resolution approved by multiple agents. Do not use for an ordinary single-agent answer, review, double-check, or "what do you think".
基于 SOC 职业分类
正在显示 SKILL.md
| name | app-chat-reply |
| description | Reply to a member request that was addressed to your handle. Use this skill when another member triggered your turn through a member request and your output is the reply they are waiting on. |
Use this skill when another participant triggered your turn through a participant request and your output is the reply they are waiting on.
A participant request is a structured ask from one participant to another. The requester is paused on your answer. In the normal path, answer directly in the active request thread; the app can attach an unambiguous reply to the request and resume the requester.
Do not use this skill when the user pinged you directly, when you are starting a new topic, or when no participant request is currently addressed to you.
Before you reply, decide exactly which request your answer belongs to.
target is you and whose prompt matches that triggering message in that
thread. In normal operation there is exactly one.Write the answer directly in the current chat thread. If the requester asked for an exact format, output only that required content. If you cannot answer, state the blocker clearly in the reply.
Use this order when deciding what to answer:
Do not reread the full chat history unless the request cannot be understood from the triggering message, current thread, or request metadata.