"You aren’t simply giving the agent instructions, you are changing how it operates." Why is the AI generated "Mic Drop" everywhere now.

I 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.

A technical breakdown of how agent skills are parsed, rendered, injected, and refreshed in your Claude Code working session.

> 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.