メニュー
Tell a client where the matter is, what it costs and what happens next.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/vstorm-co/agenticos --skill client-update-letterコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
| name | Client update letter |
| description | Tell a client where the matter is, what it costs and what happens next. |
| category | content |
Most complaints about lawyers are about communication, not outcomes. This is the cheapest thing a firm can do well.
Where we are — what has happened since the last update, in plain language. What it means — the consequence for them, not the procedural step. What happens next — with a date, and who does it. Costs — incurred to date against estimate, and any change to the estimate, with the reason.
Even when nothing has changed, say so. A silent period followed by a bill is the single largest source of fee disputes.
Replace procedural terminology with what it means for them, keeping the term in brackets once. "The other side has to file their defence by 14 March (acknowledgement of service)".
First paragraph, plainly, with what is being done about it. Bad news buried on page two reads as concealment when it is found.
Predict an outcome as a probability, promise a timescale controlled by a court or another party, or leave a question from the client's last message unanswered.
Work with messaging-channel bots — Telegram, Slack or Mattermost. Register a bot, route inbound messages through an agent, choose webhook vs polling, handle an @slug mention, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery, identity linking or "the bot answered as itself".
Change the agent spec — add or remove a field, rename one, tighten a rule, bump SPEC_VERSION, change publish-time validation, or touch YAML export/import. Use whenever editing app/agents/spec.py or anything that reads a stored spec. Every published agent and every client git repository holds a copy of this format, so a change that only works forwards breaks agents nobody touched.
Work with MCP servers — connect one, add an entry to the server catalog, debug "the agent cannot see my MCP tools" or a failing OAuth flow, or change how connections are probed, prefixed or filtered. Use when the ask involves an external SaaS tool (GitHub, Linear, Notion, Slack, Stripe, Postgres…) and before writing a capability that would just be an API client for one.