There's a widespread problem plaguing

Claude users recently, specifically on

Opus 5, because its replies [music] tend

to be confusingly long, packed with all

too possible nonsense, and it's becoming

more and more jargon dense. The good

news is that Anthropic already shared a

fix for this. It's super easy, and the

principle behind it makes your setup

faster and cheaper, and it lets you

finally understand what the heck your

agents are actually saying. And by the

end, I'll hand you a resource that

solves all of this automatically just by

sending it to Claude. Let's dive into

it. So, if you've been using Opus 5

heavily the past few days, you may have

noticed two specific problems with it.

The first one's the jargon problem,

which is its tendency to use technical

terms or acronyms much more versus

earlier models, which makes it much

harder to understand and work with. Just

to give you one simple example, and this

is probably not the worst of it. If you

ask a simple question to Opus 5 like

this, where I said our CRM dashboard

says open rate is 32%, and I said from a

conversation with a peer, we discussed

how open rates are basically fake now.

So, I ask it what does that mean, and

should I care? And it did give us a

proper explanation here, but it seems to

always default to being more

comprehensive and more technical than

most people would probably want it to.

And you can see its tendency to assume

that you know every single jargon in the

field as well. Like for example, here

it's saying every Apple Mail recipient

with MPP on registers as an open. And it

also tends to use a lot of technical

jargon like send time optimization, geo

data, or device data derived from opens,

MPP masks IP, and reports a generic

device. So, all of this is corrupted.

So, you can see what I mean, right? And

like I said, that example was probably

not the worst of it, because I first

became aware that this is sort of a

widespread problem when I saw this tweet

by Peter Levels, who's pretty popular in

the in the hacking space, where he

shared this snippet of an article that

made the rounds around X recently. And I

can probably show the actual article

just to give credit where it's due. So,

this was written by Niklas Kron, if I'm

ever pronouncing it correctly. And I

think he summarized the problem really

well here, where he's saying that

reading AI output today is extra effort.

You can pretty much do it, but it is

extra effort. It's verbose, it

frequently contains all too plausible

nonsense, and is increasingly jargon

dense. And then he says that he recently

got this sentence from Claude that even

I don't know what this means really. And

then the second, but related problem is

the wall of text issue. So if we go back

to our example here, you probably

experienced the same thing where you ask

it a simple question and then it goes

into a full-blown essay and gives you a

wall of text as an answer. And for most

cases, there's multiple issues with

that, right? Because it wastes your time

because you need to understand and read

through this whole thing in order to get

to the point. And secondly, there is

also a corresponding cost for tokens

because the longer it's output to you,

the more tokens that Claude is

consuming. And so if you have this same

problem with Opus 5 as well, which a lot

of people seem to be using as their

default, then you're in the right place

because today I'll be showing you the

two solutions for those two unique

problems. And by the way, if you want to

learn how to build and sell AI systems

that businesses actually pay for, then

that's pretty much all we do over at the

Robonuggets community where not only do

you get access to the Claude Living

Masterclass, which we update every week

and takes you from zero to mastery with

the latest on AI, but you also get

access to our Agents as a Service

course, which walks you through how to

actually get paid for all these AI

skills that you are learning. You also

get to be part of a genuinely great

community of AI builders. In fact, you

can see just some of the recent wins our

members are getting from the program

right here. So if you want to start

earning from AI, then check that just in

the pinned comment below. Now back to

the video. So let's start with the

jargon problem. And the good news about

this is that Anthropic's team actually

talked about how to fix this one issue.

And that fix is courtesy of Lidia, who

is a member of technical staff at

Anthropic. And essentially, it all has

to do with this configuration in Claude

Code that's called the output style. And

the output style is simply just that. It

is the style by which Claude Code

provides its output to you or how it

talks to you. And I'll just show you

where to find it, at least in the

terminal view, but I'll show how to do

it in the desktop app as well if in case

you're more comfortable there. But here

