Anatomy of a skill

Description and use

<p>This started with a surprise, not with a plan. I needed a survey of the state of the art on a topic I was considering working on, so I ran <code>deep-research</code>, a skill that ships with Claude Code, and it came back with a report I didn't expect from a single run —27 sources, 123 claims extracted, 25 verified, and of those 18 confirmed and 7 refuted— with an executive summary, caveats, and open questions. What struck me wasn't the volume (I already covered the 109 agents in the previous post) but that all of it came out of <strong>a single skill</strong>. I wanted to see how it was bui

Problem

<p>This started with a surprise, not with a plan. I needed a survey of the state of the art on a topic I was considering working on, so I ran <code>deep-research</code>, a skill that ships with Claude Code, and it came back with a report I didn't expect from a single run —27 sources, 123 claims extracted, 25 verified, and of those 18 confirmed and 7 refuted— with an executive summary, caveats, and open questions. What struck me wasn't the volume (I already covered the 109 agents in the previous post) but that all of it came out of <strong>a single skill</strong>. I wanted to see how it was bui

Outcome

<p>This started with a surprise, not with a plan. I needed a survey of the state of the art on a topic I was considering working on, so I ran <code>deep-research</code>, a skill that ships with Claude Code, and it came back with a report I didn't expect from a single run —27 sources, 123 claims extracted, 25 verified, and of those 18 confirmed and 7 refuted— with an executive summary, caveats, and open questions. What struck me wasn't the volume (I already covered the 109 agents in the previous post) but that all of it came out of <strong>a single skill</strong>. I wanted to see how it was bui

Evidence

Anatomy of a skill

Source