CC leak: skills are better than I thought
1–10 of 16 posts
Re: CC leak: skills are better than I thought
#2A technical breakdown of how agent skills are parsed, rendered, injected, and refreshed in your Claude Code working session.
Re: CC leak: skills are better than I thought
#3I thought this was worth the quick read. Just as the article says at the start, I thought skills were essentially the same as pasting a long Markdown prompt document into the Claude Code window, or having Claude read the prompt file. But it seems if you invoke the skill, CC handles it quite differently, eg it's special cased for how it survives compaction.
Changed my mental model of using Skills a bit anyway.
Re: CC leak: skills are better than I thought
#4"You aren’t simply giving the agent instructions, you are changing how it operates."
Why is the AI generated "Mic Drop" everywhere now.
Re: CC leak: skills are better than I thought
#5> 4. persisting context across compactions
> LLMs forget things as their context grows. When a conversation gets long, the context window fills up, and Claude Code starts compacting older messages. To prevent the agent from forgetting the skill’s instructions during a long thread, Claude Code registers the invoked skill in a dedicated session state.
> When the conversation history undergoes compaction, Claude Code references this registry and explicitly re-injects the skill’s instructions: you never lose the skill guardrails to context bloat.
If true, this means that over time a session can grow to contain all or most skills, negating the benefit of progressive disclosure. I would expect it would be better to let compaction do its thing with the possibility of an agent re-fetching a skill if needed.
I don't trust the article though. It looks like someone just pointed a LLM at the codebase and asked it to write an article.
Re: CC leak: skills are better than I thought
#6"You aren’t simply giving the agent instructions, you are changing how it operates." Why is the AI generated "Mic Drop" everywhere now.
the simple answer would be that "AI is in use everywhere"
Though I'd love to see an analysis of pre-gpt writing to see if it was more prevalent than we remember but lacked the acute sensitivity to it.
There's also the potential that AI started it but people read AI stuff and organically propagate AI tropes in their own words because it's part of the writing they consume.
Re: CC leak: skills are better than I thought
#7"You aren’t simply giving the agent instructions, you are changing how it operates." Why is the AI generated "Mic Drop" everywhere now.
"injecting messages, not prompts"
Re: CC leak: skills are better than I thought
#8"You aren’t simply giving the agent instructions, you are changing how it operates." Why is the AI generated "Mic Drop" everywhere now.
Honestly people spoke like this before, just on LinkedIn. Now that ai trained on it we have LinkedIn.. everywhere. Welcome to hell.
Re: CC leak: skills are better than I thought
#9"You aren’t simply giving the agent instructions, you are changing how it operates." Why is the AI generated "Mic Drop" everywhere now.
I quite like it, it’s a perfect signal for me to stop reading.
Re: CC leak: skills are better than I thought
#10> 4. persisting context across compactions > LLMs forget things as their context grows. When a conversation gets long, the context window fills up, and Claude Code starts compacting older messages. To prevent the agent from forgetting the skill’s instructions during a long thread, Claude Code registers the invoked skill in a dedicated session state. > When the conversation history undergoes compaction, Claude Code re…
Author here,
> It looks like someone just pointed a LLM at the codebase and asked it to write an article.
Not entirely true. I pointed an LLM at the codebase to get me to the right files for understanding skills, and to map out the dependencies and lifecycles - Then I spent quite a bit of time reading the code myself and writing about it.
An AI review at the end of the writing (to "sharpen" the language) unfortunately brought in a couple of AI fingerprints (note the "mic drop" comment above)
edit: write -> right (its 8am)