extract-colleague-decisions SKILL.md skillA
extract-colleague-decisions from tomzx/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tomzx/agents/extract-colleague-decisions@git:20261007.b35fc4bPins git:20261007.b35fc4b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tomzx/agents
- Path
skills/extract-colleague-decisions/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261007.b35fc4b, committed Oct 7, 2026
- First version recorded
- Sep 19, 2026
- Size
- 18,196 bytes
- Repository stars
- 12
- License
- MIT
Search Slack for messages a set of colleagues authored on a given day, read the full threads behind them, and extract the decisions each of them made plus who supported them, filtering out the chatter and citing permalinks. Use this to catch up on what changed across a team without reading every thread, or when asked "what decisions were made today", "what did <people> decide", "what did my colleagues decide yesterday", or to build a daily decisions digest. Reads the colleague list from the…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Colleague Decisions
Answers a recurring question: *"What did my colleagues actually decide today?"* A day of Slack produces many messages, most of them chatter, acknowledgements, and questions, with a handful of real decisions inside.
This skill searches Slack for each colleague's authored messages in a day, then reads them and pulls out the decisions, so you can catch up on what changed without reading every thread.
The judgement is the point: telling a decision from chatter is a reading task, not a keyword match.
`slackx conversations search` only gets the messages in front of you; you decide what counts.
## Prerequisites
- `SLACK_TOKEN` (and `SLACK_COOKIE` for xoxc/web tokens) in `.env`, found by searching up from the working directory.
Source it before invoking `slackx`.
- `COLLEAGUES` in `.env`: a comma-separated list of Slack usernames (e.g. `alice.smith,bob.jones`).
Resolve it with `~/.agents/scripts/get-env COLLEAGUES`.
- `slackx` on PATH; install if missing:
```bash
if ! command -v slackx &>/dev/null; then
git clone https://github.com/TomzxCode/slackx /tmp/slackx
uv tool install /tmp/slackx
fi
```
- `jq` for filtering the search JSON.
…Read the whole file at its exact version.
How to install
mdr add tomzx/agents/extract-colleague-decisions@sha256:f8002f5b9ed9cc3eThe line at the top of this page pins the label git:20261007.b35fc4b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lyhfzl3sj3vjsjcu)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 19, 2026 and Oct 7, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.b35fc4b latest | 2026-10-07 | b35fc4b | 18,196 B | A | view · diff |
| git:20261004.00bb0c5 | 2026-10-04 | 00bb0c5 | 18,215 B | A | view · diff |
| git:20260930.f079d9c | 2026-09-30 | f079d9c | 18,222 B | A | view · diff |
| git:20260929.30f58fc | 2026-09-29 | 30f58fc | 17,879 B | A | view · diff |
| git:20260919.efeebba | 2026-09-19 | efeebba | 15,707 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (18196 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tomzx/agents · 12 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lyhfzl3sj3vjsjcu GET https://markdownregistry.com/api/v1/resolve?ref=tomzx/agents/extract-colleague-decisions GET https://markdownregistry.com/api/v1/blob/f8002f5b9ed9cc3e91d3476cd0e85ea3e144e18889506147a6e0cda5be91ff15
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.