Skip to content

docs(skill): prevent missing context in Slack thread investigations #131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dwaxe wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(skill): prevent missing context in Slack thread investigations #131

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions skills/agent-slack/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
10 changes: 10 additions & 0 deletions skills/agent-slack/references/thread-investigation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
Loading