team-threads SKILL.md skillA
team-threads from atman-33/workhub is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add atman-33/workhub/team-threads@git:20260912.1a466ffPins git:20260912.1a466ff in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- atman-33/workhub
- Path
plugins/team-comms/skills/team-threads/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260912.1a466ff, committed Sep 12, 2026
- Size
- 1,860 bytes
- Repository stars
- 3
- License
- MIT
Show what is going on in the team's comms space - live threads, their state, and what is unread for you - and help pick one to work in. Use when the user asks what the team is discussing, what they have missed, or which thread to join.
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
# See the team's threads
## Steps
1. **List them:**
```bash
node "${CLAUDE_PLUGIN_ROOT}/scripts/comms.mjs" list
```
Add `--all` to include closed threads. `scan` additionally reports mentions
and any stray files.
2. **Report in the order that matters**, not the order they came back:
threads with unread posts first, then anything you are named in, then the
rest. Give each one line: title, state, unread count, who wrote last.
3. **Say what is worth doing**, with a reason. Usually one of:
- read a thread that has unread posts (`team-catchup`);
- join the discussion the user is actually working on (`team-focus`);
- nothing, because none of it touches today's work — say that plainly
rather than manufacturing a next step.
4. **For a browsable copy**, generate the local HTML list:
```bash
node "${CLAUDE_PLUGIN_ROOT}/scripts/comms.mjs" index
```
It is written under `~/.team-comms/`, and deliberately **not** into the
shared folder: one index file everyone rewrites is exactly the write
conflict the rest of the design removes. Tell the user the path.
5. **To find something specific**, search rather than opening threads one by
…Read the whole file at its exact version.
How to install
mdr add atman-33/workhub/team-threads@sha256:cea4bfab413fe8baThe line at the top of this page pins the label git:20260912.1a466ff, 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_ffefgznvj5srknqn)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 12, 2026.
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 (1860 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
atman-33/workhub · 3 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ffefgznvj5srknqn GET https://markdownregistry.com/api/v1/resolve?ref=atman-33/workhub/team-threads GET https://markdownregistry.com/api/v1/blob/cea4bfab413fe8babfbbbbc372061f4ac6a727fb44d18bef31070069886e1b7a
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.