What is describe-colleague?

A colleague-profile workflow that combines a person's Slack conversations and GitHub activity into a written summary of strengths, weaknesses, interests, and avoidances.

Use it to research a colleague's commits, pull requests, and team messages, then save a structured profile for later reference.

It turns scattered work activity into one profile while requiring the relevant accounts and notes to be available.

describe-colleague — Skill for Claude Code by tomzx/agents

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add tomzx/agents --skill describe-colleague

Clone the repo

git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/describe-colleague/github.svg)](https://agentmods.dev/skills/tomzx/agents/describe-colleague)

Your own site

<a href="https://agentmods.dev/skills/tomzx/agents/describe-colleague"><img src="https://agentmods.dev/badge/skills/tomzx/agents/describe-colleague/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tomzx/agents/describe-colleague"><img src="https://agentmods.dev/badge/skills/tomzx/agents/describe-colleague.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 573 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.00573
Opus 5.5	$0.00013	$0.00229
Sonnet 5.5	$0.00007	$0.00115
Haiku 4.5	$0.00003	$0.00057

Measured 22d ago against content hash f6aade769de3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

describe-colleague scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 22d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/describe-colleague/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

BASE_DIR=!~/.agents/scripts/get-env NOTES_DIR

Describe Colleague

Generates a structured profile for a colleague by synthesizing their Slack and GitHub activity, capturing strengths, weaknesses, interests, and avoidances.

Prerequisites

Slack MCP server connected and authenticated
gh CLI authenticated
NOTES_DIR environment variable set (resolved via ~/.agents/scripts/get-env NOTES_DIR)
Colleague identifier ({COLLEAGUE}) provided as argument or from context

Steps

Retrieve NOTES_DIR from environment:
```
~/.agents/scripts/get-env NOTES_DIR
```

Search GitHub for the colleague's contributions using gh:

gh search commits --author={COLLEAGUE} --limit 50
gh search prs --author={COLLEAGUE} --limit 50

Review their Slack messages and threads via the Slack MCP server. Do not read local files.
Synthesize observations into the profile format below.
Write the profile to {BASE_DIR}/colleagues/{COLLEAGUE}.md.

Output Format

# Strengths

- <strength>

# Weaknesses

- <weakness>

# Interests

- <topic>

# Avoids

- <topic>

# Other relevant information

- <item>

Example Usage

Scenario 1: Profile a specific colleague

/describe-colleague alice

Searches GitHub for alice's commits and PRs, reviews her Slack messages, then writes a profile to {NOTES_DIR}/colleagues/alice.md.

Scenario 2: Update an existing profile

/describe-colleague bob

If {NOTES_DIR}/colleagues/bob.md already exists, overwrite it with a refreshed profile incorporating recent activity.

Scenario 3: Colleague with limited GitHub activity

/describe-colleague carol

Carol's contributions are primarily via Slack. Profile is weighted toward Slack observations, with a note that GitHub data is sparse.

Useful Commands Reference

Command	Description
`~/.agents/scripts/get-env NOTES_DIR`	Resolve the notes directory path
`gh search commits --author=<user> --limit 50`	Fetch recent commits by a user
`gh search prs --author=<user> --limit 50`	Fetch recent PRs authored by a user

Read the full file on GitHub · 88 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

22d ago Changed · +2 lines f6aade769de3
1mo ago First seen · 86 lines · 33 tokens per session scan A faddf989743a

Subscribe to this mod's changes

describe-colleague is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 573 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Project management Research

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens