メニュー
Prepares the user's concise, spoken work update for recurring Tuesday and Thursday evening meetings. Use when the user asks for a meeting update, boss update, or summary of what they completed since the previous meeting.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Marve10s/melete --skill meeting-updateコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Write reports, plans, audits, explainers, and comparisons for the user as rich single-file HTML instead of markdown. Use whenever producing a report, implementation plan, audit result, research summary, PR walkthrough, or design exploration addressed to the user, however phrased ("write up what you found", "make a plan", "summarize the audit").
Generate or edit raster images by calling the ChatGPT/Codex Responses image_generation tool directly with local Codex or OpenClaw OAuth credentials, then save decoded image files for OpenClaw and other agent workflows.
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
SKILL.md を表示中
| name | meeting-update |
| description | Prepares the user's concise, spoken work update for recurring Tuesday and Thursday evening meetings. Use when the user asks for a meeting update, boss update, or summary of what they completed since the previous meeting. |
Use the user's current local timezone and treat 18:00 as the evening meeting boundary.
The opening boundary is exclusive. Do not repeat work completed earlier on the previous meeting day; the user already covered it in that evening's update.
Use repository and GitHub history as the source of truth. Collect work by the user's GitHub account that reached a shared branch during the window:
Do not count the same change twice when a PR and its merge or squash commit both appear. Exclude other authors' work. Exclude unmerged or unfinished work unless the user asks to include work in progress.
Combine related changes into one meaningful item. Describe the problem solved, user or business effect, and important context rather than filenames, implementation inventories, test commands, or commit mechanics.
Write a short first-person update that the user can say naturally in a meeting. Lead with the most important outcome and keep the language understandable to a nontechnical manager. Do not add confidence scores, verification sections, commit hashes, or a long source list.
If the history is ambiguous or incomplete, state the uncertainty instead of inventing work. Include PR links or a compact evidence list only when the user asks for it.
