Big Idea

The argument in one line.

/insights reads your own Claude Code session history and generates a private, personalized report on what is slowing you down, making your past usage the raw material for an automated self-improvement loop.

Who This Is For

Read if. Skip if.

READ IF YOU ARE…

You have been using Claude Code for weeks or months and suspect you are underusing it.
You want personalized suggestions based on your actual behavior rather than generic tips.
You use Obsidian or a second-brain system and want Claude Code usage reviews integrated into it automatically.
You are comfortable building custom Claude Code skills and want a real worked example with a 4-step build prompt.

SKIP IF…

You are brand new to Claude Code. /power-up is the right starting point, but /insights needs 30 days of session data to be useful.
You run only occasional one-off sessions. The report is built for power users with enough volume to surface patterns.

TL;DR

The full version, fast.

Two underused slash commands sit inside every Claude Code install: /power-up, which walks you through 10 interactive lessons covering the 80/20 of core features, and /insights, which reads 30 days of your own JSONL session logs and produces a private HTML report card on your actual usage. The report surfaces what works, what slows you down, features you are ignoring, and an On the Horizon section of autonomous workflow ideas written as copy-paste Claude Code prompts. The real leverage is building a /monthly-insights skill that extracts friction points, saves them to an Obsidian vault, and emails a clean digest, then scheduling it with /loop or /schedule so the self-improvement loop runs automatically.

Free for members

Chat with this breakdown — free.

Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.

Create a free account →

Chapters

Where the time goes.

00:00 – 00:34

01 · Intro

Hook framing two slash commands as a learning ladder: /power-up takes you zero to 80%, /insights closes the gap from 80 to 100%.

00:34 – 02:00

02 · /power-up walkthrough

Live terminal demo of the 10 PowerUp modules. Shows the menu, walks through Talk to Your Codebase, Steer with Modes, Automate Your Workflow, and Multiply Yourself.

02:00 – 03:00

03 · /insights -- what it does

Explains the purpose: /insights creates a private HTML report card from 30 days of JSONL session logs. Shows the command being submitted and the scrub step.

03:00 – 04:37

04 · Walking through the HTML report

Opens the scrubbed report in the browser. Covers At a Glance, What is Holding You Back, Quick Wins, Ambitious Workflows, and What You Work On.

04:37 – 05:50

05 · Analytics breakdown

Usage analytics: top tools (Bash, MCP), session types (single-task vs multi-task), languages (TypeScript-heavy), user response time distribution, multi-clouding percentage.

05:50 – 07:59

06 · Where things go wrong + On the Horizon

Highlights the Hooks section with a personalized settings.json snippet and the On the Horizon section which generates autonomous morning pipeline meta-prompts.

07:59 – 08:58

07 · Building the /monthly-insights skill

Pastes the 4-step build prompt into Claude Code: run /insights, extract friction points, save to Obsidian via CLI, email summary via Google Workspace CLI.

08:58 – 09:39

08 · Running the skill + scheduling

Live demo of /monthly-insights creating a timestamped note in the Obsidian vault. Shows /loop and /schedule as options to automate the whole workflow.

09:39 – 09:41

09 · Recap and CTA

Recaps the 0-to-80 / 80-to-100 ladder. Offers the Obsidian skill free via Gumroad. Plugs the early AI adopters Skool community.

Atomic Insights

Lines worth screenshotting.

