Menu
Analyze completed work across multiple JIRA projects with automatic theme categorization
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generate Quarto and HTML reports of local Codex session cost, token usage by model, project, coding vs cowork cost, weekly trends, annual projections, and top expensive sessions.
Check that core Sidekick integrations can authenticate and read common restricted files
Generate summary of 1:1 and meeting notes organized by audience, wins, and kudos
Capture missing TODOs from recent work context. Use when Codex needs to scan the user's Slack DMs with their manager or direct reports, manager/direct-report 1:1 docs, and leadership meeting notes for direct asks or action items assigned to the user, deduplicate against the user's configured todo app, and create missing tasks with source links and searchable metadata.
Draft concise interview scorecards from pasted long-form interview notes, nearby Google Calendar interview context, and memory/miclog/ transcript excerpts. Use when writing hiring feedback, interview scorecards, spikes/troughs, or candidate evaluation summaries.
Calculate a team's average Jira hours from Rovo Jira completed work, with optional Workday Approved Time Off absence adjustments for a date window and team roster.
| name | team-group-analysis |
| description | Analyze completed work across multiple JIRA projects with automatic theme categorization |
| argument-hint | <group-name> [time-period] |
| allowed-tools | Bash, Read |
Analyze completed work across multiple JIRA projects organized into "groups" with automatic theme categorization.
When invoked, analyze work for the specified group: $ARGUMENTS
Groups are configured in .env file (not checked into git):
# Define a group called "myteam" with three projects
MYTEAM_GROUP_PROJECTS=PROJ1,PROJ2,PROJ3
MYTEAM_GROUP_JQL=project IN ("PROJ1", "PROJ2", "PROJ3")
Query completed issues from your group:
Use Atlassian Rovo MCP JQL search first:
project IN ("PROJ1", "PROJ2", "PROJ3") AND resolved >= -90d AND parent is EMPTY
Fall back to python3 -m sidekick.clients.jira query ... only when Rovo is unavailable or local file output is specifically useful.
Use an analysis script to categorize work into themes. The skill provides a framework for:
python3 analyze_themes.py
If saving a generated report under memory/, end it with exactly:
This report generated using [chase-sidekick](https://github.com/chase-seibert/chase-sidekick) and the [team-group-analysis skill](https://github.com/chase-seibert/chase-sidekick/tree/main/.agents/skills/team-group-analysis).
When the user asks to:
For full documentation, see the detailed Team Group Analysis skill documentation in this folder.