cloudflare-api
Hit the Cloudflare REST API directly for operations that wrangler and MCP can't handle well. Bulk DNS, custom hostnames, email…
@jezwebInstall SkillDevelopment
Skill
/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',
Claude Code
$ npx -y skills add jezweb/claude-skills --skill team-update --agent claude-code
Codex
$ npx skills add jezweb/claude-skills --skill team-update -a codex -y
Cursor
$ npx skills add jezweb/claude-skills --skill team-update -a cursor -y
Gemini CLI
$ npx skills add jezweb/claude-skills --skill team-update -a gemini-cli -y
GitHub Copilot
$ npx skills add jezweb/claude-skills --skill team-update -a github-copilot -y
OpenCode
$ npx skills add jezweb/claude-skills --skill team-update -a opencode -y
Windsurf
$ npx skills add jezweb/claude-skills --skill team-update -a windsurf -y
SKILL.md
team-update.SKILL.mdname: team-update
description: "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'."
compatibility: claude-code-only
allowed-tools: "*"
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/discovery-patterns.md) for detection patterns.
Capability Detection
Check for each capability category:
| Capability | How to detect | Fallback if missing | |---|---|---| | **Chat** | MCP tools matching `chat`, `slack`, `discord`, `teams` | Output formatted text for manual posting | | **Git** | `git rev-parse --is-inside-work-tree` | Skip commit summaries | | **Issues** | MCP tools matching `github`, `linear`, `jira` | Skip or output text list | | **Tasks** | MCP tools matching `tasks`, `todos`, `asana` | Skip or output text list | | **Knowledge** | Basalt Cortex (`~/Documents/basalt-cortex/`) | Search for related knowledge notes |
User Preferences (Ask)
After discovery, ask the user to confirm:
1. **Channel**: Which chat space/channel to post updates to? (List discovered options) 2. **Identity**: Post as yourself or a bot identity? (e.g. Anthro Morphic) 3. **Repo scope**: Which repo(s) to track? (Default: current repo) 4. **Message style**: Brief standup, detailed changelog, or conversational update? 5. **Team context**: Any team members to be aware of? (Names, roles) 6. **Triage rules**: Any custom rules for handling feedback? (Or use defaults)
Save Playbook
After discovery + user preferences, save the playbook to `.claude/team-update-playbook.md`.
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.
Ensure `.claude/` is in `.gitignore` (the playbook contains space IDs and preferences that shouldn't be committed).
---
Phase 1: Gather Context
Collect information from all available sources. Use the playbook's "Data Sources" section to know which tools to call.
1a. Determine Time Window
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).
1b. Collect Data
Gather from each available source:
| Source | What to collect | Tool | |---|---|---| | **Git commits** | `git log --oneline --since=<last-update>` | Bash | | **Chat messages** | Messages in the configured channel since last update | Chat MCP tool from playbook | | **Open issues/PRs** | Recently updated or newly created items | Issue tracker from playbook | | **Active tasks** | In-progress or recently completed tasks | Task tracker from playbook |
1c. Summarise for Drafting
Group commits by theme (not individual hashes). Note any issues closed, PRs merged, or tasks completed. Flag any team messages that need response.
---
Phase 2: Draft and Post Update
2a. Compose Message
Read [references/message-composition.md](references/message-composition.md) for message patterns.
Follow the playbook's "Message Style" section. General principles:
- Lead with what shipped or changed, not process
- Group related commits into themes
- Mention specific people only when relevant
- Keep it scannable (short paragraphs, bullet points)
- **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).
2b. Preview and Approval
Show the draft to the user. Include:
- The composed message
- Which channel it will be posted to
- Whether it's a new message or thread reply
**APPROVAL REQUIRED**: Never post to external channels without explicit user approval.
2c. Post
Post the approved message using the chat tool from the playbook. If no chat tool is available, output the formatted message for the user to post manually.
2d. Update Playbook
After posting, update the "Last Run" section of the playbook with:
- Current timestamp
- Thread key (if applicable)
- Brief summary of what was posted
---
Phase 3: Read and Triage Feedback
3a. Read Responses
Read messages from the configured channel since the update was posted. Look for:
- Direct replies to the update
- New messages in the channel that reference the project
- Reactions or acknowledgements
3b. Classify Feedback
Read [references/feedback-triage.md](references/feedback-triage.md) for classification patterns.
Use the playbook's "Triage Rules" se
Read more
name: team-update description: "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'." compatibility: claude-code-only allowed-tools: "*"
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/discovery-patterns.md) for detection patterns.
Capability Detection
Check for each capability category:
| Capability | How to detect | Fallback if missing | |---|---|---| | **Chat** | MCP tools matching `chat`, `slack`, `discord`, `teams` | Output formatted text for manual posting | | **Git** | `git rev-parse --is-inside-work-tree` | Skip commit summaries | | **Issues** | MCP tools matching `github`, `linear`, `jira` | Skip or output text list | | **Tasks** | MCP tools matching `tasks`, `todos`, `asana` | Skip or output text list | | **Knowledge** | Basalt Cortex (`~/Documents/basalt-cortex/`) | Search for related knowledge notes |
User Preferences (Ask)
After discovery, ask the user to confirm:
1. **Channel**: Which chat space/channel to post updates to? (List discovered options) 2. **Identity**: Post as yourself or a bot identity? (e.g. Anthro Morphic) 3. **Repo scope**: Which repo(s) to track? (Default: current repo) 4. **Message style**: Brief standup, detailed changelog, or conversational update? 5. **Team context**: Any team members to be aware of? (Names, roles) 6. **Triage rules**: Any custom rules for handling feedback? (Or use defaults)
Save Playbook
After discovery + user preferences, save the playbook to `.claude/team-update-playbook.md`.
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.
Ensure `.claude/` is in `.gitignore` (the playbook contains space IDs and preferences that shouldn't be committed).
---
Phase 1: Gather Context
Collect information from all available sources. Use the playbook's "Data Sources" section to know which tools to call.
1a. Determine Time Window
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).
1b. Collect Data
Gather from each available source:
| Source | What to collect | Tool | |---|---|---| | **Git commits** | `git log --oneline --since=<last-update>` | Bash | | **Chat messages** | Messages in the configured channel since last update | Chat MCP tool from playbook | | **Open issues/PRs** | Recently updated or newly created items | Issue tracker from playbook | | **Active tasks** | In-progress or recently completed tasks | Task tracker from playbook |
1c. Summarise for Drafting
Group commits by theme (not individual hashes). Note any issues closed, PRs merged, or tasks completed. Flag any team messages that need response.
---
Phase 2: Draft and Post Update
2a. Compose Message
Read [references/message-composition.md](references/message-composition.md) for message patterns.
Follow the playbook's "Message Style" section. General principles:
- Lead with what shipped or changed, not process
- Group related commits into themes
- Mention specific people only when relevant
- Keep it scannable (short paragraphs, bullet points)
- **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).
2b. Preview and Approval
Show the draft to the user. Include:
- The composed message
- Which channel it will be posted to
- Whether it's a new message or thread reply
**APPROVAL REQUIRED**: Never post to external channels without explicit user approval.
2c. Post
Post the approved message using the chat tool from the playbook. If no chat tool is available, output the formatted message for the user to post manually.
2d. Update Playbook
After posting, update the "Last Run" section of the playbook with:
- Current timestamp
- Thread key (if applicable)
- Brief summary of what was posted
---
Phase 3: Read and Triage Feedback
3a. Read Responses
Read messages from the configured channel since the update was posted. Look for:
- Direct replies to the update
- New messages in the channel that reference the project
- Reactions or acknowledgements
3b. Classify Feedback
Read [references/feedback-triage.md](references/feedback-triage.md) for classification patterns.
Use the playbook's "Triage Rules" se
Stats
1,107
Stars
110
Forks
Maintained
Maintenance
Python
Language
MIT
License
Last commit
Created
Ships withjezweb-skills
Production workflow skills for Claude Code. Each skill guides Claude through a recipe to produce tangible output — scaffolded projects, generated assets, professional documents, deployed services. Ten plugins of practical, production-oriented skills.
1.1k63 skills
Stars on GitHub
Momentum
- stars in total
- 1.1k
Other skills on jezweb-skills.
@jezwebInstall Skillcloudflare-worker-buil…
Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure,…
@jezwebInstall Skilld1-drizzle-schema
Generate Drizzle ORM schemas for Cloudflare D1 databases with correct D1-specific patterns. Produces schema files, migration…
@jezwebInstall Skilld1-migration
Cloudflare D1 migration workflow: generate with Drizzle, inspect SQL for gotchas, apply to local and remote, fix stuck…
@jezwebInstall Skilldb-seed
Generate database seed scripts with realistic sample data. Reads Drizzle schemas or SQL migrations, respects foreign key…
@jezwebInstall Skillhono-api-scaffolder
Scaffold Hono API routes for Cloudflare Workers. Produces route files, middleware, typed bindings, Zod validation, error…
@jezwebInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about team-update.
- Which coding agents can use team-update?
- team-update installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.