in the terminal, if you have Claude

Claude open, you can slash config, which

brings up all your settings. And if you

find output style here, and if I click

on enter, what you would most likely

find is that your Claude is set to the

default output style, which is that

verbose jargony output that Opus 5

usually defaults to. You have other

options here like proactive,

explanatory, and learning that Claude

Claude ships with by default. But you

can see that I have a fifth one here

that I added as a custom called ELI5.

And this ELI5 is the fix that Lydia was

talking about here. And in case you're

curious, ELI5 simply stands for explain

like I'm 5. It is a popular subreddit.

And so the reason why that acronym works

for a lot of models, including Opus 5,

is because they've been trained with the

entirety of the internet, including that

subreddit. And if you're curious, this

is what that subreddit is. And there's

like thousands of posts in here asking

questions in the ELI5 format. And you

can be sure that these models have

scraped this whole thing in order to

understand how people respond to these

questions. But the core principle of it

is if you want things to be simple to

understand, then this ELI5 is one way to

do it. Now, obviously, you don't have to

adopt the exact verbiage that Lydia has

here. For example, one thing that I

added in my output style personally is

this tip from Andrew that I found where

he asked Claude to only report to him in

this ASD STE 100 simplified technical

English. So what is that? Well, in a

nutshell, that's essentially a

controlled language standard that uses a

more restricted dictionary. So a list of

words that are much easier to

understand. So it avoids jargon, it

avoids a lot of those technical

vagueness. And at least from what I

found personally, and for a lot of

people it seems, that standard seems to

help a lot in terms of just making

talking to your agents much easier and

much more seamless. So how do you now

apply this fix and actually change your

output style so you can test it out?

Well, what you can do is to just copy

this prompt or take a screenshot of it

and send it to your Claude Claude. And

what you're saying here is simply to set

your output style to the one below,

which is this whole snippet from Lidia

with that addition of the ASDSE100.

And then the important part here is

direction to save it in your output

styles folder, which obviously depending

on your workspace, that location of that

folder may be different. But the good

news is Claude Code can probably find

that for you. At least for me, this is

where it put that markdown file. And

within this markdown file is just this

piece of text. And then the second thing

that this prompt will do is to just set

this output style for ELI5 in the

appropriate settings files. And you can

see for me, because I already have it

set, that is what Claude also told me,

where it created that style file for me

that ELI5.md. And it also updated the

relevant settings. And the best way for

you to check is to just open up a new

session and ask what output style it's

using now just to confirm. And if you

need to make any changes to it, then you

can just tell that to Claude and it will

update this output style for you. Now,

you may be asking why it's important to

put these rules in the output style

instead of something like the Claude.

md. And the truth of the matter is that

you can actually put these rules into

Claude.md, but it just isn't as

effective. And if you're curious, it has

to do with two things. One is the

strength of the placement with regard to

the output style, because if you notice,

what we changed earlier is the actual

settings for Claude Code. So, it's

written into the core system prompt of

your Claude Code instance. And then more

importantly, at least I would think, is

that under the hood what Claude Code

actually does is it auto injects these

sort of nudges, these reminders like

stick to your output style even midway

through out your session. So, if you

were to show that visually, your

Claude.md that does get preloaded into

every session that you start, but only

at the top, right? But the great thing

about putting this rule into your output

style is that it becomes part of the

core system prompt, number one, and

number two, throughout your session,

Claude Code actually gets reminded about

this rule so that it follows it more

consistently and religiously. And just

to give an example of that same question

that we asked it, if you read through

this, it's much more legible now, at

least in my view. It leads with the key

answer, where it's saying that that open

rate is not all real people. And then it

tells the clear story here of why that

is, and then ends with this conclusion

that anyone can understand. Now, that

fixes the jargon problem. Now, let's go

to the second issue, which is this wall

of text that you usually get from Opus

5. And for a lot [snorts] of use cases,

especially knowledge work or production

