Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jezweb/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'.
Passed 14 of 21 test cases with the skill, and 10 of 21 without it.
and 3 more in the full report
6 fixed10 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
During capability discovery on local environment tools, what specific local directory path should be checked to detect Basalt Cortex knowledge notes availability?
| Checked | Without skill | With skill |
|---|---|---|
| Checks the path `~/Documents/basalt-cortex/` | Missed | Passed |
The instructions your model reads when the skill loads.
Post project updates to team chat, read and triage feedback, and plan next steps. Adapts to whatever communication and project tools are available.
This skill uses a playbook file at .claude/team-update-playbook.md in the project root.
The playbook is plain markdown the user can edit. It captures tool configuration, channel preferences, message style, triage rules, and last-run metadata.
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.
Detect available capabilities by checking what MCP tools are connected and what local tools exist.
Read references/discovery-patterns.md for detection patterns.
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 |
test cases passed, vs 10 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.