From 1f9ddb122c56ec14957897767573998c849c056c Mon Sep 17 00:00:00 2001 From: Darwin Wu Date: Thu, 23 Jul 2026 18:52:10 -0700 Subject: [PATCH] docs(skill): guide Slack thread investigations Agents working from a Slack link can miss later replies, repeat stale claims, or search beyond the user's intended scope. Add a short reference that requires reading the full thread, limits follow-up searches, verifies changing facts at their source, respects privacy boundaries, and rereads the thread before replying. --- skills/agent-slack/SKILL.md | 1 + skills/agent-slack/references/thread-investigation.md | 10 ++++++++++ 2 files changed, 11 insertions(+) create mode 100644 skills/agent-slack/references/thread-investigation.md diff --git a/skills/agent-slack/SKILL.md b/skills/agent-slack/SKILL.md index 7512344..029befb 100644 --- a/skills/agent-slack/SKILL.md +++ b/skills/agent-slack/SKILL.md @@ -41,5 +41,6 @@ Slack-native drafts (`message draft list|create|update|delete`) manage drafts th ## Conditional references +- Read [references/thread-investigation.md](references/thread-investigation.md) only when interpreting a Slack thread, verifying its claims, advising an action from it, or preparing a reply to that thread. - Read [references/targets.md](references/targets.md) only when choosing between a message URL, channel, or user target, or when resolving multiple workspaces. - Read [references/output.md](references/output.md) only when handling returned message or canvas metadata, resolved users, or downloaded and failed attachments. diff --git a/skills/agent-slack/references/thread-investigation.md b/skills/agent-slack/references/thread-investigation.md new file mode 100644 index 0000000..8bee091 --- /dev/null +++ b/skills/agent-slack/references/thread-investigation.md @@ -0,0 +1,10 @@ +# Thread investigation + +- Anchor to the exact message permalink and workspace. Read the root and every reply, note later corrections, and reread the thread before an authorized reply. +- Follow only attachments, canvases, and linked material needed to answer the focal question. +- Search only to fill a specific gap, bounded to the anchored workspace and, where useful, by channel, participant, and date range. +- Treat mutable Slack claims as leads. Verify decision-relevant claims in their current authoritative source when available, prefer current state, and surface material conflicts or uncertainty. +- Keep proposed, approved, merged, built, deployed, and completed states distinct. +- Do not infer through inaccessible content or failed downloads. +- Keep evidence in the anchored workspace unless cross-workspace work is explicit; do not broaden DM/private-channel evidence without authorization; minimize sensitive detail. +- If new activity changes or answers the question, stop and revise rather than send a stale or duplicate reply.