/power-up is a structured 10-lesson interactive module built into Claude Code covering the 80/20 of core features from file tagging to sub-agents.
/insights reads your last 30 days of JSONL session logs and generates a fully private HTML report card with personalized analytics.
The report includes what you work on most, top tools used, where sessions go wrong, and an On the Horizon section of autonomous workflow meta-prompts.
The real value of /insights is not the HTML page. It is using the output to update CLAUDE.md rules automatically and encode friction patterns into long-term memory.
A custom /monthly-insights skill that runs, extracts, saves to Obsidian, and emails takes a single 4-step prompt to Claude Code.
Session history is stored in JSONL format, so the insights output can be reformatted in any shape by changing the extraction prompt.
The On the Horizon section generates meta-prompts: autonomous workflows you could build, written as copy-paste-ready Claude Code prompts.
Scheduling /monthly-insights with /loop or /schedule turns the self-improvement loop into a fully autonomous feedback system.
/power-up gets you to 80% understanding; iterating on /insights feedback closes the gap from 80% to 100%.
New Claude Code skills do not exist in a running terminal session. Always start a fresh terminal session before testing a newly created skill.

Takeaway

Your session history is already a coaching dataset.

WHAT TO LEARN

The gap between using Claude Code and using it well is mostly hidden in your own past sessions -- /insights makes that gap visible and actionable.

01Intro

/power-up takes you from zero to 80% proficiency; /insights closes the gap from 80% to 100% by making your own mistakes the curriculum.

02/power-up walkthrough

/power-up is a structured 10-lesson interactive module built into Claude Code covering the 80/20 of core features from file tagging to sub-agents.
Each lesson includes a pseudo-GIF in ASCII art and a prompt you can run immediately -- it teaches by doing, not by reading.

03/insights -- what it does

/insights generates a fully private HTML report card from 30 days of your own JSONL session logs -- no data leaves your machine.
The report takes 1 to 5 minutes to generate and lands as a local HTML file you open in any browser.

04Walking through the HTML report

The At a Glance section is a plain-language summary of what is working and what is slowing you down -- read this first before diving into analytics.
The Quick Wins and Ambitious Workflows sections suggest specific hooks and skills based on your most repeated workflows.

05Analytics breakdown

The analytics track top tools used (Bash, MCP, search), session types, programming languages, and multi-clouding percentage -- all derived from your local JSONL logs.
User response time distribution shows how long you personally take to reply to Claude -- longer gaps often correlate with confusion or interrupted flow.

06Where things go wrong + On the Horizon

The Where Things Go Wrong section identifies recurring failure modes by name -- treat these as bugs in your workflow, not in Claude.
The On the Horizon section writes autonomous workflow prompts based on your patterns -- copy one into Claude Code and you have a starting point for a real automation.

07Building the /monthly-insights skill

The entire /monthly-insights skill can be built with a single 4-step natural-language prompt to Claude Code.
The Obsidian integration requires the Obsidian CLI installed separately -- without it the skill will fail on the save step.

08Running the skill + scheduling

New Claude Code skills do not exist in a running terminal session -- start a fresh session before testing any skill you just created.
Scheduling /monthly-insights with /loop or /schedule converts a manual review process into an autonomous feedback loop.

Glossary

Terms worth knowing.

/power-up: A built-in Claude Code slash command that presents 10 interactive lessons covering core features, designed to take a user from zero to 80% proficiency through guided, terminal-based walkthroughs.
/insights: A built-in Claude Code slash command that analyzes 30 days of local JSONL session logs and generates a private HTML report card on how you actually use Claude Code.
JSONL session logs: The local files Claude Code writes after each session, storing each chat turn as a JSON object on its own line. These are the raw material /insights reads to build the report.
Obsidian CLI: A command-line interface for the Obsidian note-taking app that allows scripts to create or update notes in a vault without opening the GUI.
Google Workspace CLI: A command-line tool for interacting with Google Workspace services, used here to send email summaries from a script without opening Gmail.
On the Horizon: The final section of the /insights HTML report that generates meta-prompts: ready-to-paste Claude Code prompts for autonomous workflows tailored to your actual usage patterns.
Multi-clouding: Running multiple Claude Code sessions simultaneously, detected when sessions overlap in time. Shown as a metric in the /insights analytics breakdown.

Resources

Things they pointed at.

08:00toolObsidian CLI

07:23toolGoogle Workspace CLI

