Get Better at Claude Code with One Simple Command
Por Miguel Torrez, fundador de Genial Agency
You will run Claude Code's built-in /insights command, open the report it builds from your recent sessions, and use its suggestions to improve your CLAUDE.md, skills and connected tools.
Lo que necesitas
Claude Code (desktop app, terminal or extension)
A few days of real Claude Code sessions for it to analyze
Paso a paso
Open Claude Code where you usually work
Open Claude Code in the desktop app, the terminal or the extension. The command works in all three. Nothing to install: it comes built in.
Run the insights command
Type /insights and send it. Claude Code analyzes your chat sessions from the last three days and builds a report of actionable changes.
Command/insights
Wait for the report
Give it a few seconds to a few minutes. The time depends on how much you use Claude Code and the reasoning level of your model (on Opus high, mine took about a minute).
Ask Claude to open the report
When it finishes, simply ask Claude Code to open the report so you can look through it.
Read the At a Glance section
Start with At a Glance: how you currently work with Claude Code, what's working, what's hindering you, quick wins, and the most ambitious workflows (those are for later).
Check the specific problems it found
Click into the sections that interest you. Look for recurring issues, like errors in scripts, answers from memory that were not verified, or workflows hitting limits.
Apply the CLAUDE.md suggestions
Open CLAUDE.md suggestions. Copy the lines into your CLAUDE.md by hand, or ask Claude Code to read the whole report with you and make the changes one by one.
Review suggested skills and MCP servers
Look at the custom skills it proposes and the MCP servers it recommends for software you already use (for me, Notion). Note the future use cases for later.
Repeat once a week
Run /insights about once a week so there is enough data to act on. Daily runs only make sense if you are a new beginner who wants guardrails.
Ten cuidado con
Running it every day: with only a day of sessions there is not much in the report to act on.
Trying to get your setup right in one go: CLAUDE.md, hooks, custom commands and skills are hard to nail the first time, so fix things gradually from each report.
Jumping to the ambitious workflows first: those are for the coming months, so start with the quick wins and the problems it found.
