team-update

Name: team-update
Author: jezweb

858installs96forks

How to install team-update?

jezweb/claude-skills/team-update

$npx -y skills add jezweb/claude-skills --skill team-update

Installs into the current project.

Summary

Post project updates to team chat, gather feedback, triage responses, and plan next steps. Adapts to available tools (chat, git, issues, tasks). First run discovers tools and saves a playbook; subsequent runs execute from the playbook. Trigger with 'team update', 'post update', '

Files · 1

View on GitHub

SKILL.md

1	# Team Update
2
3	Post project updates to team chat, read and triage feedback, and plan next steps. Adapts to whatever communication and project tools are available.
4
5	## The Playbook Pattern
6
7	This skill uses a playbook file at `.claude/team-update-playbook.md` in the project root.
8
9	- First run: Discover available tools, ask the user for preferences, execute, save a playbook
10	- Subsequent runs: Read the playbook, skip discovery, execute directly
11	- User edits playbook: Changes take effect immediately (channel, style, triage rules)
12
13	The playbook is plain markdown the user can edit. It captures tool configuration, channel preferences, message style, triage rules, and last-run metadata.
14
15	---
16
17	## Phase 0: Playbook Check
18
19	Check if `.claude/team-update-playbook.md` exists in the project root.
20
21	If it exists: Read it. All tool configuration, channel info, message style, and triage rules are in there. Jump to Phase 1 with known config.
22
23	If it does not exist: Run Phase 0b (Discovery) first.
24
25	---
26
27	## Phase 0b: Discovery (First Run Only)
28
29	Detect available capabilities by checking what MCP tools are connected and what local tools exist.
30
31	Read [references/discovery-patterns.md](references/discovery-patterns.md) for detection patterns.
32
33	### Capability Detection
34
35	Check for each capability category:
36
37	\| Capability \| How to detect \| Fallback if missing \|
38	\|---\|---\|---\|
39	\| Chat \| MCP tools matching `chat`, `slack`, `discord`, `teams` \| Output formatted text for manual posting \|
40	\| Git \| `git rev-parse --is-inside-work-tree` \| Skip commit summaries \|
41	\| Issues \| MCP tools matching `github`, `linear`, `jira` \| Skip or output text list \|
42	\| Tasks \| MCP tools matching `tasks`, `todos`, `asana` \| Skip or output text list \|
43	\| Knowledge \| Basalt Cortex (`~/Documents/basalt-cortex/`) \| Search for related knowledge notes \|
44
45	### User Preferences (Ask)
46
47	After discovery, ask the user to confirm:
48
49	1. Channel: Which chat space/channel to post updates to? (List discovered options)
50	2. Identity: Post as yourself or a bot identity? (e.g. Anthro Morphic)
51	3. Repo scope: Which repo(s) to track? (Default: current repo)
52	4. Message style: Brief standup, detailed changelog, or conversational update?
53	5. Team context: Any team members to be aware of? (Names, roles)
54	6. Triage rules: Any custom rules for handling feedback? (Or use defaults)
55
56	### Save Playbook
57
58	After discovery + user preferences, save the playbook to `.claude/team-update-playbook.md`.
59
60	Read [references/playbook-format.md](references/playbook-format.md) for the full template. Fill in all sections with discovered tools and user preferences. If a capability was not found, note it as "Not available" in the playbook.
61
62	Ensure `.claude/` is in `.gitignore` (the playbook contains space IDs and preferences that shouldn't be committed).
63
64	---
65
66	## Phase 1: Gather Context
67
68	Collect information from all available sources. Use the playbook's "Data Sources" section to know which tools to call.
69
70	### 1a. Determine Time Window
71
72	Check the playbook's "Last Run" section for the last update timestamp. If no previous run, ask the user how far back to go (default: 24 hours).
73
74	### 1b. Collect Data
75
76	Gather from each available source:
77
78	\| Source \| What to collect \| Tool \|
79	\|---\|---\|---\|
80	\| Git commits \| `git log --oneline --since=<last-update>` \| Bash \|
81	\| Chat messages \| Messages in the configured channel since last update \| Chat MCP tool from playbook \|
82	\| Open issues/PRs \| Recently updated or newly created items \| Issue tracker from playbook \|
83	\| Active tasks \| In-progress or recently completed tasks \| Task tracker from playbook \|
84
85	### 1c. Summarise for Drafting
86
87	Group commits by theme (not individual hashes). Note any issues closed, PRs merged, or tasks completed. Flag any team messages that need response.
88
89	---
90
91	## Phase 2: Draft and Post Update
92
93	### 2a. Compose Message
94
95	Read [references/message-composition.md](references/message-composition.md) for message patterns.
96
97	Follow the playbook's "Message Style" section. General principles:
98
99	- Lead with what shipped or changed, not process
100	- Group related commits into themes
101	- Mention specific people only when relevant
102	- Keep it scannable (short paragraphs, bullet points)
103	- Write like a teammate, not an AI — no emoji spam, no hedging, no over-explaining context the team already has. See the Communication Style section in [references/message-composition.md](references/message-composition.md).
104
105	### 2b. Preview and Approval
106
107	Show the

People who liked this also viewed

6 picks

Type

team-update

858installs96forks

View on GitHub

How to install team-update?

jezweb/claude-skills/team-update

$npx -y skills add jezweb/claude-skills --skill team-update

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Team Update
2
3	Post project updates to team chat, read and triage feedback, and plan next steps. Adapts to whatever communication and project tools are available.
4
5	## The Playbook Pattern
6
7	This skill uses a playbook file at `.claude/team-update-playbook.md` in the project root.
8
9	- First run: Discover available tools, ask the user for preferences, execute, save a playbook
10	- Subsequent runs: Read the playbook, skip discovery, execute directly
11	- User edits playbook: Changes take effect immediately (channel, style, triage rules)
12
13	The playbook is plain markdown the user can edit. It captures tool configuration, channel preferences, message style, triage rules, and last-run metadata.
14
15	---
16
17	## Phase 0: Playbook Check
18
19	Check if `.claude/team-update-playbook.md` exists in the project root.
20
21	If it exists: Read it. All tool configuration, channel info, message style, and triage rules are in there. Jump to Phase 1 with known config.
22
23	If it does not exist: Run Phase 0b (Discovery) first.
24
25	---
26
27	## Phase 0b: Discovery (First Run Only)
28
29	Detect available capabilities by checking what MCP tools are connected and what local tools exist.
30
31	Read [references/discovery-patterns.md](references/discovery-patterns.md) for detection patterns.
32
33	### Capability Detection
34
35	Check for each capability category:
36
37	\| Capability \| How to detect \| Fallback if missing \|
38	\|---\|---\|---\|
39	\| Chat \| MCP tools matching `chat`, `slack`, `discord`, `teams` \| Output formatted text for manual posting \|
40	\| Git \| `git rev-parse --is-inside-work-tree` \| Skip commit summaries \|
41	\| Issues \| MCP tools matching `github`, `linear`, `jira` \| Skip or output text list \|
42	\| Tasks \| MCP tools matching `tasks`, `todos`, `asana` \| Skip or output text list \|
43	\| Knowledge \| Basalt Cortex (`~/Documents/basalt-cortex/`) \| Search for related knowledge notes \|
44
45	### User Preferences (Ask)
46
47	After discovery, ask the user to confirm:
48
49	1. Channel: Which chat space/channel to post updates to? (List discovered options)
50	2. Identity: Post as yourself or a bot identity? (e.g. Anthro Morphic)
51	3. Repo scope: Which repo(s) to track? (Default: current repo)
52	4. Message style: Brief standup, detailed changelog, or conversational update?
53	5. Team context: Any team members to be aware of? (Names, roles)
54	6. Triage rules: Any custom rules for handling feedback? (Or use defaults)
55
56	### Save Playbook
57
58	After discovery + user preferences, save the playbook to `.claude/team-update-playbook.md`.
59
60	Read [references/playbook-format.md](references/playbook-format.md) for the full template. Fill in all sections with discovered tools and user preferences. If a capability was not found, note it as "Not available" in the playbook.
61
62	Ensure `.claude/` is in `.gitignore` (the playbook contains space IDs and preferences that shouldn't be committed).
63
64	---
65
66	## Phase 1: Gather Context
67
68	Collect information from all available sources. Use the playbook's "Data Sources" section to know which tools to call.
69
70	### 1a. Determine Time Window
71
72	Check the playbook's "Last Run" section for the last update timestamp. If no previous run, ask the user how far back to go (default: 24 hours).
73
74	### 1b. Collect Data
75
76	Gather from each available source:
77
78	\| Source \| What to collect \| Tool \|
79	\|---\|---\|---\|
80	\| Git commits \| `git log --oneline --since=<last-update>` \| Bash \|
81	\| Chat messages \| Messages in the configured channel since last update \| Chat MCP tool from playbook \|
82	\| Open issues/PRs \| Recently updated or newly created items \| Issue tracker from playbook \|
83	\| Active tasks \| In-progress or recently completed tasks \| Task tracker from playbook \|
84
85	### 1c. Summarise for Drafting
86
87	Group commits by theme (not individual hashes). Note any issues closed, PRs merged, or tasks completed. Flag any team messages that need response.
88
89	---
90
91	## Phase 2: Draft and Post Update
92
93	### 2a. Compose Message
94
95	Read [references/message-composition.md](references/message-composition.md) for message patterns.
96
97	Follow the playbook's "Message Style" section. General principles:
98
99	- Lead with what shipped or changed, not process
100	- Group related commits into themes
101	- Mention specific people only when relevant
102	- Keep it scannable (short paragraphs, bullet points)
103	- Write like a teammate, not an AI — no emoji spam, no hedging, no over-explaining context the team already has. See the Communication Style section in [references/message-composition.md](references/message-composition.md).
104
105	### 2b. Preview and Approval
106
107	Show the

People who liked this also viewed

6 picks

Type