Team Update
Install this when the agent should discover chat and issue MCP tools, then draft and send a concise team status update with sensible fallbacks.
Overview
team-update is an agent skill most often used in Build (also Ship, Grow) that discovers MCP chat and issue capabilities and formats team status updates with git-aware fallbacks.
Install
npx skills add https://github.com/jezweb/claude-skills --skill team-updateWhat is this skill?
- First-run discovery maps MCP tools by `mcp__<server>__<tool>` naming patterns
- Chat coverage table for Google Chat, Slack, Discord, and Microsoft Teams threading behavior
- Git availability via `git rev-parse --is-inside-work-tree` plus optional remote origin capture
- Issue tracker patterns for GitHub, Linear, Jira, and ERPNext MCP surfaces
- Copy-paste formatted text fallback when no chat MCP is connected
- 4 chat platform pattern families in discovery table
- 4 issue tracker MCP pattern families listed
Adoption & trust: 694 installs on skills.sh; 841 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want the agent to post a team update but you are not sure which MCP chat or issue tools exist in this session.
Who is it for?
Solo builders running agents with heterogeneous MCP setups who need reliable standup or progress posts without hard-coding one vendor.
Skip if: Teams without any chat or issue MCP and no appetite for copy-paste fallback text, or orgs that require a fixed corporate comms template this skill does not define.
When should I use this skill?
User asks for a team update, standup post, or status message and MCP chat/issue tooling may be present in the session.
What do I get? / Deliverables
The agent catalogs available messaging and issue MCP tools, pulls git context when present, and sends or outputs a polished update using the best available channel.
- Capability discovery summary of chat and issue MCP tools
- Formatted team update message sent or ready to paste
- Captured repo name or remote hint when git is available
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build pm is the canonical shelf because the skill centers on communicating progress during active development, not on marketing or production incident response alone. Pm fits standups, sprint notes, and stakeholder pings that tie git activity to issue trackers and team channels.
Where it fits
Run discovery for Linear and Slack MCP, then summarize merged PR themes for a daily standup.
Post a release-ready changelog snippet to Google Chat after detecting `mcp__*google-chat*` tools.
Broadcast a support queue snapshot from ERPNext or GitHub issues when chat MCP is available.
How it compares
MCP discovery plus update drafting skill, not a hosted notification SaaS or pager-duty runbook.
Common Questions / FAQ
Who is team-update for?
Indie developers and small teams using Claude-style agents with optional Slack, Teams, Google Chat, GitHub, Linear, or Jira MCP integrations.
When should I use team-update?
During Build pm for daily standups; during Ship launch prep for release notes to the team; during Grow support when syncing customer-impacting progress to internal channels.
Is team-update safe to install?
It may trigger git shell checks and MCP tools that post messages; review the Security Audits panel on this Prism page and limit MCP servers you trust.
SKILL.md
READMESKILL.md - Team Update
# Discovery Patterns How to detect available MCP tools by capability category during first-run discovery. ## Detection Strategy List all available MCP tools by checking what's loaded in the current session. MCP tool names follow the pattern `mcp__<server>__<tool>`. Match tool names against these patterns to categorise capabilities. ## Chat Tools Look for tools that can send and read messages in team channels. | Pattern | Server | Notes | |---|---|---| | `mcp__*google-chat*__chat_messages` | Google Chat | Supports spaces, threads, cards | | `mcp__*slack*__*message*` | Slack | Channels, threads, blocks | | `mcp__*discord*__*message*` | Discord | Channels, threads | | `mcp__*teams*__*message*` | Microsoft Teams | Channels, threads, cards | **What to capture**: The exact tool name, which server it belongs to, and whether it supports threading. **Fallback**: If no chat tools are found, the skill outputs formatted text for the user to copy-paste into their preferred channel. ## Git Not an MCP tool. Detect with: ```bash git rev-parse --is-inside-work-tree 2>/dev/null ``` If true, git is available. Capture the repo name from the directory or `git remote get-url origin`. ## Issue Trackers | Pattern | Server | Notes | |---|---|---| | `mcp__*github*__github_issues` | GitHub | Issues and PRs, labels | | `mcp__*linear*__*issue*` | Linear | Issues, projects, labels | | `mcp__*jira*__*issue*` | Jira | Issues, projects | | `mcp__*erpnext*__erpnext_issues` | ERPNext | Issues with client scoping | **What to capture**: Tool name, whether it supports creating issues, available label schemes. ## Task Trackers | Pattern | Server | Notes | |---|---|---| | `mcp__*asana*__*task*` | Asana | Tasks, projects | | `mcp__*linear*__*issue*` | Linear | Also serves as task tracker | | `mcp__*todoist*__*task*` | Todoist | Tasks, projects | | `mcp__*tuesday*__*task*` | Tuesday | Workspaces, boards, items | ## Knowledge | Source | Location | Notes | |---|---|---| | Basalt Cortex | `~/Documents/basalt-cortex/` | Clients, contacts, knowledge — grep to search | **What to capture**: Whether Basalt Cortex vault exists and has relevant data. ## Discovery Output After detection, present a summary to the user: ``` ## Discovered Capabilities - Chat: Google Chat (via google-chat-anthro) - Git: Yes (jezweb/my-project on branch main) - Issues: GitHub (via github MCP) - Tasks: Brain (via brain MCP) - Knowledge: Vault (via vault MCP) Missing: - (none — all capabilities available) Which chat space should I post updates to? ``` If multiple options exist for a category (e.g. two chat servers), ask the user which one to use. ## Re-Discovery If a tool becomes unavailable after the playbook was saved (MCP server disconnected), the skill should: 1. Note the missing tool in its output 2. Fall back gracefully (skip that data source, or output text instead of posting) 3. Suggest updating the playbook if the change is permanent # Feedback Triage How to classify and act on team responses to project updates. ## Classification Table | Signal | Classification | Default Action | |---|---|---| | Reports a bug, error, or broken behaviour | **Bug report** | Create issue (label: `bug`) | | Suggests a new feature or improvement | **Feature request** | Create issue (label: `enhancement`) | | Asks a question about how something works | **Question** | Draft reply for user approval | | Reports something blocking their work | **Blocker** | Flag immediately, present to user | | Positive feedback, thumbs up, "looks good" | **Acknowledgement** | Note, no action | | Unrelated to the project update | **Off-topic** | Ignore | | Requests a change to existing behaviour | **Change request** | Create issue (label: `enhancement`) | | Reports a security concern | **Security** | Flag immediately, do NOT create public issue | ## Signal Detection ### Bug Reports Look for language indicating something is broken or not working: - "X is broken", "X doesn't work", "X crashes" - "I'm