Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From sessions
Generate a comprehensive summary of AI coding sessions from the past week. Use when the user says "weekly summary", "what did I do this week", "summarize my week", "weekly recap", "week in review", or asks for a summary of recent work across projects.
npx claudepluginhub nicknisi/sessions --plugin sessionsHow this skill is triggered — by the user, by Claude, or both
Slash command
/sessions:weekly-summaryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a weekly summary of the user's AI coding sessions.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Guides systematic root-cause debugging when tests fail, builds break, or unexpected errors occur. Provides a structured triage checklist to preserve evidence, localize, and fix issues instead of guessing.
Share bugs, ideas, or general feedback.
Generate a weekly summary of the user's AI coding sessions.
Get the date range. Calculate the start date (7 days ago) and end date (today) in YYYY-MM-DD format.
Fetch the digest. Call get_activity_digest with:
startDate: 7 days agoendDate: todaydetail: "highlights" (first + last user messages for substantive sessions)Review the digest. Read the response directly — do NOT send it to a subagent. The highlights mode is compact enough to process inline. For each day, identify:
Drill into key sessions (optional). If any sessions look particularly significant (high message count, interesting topic) but the highlights don't capture enough detail, call get_session_messages on those specific sessions (up to 5) using the filePath from the digest.
Write the summary. Structure it as:
By the numbers: {total sessions} sessions, {total messages} messages across {project count} projects.
Day-by-day: For each day with activity, write 2-4 bullet points capturing the most significant work. Be specific — name projects, features, and outcomes. Skip days with no meaningful activity.
Highlights: The 3-5 most significant accomplishments across the entire week.
Themes: Recurring work streams or focus areas (e.g., "SDK development", "infrastructure", "bug fixes").