team-update
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', 'sync with team', 'standup', 'check team chat', 'feedback loop', 'project update', 'what did the team say'.
npx skills add jezweb/claude-skills --skill team-update --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Team Update Post project updates to team chat, read and triage feedback, and plan next steps. Adapts to whatever communication and project tools are available. ## The Playbook Pattern This skill uses a **playbook** file at `.claude/team-update-playbook.md` in the project root. - **First run**: Discover available tools, ask the user for preferences, execute, save a playbook - **Subsequent runs**: Read the playbook, skip discovery, execute directly - **User edits playbook**: Changes take effect immediately (channel, style, triage rules) The playbook is plain markdown the user can edit. It captures tool configuration, channel preferences, message style, triage rules, and last-run metadata. --- ## Phase 0: Playbook Check Check if `.claude/team-update-playbook.md` exists in the project root. **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. **If it does not exist**: Run Phase 0b (Discovery) first. --- ## Phase 0b: Discovery (First Run Only) Detect available capabilities by checking what MCP tools are connected and what local tools exist. Read [references/discovery-patterns.md](references/di
- The Playbook Pattern
- Phase 0: Playbook Check
- Phase 0b: Discovery (First Run Only)
- Capability Detection
- User Preferences (Ask)
- Save Playbook
- Phase 1: Gather Context
- 1a. Determine Time Window
- 1b. Collect Data
- 1c. Summarise for Drafting
- Phase 2: Draft and Post Update
- 2a. Compose Message
- 2b. Preview and Approval
- 2c. Post
What does the team-update skill do?
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', 'sync with team', 'standup', 'check team chat', 'feedback loop', 'project update', 'what did the team say'.
How do I install it?
Run `npx skills add jezweb/claude-skills --skill team-update --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jezweb/claude-skills, a repository with 954 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.