team-collaboration-standup-notes
Automates the creation of daily standup notes by aggregating data from Git, Jira, and documentation for efficient async team coordination.
Install
mkdir -p .claude/skills/team-collaboration-standup-notes && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5227" && unzip -o skill.zip -d .claude/skills/team-collaboration-standup-notes && rm skill.zipInstalls to .claude/skills/team-collaboration-standup-notes
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.Key capabilities
- →Generate complete daily standup notes
- →Analyze Obsidian vault context
- →Query Jira tickets
- →Process Git commit history
- →Incorporate calendar events
How it works
The skill analyzes data from Obsidian, Jira, Git commit history, and calendar events to generate daily standup notes, extracting accomplishments and formatting them for team visibility.
Inputs & outputs
When to use team-collaboration-standup-notes
- →Generating daily status updates
- →Summarizing progress from Jira and Git
- →Identifying blockers for async teams
- →Preparing for team sync meetings
About this skill
Standup Notes Generator
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.
Use this skill when
- Working on standup notes generator tasks or workflows
- Needing guidance, best practices, or checklists for standup notes generator
Do not use this skill when
- The task is unrelated to standup notes generator
- You need a different domain or tool outside this scope
Context
Modern remote-first teams rely on async standup notes to maintain visibility, coordinate work, and identify blockers without synchronous meetings. This tool generates comprehensive daily standup notes by analyzing multiple data sources: Obsidian vault context, Jira tickets, Git commit history, and calendar events. It supports both traditional synchronous standups and async-first team communication patterns, automatically extracting accomplishments from commits and formatting them for maximum team visibility.
Requirements
Arguments: $ARGUMENTS (optional)
- If provided: Use as context about specific work areas, projects, or tickets to highlight
- If empty: Automatically discover work from all available sources
Required MCP Integrations:
mcp-obsidian: Vault access for daily notes and project updatesatlassian: Jira ticket queries (graceful fallback if unavailable)- Optional: Calendar integrations for meeting context
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Resources
resources/implementation-playbook.mdfor detailed patterns and examples.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Prerequisites
How it compares
This skill automatically generates standup notes from multiple data sources, unlike manually compiling updates from various platforms.
Compared to similar skills
team-collaboration-standup-notes side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| team-collaboration-standup-notes (this skill) | 1 | 4mo | No flags | Intermediate |
| notion-meeting-intelligence | 6 | 6mo | No flags | Intermediate |
| gtd | 0 | 6mo | No flags | Intermediate |
| end-session | 0 | 5mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by sickn33
View all by sickn33 →You might also like
notion-meeting-intelligence
openai
Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
gtd
Gerstep
Autonomous task execution from GTD.md items. Use when processing GTD tasks, call prep, outreach, or podcast preparation.
end-session
connorkitchings
Close a development session properly. Create session log, run health checks, update schedule, prepare handoff documentation.
standup
thrawn01
Reconstruct what you actually did over a time window from Claude session logs, GitHub, Linear, and daily notes; group it by Linear ticket; write a standup-ready markdown report to ~/Notes; and copy a Range.co-ready version to the clipboard. Use when the user says 'standup', '/standup', 'what did I d
slack-proactive-intervention-patterns
krafton-ai
메모리에서 7가지 개입 기회 패턴을 감지하는 지식 베이스. 조사 제안, 스케줄링, 문서화, 초안 작성, 연결 조율, 예측적 제안, 루틴 자동화 패턴의 시그널과 점수 계산 방법.
team-communication-protocols
wshobson
Structured messaging protocols for agent team communication including message type selection, plan approval, shutdown procedures, and anti-patterns to avoid. Use this skill when establishing team communication norms, handling plan approvals, or managing team shutdown.