09:18linkEarly AI Adopters Skool community ↗

09:18productMonthly Insights Skill (Gumroad) ↗

Quotables

Lines you could clip.

02:00

“Slash insights is infinitely more powerful.”

Tight pivot line -- creates curiosity gap before the main demo.→ TikTok hook↗ Tweet quote

04:40

“A series of analytics that only Claude Code could know about you.”

One-liner that lands the unique value of session-log analysis.→ IG reel cold open↗ Tweet quote

08:53

“You're basically scheduling the execution of a workflow whose sole intention is to give you feedback on how you become superhuman in Cloud Code.”

Strong aspirational close -- works standalone.→ Newsletter pull-quote↗ Tweet quote

09:00

“One of these commands, power up, will take you from zero to 80%, and then through the iterations and feedback of slash insights, you will in a very short amount of time go from 80% to 100%.”

Clean ladder framing -- explicit outcome promise.→ IG reel cold open↗ Tweet quote

The Script

Word for word.

Read-along

Don't just watch it. Burn it in.

See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.

metaphor

In this video, I'm gonna demo two very easy ways to take your Claude code skills to the next level. They're both short and sweet slash commands that you either don't know about at all or are greatly underutilized. Both are minimal complexity, but can make all the difference and give you that extra alpha you need to be better than 90% of folks.

One of these is hot off the press and will act as your learning companion to give you the eighty twenty of using Cloud Code. And the other will act as your personal trainer, where it will continually monitor your progress and give you all the critique and the tips and tricks tailored to the way that you personally use Cloud Code.

So if you watch this video till the very end, you'll have two more tools in your back pocket to take your Cloud Code skills to new heights. Let's get into it. The two slash commands are slash power up as well as slash insights.

Now you're gonna have to make sure you update to the absolute latest version on 02/1990. I'll start off with power up because it's super simple. And if you already know about using Insights, just wait because I'm gonna show you a different way that you can use it to your advantage.

So if you use PowerUp, the whole point of it is it's meant to be, like I said, your learning companion. So when you use it, you could see that you have 10 different PowerUp's to unlock, and these are basically the eighty twenty fundamentals of just knowing how to use Cloud Code. This is not going to make you a wizard.

This will take you from zero to, again, 80 in terms of core understanding. So one goes through how to talk to your code base. So if you click on enter, this will walk you through and it will show you the at simple and how you can use the at simple to tag specific files, maintain context window, and reduce the ability for Cloud Code to just aimlessly look for files.

This will show you a small preview, basically a pseudo GIF in the form of ASCII art, and it will tell you exactly what to do. And if you go into something like steer with different modes, it will walk you through every single mode in Cloud Code.

If you're using this or you've been using these methods for a while, this isn't groundbreaking news to you. But some of these become really helpful.

So extending with tools, automating your workflow, walking through when and where to use skills and how to run them. And then when we use something like multiply yourself, if you're less familiar with things like agents and sub agents, this will break down exactly how those work behind the scenes. So for power up, this is pretty much the TLDR.

So going now into insights, which is infinitely more powerful. If we go into here and we do slash insights, the whole point of this function is it will create a web page for you.

This web page will have your report card on how you've been doing with using Cloud Code over the last thirty days. It'll walk through the good, the bad, any observations, and give you a series of analytics that only Claude Code could know about you.

So I'm gonna shoot this over to Claude Code, and I'll show you the result once it's done. So this process will take anywhere between one to five minutes, and then you'll get this HTML file. Now I wanna open this file for you to walk through exactly what to look out for.

But because there's a lot of client data, personal data, I'm just going to scrub this, and then I'll show you the scrub version. And once it's done scrubbing, then all I do is I ask it to use Bash to open up the web page for me. And then we get something like this, a very minimalistic web page that has a series of analytics.

