Agent skill · data analytics · microsoft
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting session data.
Why this skill is useful
Provides specific SQL query patterns and workflows for analyzing Copilot session history that the AI wouldn't generate on its own.
What it needs
About 12k tokens when loaded. Last updated 2026-08-07. 188,455 stars on the source repository.
What this skill does
Chronicle Analyze the user's Copilot session history using the copilotsessionStoreSql tool. This skill handles standup reports, usage analysis, session search, and session store maintenance. Sessions may be stored locally (SQLite) and optionally synced to the cloud for cross-device access. Cloud sync is controlled by the chat.sessionSync.enabled setting. Prerequisite: Chronicle requires the github.copilot.chat.localIndex.enabled setting to be true. If the copilotsessionStoreSql tool is not available, tell the user to enable this setting in VS Code Settings. Available Tool Actions The copilotsessionStoreSql tool supports two actions: Action Purpose query param -------- --------- --------------- query Execute a read-only SQL query Required reindex Rebuild local session index + cloud sync Not needed Workflows Standup When the user asks for a standup, daily summary, or "what did I do" (e.g. /chronicle standup): Step 1: Gather the last 24h of activity Use copilotsessionStoreSql with action: "query" and follow the SQL dialect shown in the tool description (SQLite locally, DuckDB on cloud — see the Database Schema and Query Guidelines sections below). Query the sessions table for rows where updatedat falls within the last 24 hours, ordered by updatedat descending. Recent-window predicate by backend: Local SQLite: WHERE updatedat >= datetime('now', '-1 day') Cloud DuckDB: WHERE updatedat >= now() - INTERVAL '1 day' Then, for those session ids, pull related references from sessionrefs (PRs, issues, commits). If you need more detail on a particular session, query turns (and sessionfiles, or checkpoints on cloud) further — don't dump every turn for every session up front. If no sessions are found in the last 24 hours, tell the user there's no recent activity to report, suggest a longer window or /chronicle reindex, and stop. Do not fabricate a standup. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills microsoft/chronicle