collect-team-activity

Cross-tool activity reporting aggregates a member's work evidence from Slack, Jira, Confluence, and GitHub into a structured timeline. It organizes findings into status, summary, activity, and gaps for leadership oversight without manual hunting.

Yes, you can track a direct report's Jira and Slack activity for 1:1 prep. The skill organizes their work evidence into status, summary, activity, and gaps, providing a structured timeline with source links for leadership review.

Team activity reporting handles timezone-aware date boundaries by using the member's local timezone. This ensures single-day or date-range scoping remains accurate for remote teams across different regions.

To gather cross-tool work evidence from Slack and Atlassian, you need workspace roster files and MCP access. Optional GitHub integration requires gh CLI access to collect commits alongside messages, tickets, and pages.

Yes, you can include private-channel context when collecting Slack activity. The skill supports accessing private-channel context alongside Jira, Confluence, and GitHub evidence to provide comprehensive cross-tool session evidence.

Limitations of timezone-aware activity reporting include requiring workspace roster files and MCP access to Slack and Atlassian. GitHub integration is optional, and the structured output depends on accessible sources within the member's workspace.