activity

Activity Tracker Skill

Use this skill when the user types /activity or asks about their Claude Code usage, coding stats, session summaries, or productivity metrics.

Instructions

Step 1 — Fetch today's stats

Call the activity_stats MCP tool (server: activity-tracker):

tool: activity_stats
arguments: {}

This returns a JSON object with:

• date — today's date
• session_count — number of sessions started
• total_duration_minutes — total active time
• tool_calls — total MCP/tool invocations
• files_edited — number of unique files touched
• top_files — list of {path, edits} objects (up to 10)
• top_tools — list of {tool, calls} objects (up to 10)

Step 2 — Format the output

Present results as a clean markdown summary. Use the template below, substituting real values:

## 📊 Today's Activity — {date}

| Metric | Value |
|--------|-------|
| Sessions | {session_count} |
| Active time | {total_duration_minutes} min |
| Tool calls | {tool_calls} |
| Files edited | {files_edited} |

### 🔧 Top Tools
| Tool | Calls |
|------|-------|
| {tool} | {calls} |
... (repeat for each entry)

### 📁 Top Files
| File | Edits |
|------|-------|
| {path} | {edits} |
... (repeat for each entry)

Shorten file paths to the last 2-3 path segments for readability (e.g. src/server.py instead of /home/user/projects/foo/src/server.py).

Step 3 — Offer weekly view (optional)

After showing today's stats, offer: "Type /activity week for a 7-day report."

If the user asked for weekly stats (e.g. said "weekly", "this week", "7 days"), call activity_report instead:

tool: activity_report
arguments: { "days": 7 }

Format the weekly report similarly, but add a daily breakdown table:

### 📅 Daily Breakdown
| Date | Sessions | Duration | Tools |
|------|----------|----------|-------|
| {date} | {sessions} | {minutes} min | {tools} |

Step 4 — Insight (optional, 1 sentence)

If any single tool accounts for more than 40% of calls, note it: "You relied heavily on {tool} today — it accounted for {pct}% of all tool calls."