Try /insights in Claude Code: it reads the seams in your system

Quick one for anyone running Claude Code on knowledge work rather than code.

There's a built-in command, /insights, that reads your last X sessions and produces a report on how you're actually using it. Mine just landed and it's worth sharing.

What it gives you:

The areas you spend most time in (mine: client emails, quoting, workspace reorgs, daily inbox rhythm, strategic research)
Your interaction style, with one sentence that nails the pattern
Where Claude misfired and why (mine: filling gaps with plausible guesses instead of verifying, pulling from the wrong source file, output formatting that won't paste cleanly into Outlook)
Specific CLAUDE.md additions to stop the same friction recurring
Features to try (Skills, Hooks, MCP servers) tied to your actual usage, not generic advice
"On the horizon" workflows you could build given your patterns

For me it surfaced that my three-way workspace split was working, but my email-drafting conventions weren't documented anywhere Claude could see. For someone running a coaching practice it might surface that client-note structure is fine but session-prep is repeatedly being rebuilt from scratch. For a researcher it might flag that source-citation conventions are missing. For an agency, that brief-to-deck handoffs keep needing the same corrections. It reads the seams in your system, whatever that system is.

That's exactly the gap ICM is meant to close, and /insights makes it visible.

Takes a minute to run. Just type /insights. Worth dropping a screenshot of your "At a Glance" section in the comments if you give it a go, would be interesting to see the patterns across the group. 🙏

5 comments