If we go to the very, very top, you'll see here at a glance, it walks you through what is working, the TLDR of that. You've built Cloud Code into a genuine business operating system using Gmail, client invoicing, meeting scheduling, and then the next section goes through what is holding you back, what is hindering you, how you can do a better job of managing Cloud Code.

It goes through some quick wins, some ambitious workflows that you can actually set out to accomplish based on your usage, and then you have these core sections. What you work on, how you use Cloud Code, impressive things, where things go wrong, features to try, new usage patterns, etcetera.

So if we go through, this is what you work on. So this is a summary, and it walks through the number of sessions. And if you're curious how it does this, a lot of your sessions are in JSONL format.

So these chats that you have can all be compartmentalized and categorized any which way you want.

So even though insights structures it in this way, you can format it to do whatever you'd like. So as you go down here, you'll see these are examples of analytics. So examples of what I wanted, so most of them being bug fixes, top tools used, in this case, from the tool set from Cloud Code, I'm using bash quite a bit, and you'll see other things like MCP usage, searching, etcetera, session types, different languages that I'm writing in.

For the most part, it seems to be TypeScript with some minimal use of Python, a breakdown that I am a power user, surprise, surprise, and everything else that's involved, any form of key patterns, average user response time.

And then as you go down here, let's say impressive things you did. So this is where it hypes you up on things that you've done well. But for me, where I wanna care and put my attention to are where things go wrong.

So wrong diagnosis loops, destructive or overbroad actions, so basically me lazily prompting, repeated image and asset generation failures, so that's for generating thumbnails like the one that brought you to this video.

And then these are examples of exciting Cloud Code features to try, and it even provides you different recommendations for using hooks in the right way depending on your level of behavior. So in this case, says, you already built session start hooks for brand guidelines, extend this pattern to auto load project context and auto run, let's say, linting, type checks, etcetera.

So it gives you also the solution that you can add to your JSON file. And this is the section that you really wanna pay attention to, which is called on the horizon. And you can even create an automated pipeline to go and pull ideas from this and implement it because it will look at all of the sessions that you've had and go through different recommendations.

So based on how I like to use my Cloud Code in the very early morning, it says, you should create an autonomous morning operations pipeline, and it goes through everything possible that I could do. And this is what I would paste in the cloud code in the form of a prompt. So it even creates a meta prompt on what to do based on the behavior.

So if you wanna leverage this, then from all the recommendations, assuming that you are in line with said recommendations, you could create a scheduled job, a skill, a loop, whatever it is, to go through the recommendations and implement them.

In my case, I not only want to leverage them, but I also wanna store them in my second brain in Obsidian and be able to create a report like this where I get an email every 30 walking through all these insights in the way that I care to see them. So instead of seeing this web page with different piece parts that are nice to haves but could have some fluff, I can iron it down to exactly what I'm looking for.

And assuming that you're on the same page with Claude code, you can send the following prompt where you can say, take the suggested rules from the slash insights report and save them as new rules in my dot Claude folder. If you're as big as an Obsidian user as I am, then you can also send the following prompt to create a skill not only to generate the asset to send the email, but also store it in a crystallized repository in the vault of your choice.

So you could say something like this, build me a custom skill that does four things. Number one, runs the insights command. Number two, reads the report and pulls out the friction points, the really salient nuggets.

Then number three, you wanna store this and save this in a vault of your choice. Now you wanna make sure you have the Obsidian CLI command line interface installed, and some skills out there can really help you.

So if you're not as familiar with both of these concepts, but you wanna use Obsidian, make sure to check out the video that's appearing in the top corner of this video right now. And then number four is email me a clean summary using the Google Workspace CLI, another command line interface tool that I covered as well.

This will allow you to easily integrate with your Google Workspace if you're a Gmail user. Otherwise, there are different ways to access things like Outlook or any other provider. Once you run this and set it up, make sure to start a brand new terminal session because brand new skills don't exist in your current session until you clear it.

