Capture decisions and commitments after a meeting and draft a concise follow-up.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Identify the exact meeting and inspect its note or bounded transcript using screenpipe-api. Keep stated intent, agreed work, and completed work separate.
Never infer who spoke from the wording of a transcript. Speaker separation is an audio problem, not a text one, and guessing it is how commitments get assigned to the wrong person. Get attribution from the deterministic layer instead: python ~/.claude/scripts/_shared/speaker_truth.py --timeline --hours N (add --jsonl for machine use, --llm-contract for what you may and may not change). Lines it marks at confidence 1.00 come from the recording device and are not yours to reassign; ГОСТЬ-<id> may be given a name from context; ГОСТЬ-? stays unknown. A desk microphone hears the whole room, so on one it proves whose machine is recording, not whose voice it is.
Write the outcome, decisions, owners, due dates explicitly mentioned, and open questions. Do not invent owners or dates. Include a source link and flag gaps in recording. Draft a short follow-up when requested. Check the user’s current casing and punctuation preferences. Sending, updating external systems, or creating calendar events requires the user’s explicit request.
<!--kit-footer-->Like this skill? It is part of second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.
Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).
Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_
Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Run an autonomous consensus round between agent peers on several machines: they negotiate a decision over a shared channel and execute it without a human relaying messages. Use when multiple machines must agree on a change. Triggers: "/03", "work it out among yourselves", "find consensus". Wakes the human only for irreversible actions or a deadlock.
中文简介正在准备中。当前显示原文说明。
Recover a session after a hard crash (app died, machine rebooted, context lost mid-work): replay the turn-state ledger for the last requests, files and decisions, run a green/red health ping over the system map, file sync and MCP connectors, then rebuild the previous session history for pickup. Triggers: "/1", "resume after crash", "wake".
中文简介正在准备中。当前显示原文说明。
Show the operator's day: today's calendar plus what needs them personally (leads due, people awaiting a reply, deadlines), pulled from Calendar and Telegram and ranked. Read-only: sends and commits nothing. Triggers: "/agenda", "what's on today", "my agenda".
中文简介正在准备中。当前显示原文说明。
Rewrite machine-written text so it reads like a busy human wrote it: cut 50-70%, break the even rhythm, drop AI-tell words and filler, keep facts and protected terms. Use before publishing any post, reply or email drafted by a model. Triggers: /ai-slop, /slop, humanize, anti-slop, make it shorter and alive.
中文简介正在准备中。当前显示原文说明。
Decision protocol for strategic work: recall the knowledge vault, run a gap analysis, emit a deep-research prompt for external tools, then synthesize the returned reports into a decision memo. Use before any new product, feature, market, pricing, GTM or architecture call, where local recall alone is not enough. Triggers: "/alfa-search-recall-deepresearch", "alpha protocol", "R+DR".
中文简介正在准备中。当前显示原文说明。
- КРЕДИТ АВТОРУ ИДЕИ: совет из комментария (TG @ClawRus / @ClawInga, комменты под постами Антона в FB, треды и issue на… Триггеры: “/alpha-credit“, “/credit“, “кто нам это посоветовал“, “запиши совет“, “поблагодари советчиков“, “кому мы должны спасибо“, “кредит автору“, “чей это был совет“, “credit the author“
中文简介正在准备中。当前显示原文说明。