code, the tricky part about this problem

is that you do sometimes need long

pieces of text in order to get a lot of

the detail that you need. And so this is

why I generally I won't advise people to

put the wall of text fix right in the

output style. And so what I would

generally recommend is to just use a

skill when you need that wall of text to

be shorter. And in our community, I

always advise people to make their own

skills because each of our work is

different. But let me give you some

ideas, and I'll also share how I do it

personally. One really interesting skill

that I found is this one called {slash}

bro. And it's probably one of the

shortest, but really useful skill that

you can add to your arsenal because it

is only one line. So its sole purpose,

whenever you invoke it, is for your

agent to restate the last message in

plain human language with zero jargon.

And so if we go back to this wall of

text, and you can see here I just used

that skill, {slash} bro. When it rewrote

their response, it's saying here, "Okay,

so basically that 32% never meant 32 out

of 100 people actually read this. And

here's how it actually works." So I'm

not going to read the whole response

here, but you can see just how much more

understandable and better it is versus

what we started, right? Another example

of a skill that I found is this one from

Matt Pocock. It's called wait, what? So

again, it's a very short skill. It says,

"I don't understand where you've got to

here. Repitch that and give a little bit

of context." And this is what I'm saying

where you need to create your own skills

because you can see from Matt's

workspace here, he probably has this

context.md that he uses a lot. You may

not have that. So what you can do is to

take a screenshot of this or copy this

skill and just ask Claude to personalize

it for your own setup. Now, what I tend

to do personally, in conjunction with

{slash} bro, since you can see sometimes

Opus 5 still defaults to a wall of text

if it doesn't know how long you want the

response to be. Is I use this skill of

mine called /quick, where I just declare

a number, in this case three, and it

gives me just three points in sequence

of what it thinks is the most important

takeaway from that whole essay that it

wrote. And just to show you what that

skill looks like, I think it's this one.

Yeah, so you can see this is the /quick

skill. And you can see just in its

current state, it just has rules on when

to use it when I don't declare a number,

when I declare a number. And apparently

there's now, how many? Two modes here

that probably naturally arose since I

use this skill a lot, and I also ask

Claude to tweak it depending on our

conversation. But that is one idea by

which you can cut that wall of text into

more bite-size chunks. But like I

mentioned, it's probably better for you

to just get these ideas for skills and

create them yourself as well, depending

on your type of work. Now, what I talked

about just now are pretty simple fixes,

but if you take a step back, there's

actually a larger takeaway to this whole

thing. Because interestingly, and if you

remember, Opus 5 is actually the best in

terms of a lot of benchmarks that we see

online, including this one from

artificialanalysis.ai,

where it is leading at the moment. And

so, the first key takeaway here is that

even though benchmarks show the raw

intelligence of these models, user

experience can sometimes differ. So,

it's sort of like if you bought a

computer with the highest specs

available, but then you actually find

that you prefer your older computer just

because of maybe some unique features

that that old model have. So, it's quite

similar to AI models also is what I'm

finding. And so, what you should realize

here is that let's say a year or two

down the line where you have Opus 7 or

Opus 10 already, if those future more

powerful models have the same issue as

well, the good news about it is that

these AI models are very malleable, and

you can just tweak your AgentiC

Operating System, or essentially the way

that you talk to these agents, through

these same solutions that we talked

about, and that will just provide a much

better experience for you when you work

with agentic AI. And so just remember

that you can always direct these models

with your preferred output style as well

as these skills, which are essentially

shortcuts. And just to make it easy,

everything that I talked about in this

lesson in this video, I just put it all

in this eight-page PDF, which you can

probably just send to your cloud code

and just pick out the prompts and the

styles and the skills that you would

need and just tweak them to whatever

your workspace needs. So you can just

find this whole thing down in the

description. I hope that was helpful and

as always appreciate you for making it

until the end because that helps me a

lot and I'll see you next time. Thanks.

>> [music]