Same Data, Same Packet
The video explains that Claude's client-review capability is not a hidden portfolio analysis app but a plain-text skill file. Claude reads the steps in order, builds the same meeting-ready packet from the same data, and reasons on its own when the file is silent.
Does a repeatable, finance-specific Claude capability mean there is a built-in portfolio analysis app underneath? This short video says no. The client-review skill is a plain text file that Claude reads, and the video uses it to explain what a skill really is, what it guarantees, and where it stops.
A skill is a folder with one file
A Claude skill is a folder Claude reads before it works. This one holds a single file, SKILL.md, which contains the full instruction set in plain language with no hidden logic. Claude reads the file and then acts on it. The video's phrase for this is that the file is the program.
Read, execute, return
The pipeline lives in the file's Steps section. Claude reads the file, runs each step in order, and returns the result. The flow is linear, with no branching unless a step itself says to branch.
What the file specifies
The client-review SKILL.md spells out exactly what to produce. It preps four things ahead of quarterly reviews, annual checkups or ad-hoc client meetings:
- a portfolio performance summary,
- an allocation analysis,
- talking points, and
- action items.
Because the file is explicit, feeding it the same account data twice builds the same meeting-ready packet twice.
When the file is silent
The video then covers the limit. Ask for something the file does not cover, such as a comparison it never mentions or a chart it does not list, and there is no instruction to fall back on. In that case, Claude reasons past the file on its own. The repeatable part of the output comes from what the file says, and the rest comes from Claude's judgment in the moment. That is a useful boundary to know, because it tells you which parts of a result you can count on to repeat and which you should check.
The carry-out
A Claude skill is not a hidden analysis app. It is a plain text file of instructions. The same account data builds the same packet every time, and whatever the file does not say, Claude has to work out itself. The video notes that it makes no claim that every skill is structured exactly like this one, only that a skill is a file Claude reads.
Key takeaways
- A skill is a folder Claude reads before it works.
- client-review has one file, SKILL.md, written in plain language.
- Claude reads the file, runs each step in order, and returns the result.
- Steps run linearly unless a step says to branch.
- The file defines a performance summary, allocation analysis, talking points and action items.
- The same account data produces the same packet each time.
- Anything the file does not cover is left to Claude's own reasoning.
Try it yourself
Paste this into Claude: write a SKILL.md for a recurring meeting you prep for. List exactly what must appear every time, then list what would be left to your judgment because the file does not cover it. Read back what Claude wrote. The first list is what repeats identically on every run, and the second is where Claude is reasoning past the file instead of following it.
Chapters
Full transcript(auto-generated, with timestamps)
The naive framing: "does the app analyze the portfolio?"
[0:00]Someone assumed Claude's client review capability was a built-in portfolio analysis app. It isn't. It's a plain text skill Claude reads. So, does Claude's client review skill analyze the portfolio or does it just assemble the meeting? A skill is a folder Claude reads before
A skill is a folder
[0:14]It works. This one is client review. The skill MD file holds the full instruction set, plain language, no hidden logic. Claude reads it then acts. The file is the program.
Read, execute, return
[0:25]The pipeline lives in the file step section. Claude reads the file, runs each step in order, and returns the result linear, no branching unless a step itself says so.
Spec it, or Claude reasons past it
[0:35]Client review skill MD spells out exactly what to produce. A portfolio performance summary, allocation analysis, talking points, and action items ready before quarterly reviews, annual check-ups, or an ad-hoc client meeting. Feed it the same account data twice and it builds the same meeting-ready packet twice. Ask for something the file doesn't cover, a comparison it never mentions, a chart it doesn't list, and there's no instruction to fall back on. So, Claude reasons past the file on its own. A Claude skill
Carry-out
[1:01]Isn't a hidden analysis app. It's a plain text file of instructions. So, the same account data builds the same meeting-ready packet every time. Whatever that file doesn't say, Claude has to work out on its own. Your turn.
Your turn
[1:14]Paste this into Claude. Write a skill MD for a recurring meeting you prep for. List exactly what must appear every time, then list what would be left to my judgment because the file doesn't cover it. Read back what Claude wrote. The first list is what repeats identically every run. The second is where it's reasoning past the file, not following
Outro
[1:31]It. Same data, same packet, lay 'em in forbear.