So when we go into that session and run slash monthly insights, you'll now see it create the report, save it to Obsidian using the CLI, and in Obsidian itself, if we navigate to my second brain, you'll see this section at the top left hand corner called clawed tips. So in here, automatically, we are storing the review, time stamped.

This breaks down everything that is super important. So from the TLDR of the web page, we now make our own synthesized tailored version, and now we can tap into this from anything you want. It could be your Open Claw.

In my case, it's my Clawed Claw, or anything remotely where I wanna be able to tap into these cheat codes. And in case you want this to happen automatically, the only thing you'd really have to do is either use slash loop or slash schedule.

And you could schedule the running of this insight skill and then the execution of it end to end. So now you're basically scheduling the execution of a workflow whose sole intention is to give you feedback on how you become superhuman in Cloud Code.

So one of these commands, power up, will take you from zero to 80%, and then through going through the iterations and going through the feedback of slash insights, you will, in a very short amount of time, go from 80% to a 100%.

If you want access to the Obsidian skill that I've just created right in front of you, I'll make that available to you on the house in the second link in the description below. If you like the way that I go through these concepts and you want even more exclusive content on how to become an absolute expert using Cloud Code, then make sure to check out the first link in the description below, and maybe I'll see you in my early AI adopters community.

If the rest of you, if you found this video helpful, then please make sure to leave a like and a comment on the video. Really helps the videos reach and the channel, and I'll see you in the

The Hook

The bait, then the rug-pull.

Two slash commands ship inside every Claude Code install, ignored by most users -- one teaches you the fundamentals in ten interactive steps, the other turns thirty days of your own session history into a private coach that knows exactly where you waste time.

Frameworks

Named ideas worth stealing.

00:53list

The 10 PowerUp Modules

Talk to your codebase (@-mentions, file tagging)
Steer with modes (shift+tab, plan/auto)
Undo anything (/rewind, Esc-Esc)
Run in the background (tasks)
Teach Claude your rules (CLAUDE.md, /memory)
Extend with tools (MCP, /mcp)
Automate your workflow (skills, hooks)
Multiply yourself (subagents, /agents)
Code from anywhere (/remote-control, /teleport)
Dial the model (/model, /effort)

An interactive 10-lesson curriculum covering the 80/20 of Claude Code fundamentals, accessible via /power-up.

Steal forOnboarding doc for any developer team adopting Claude Code

02:24model

/insights HTML Report Structure

At a Glance (what is working + what is hindering you)
Quick Wins
Ambitious Workflows
What You Work On
How You Use Claude Code (tools, languages, session types)
Impressive Things You Did
Where Things Go Wrong
Features to Try (with personalized settings.json snippets)
On the Horizon (autonomous workflow meta-prompts)

The nine-section structure of the /insights-generated HTML report card, built from 30 days of local JSONL session logs.

Steal forTemplate for any AI usage review document

07:59list

The 4-Step Monthly Insights Skill

Run /insights to generate the usage report
Read the report and extract friction points and suggested CLAUDE.md rules
Save as a timestamped Obsidian note via the Obsidian CLI
Email a clean summary via Google Workspace CLI with subject Monthly Claude Code Review

A single Claude Code prompt that builds a complete /monthly-insights skill covering report generation, extraction, vault storage, and email delivery.

Steal forAny AI tool usage review that needs to go from raw data to inbox automatically

CTA Breakdown

How they asked for the click.

VERBAL ASK

09:18product

“If you want access to the Obsidian skill that I just created right in front of you, I will make that available to you on the house in the second link in the description below.”

Clean, low-pressure offer. Gives away the skill for free as a lead magnet to the paid Skool community. Delivers value first, then pitches.

MENTIONED ON CAMERA

09:18linkEarly AI Adopters Skool community ↗

09:18productMonthly Insights Skill (Gumroad) ↗

FROM THE DESCRIPTION

PRIMARY CTAWhere the creator wants you to go next.