Turn a PDF Guide Into a Skill by Deleting Most of It
A document explains to a reader. A skill instructs an agent whose every line is a recurring token cost — so a faithful conversion produces a bad skill. What to cut, what to move into bundled files, and the one field your PDF can never give you.
- #claude-code
- #skills
- #documentation
Sign in to keep reading
Turn a PDF Guide Into a Skill by Deleting Most of It — A document explains to a reader. A skill instructs an agent whose every line is a recurring token cost — so a faithful conversion produces a bad skill. What to cut, what to move into bundled files, and the one field your PDF can never give you.
Your first guide is free. Sign in with Google or LinkedIn to read the whole library and get new guides as they ship — no cost.
Keep reading
More guides like this one.
Build a Claude Skill Three Ways: Write It, Capture It, or Install It
All three paths end in roughly the same 30-line file. What they don't produce equally is the description — the only part of a skill that sits in context permanently, and the only part that decides whether it ever fires. Pick your path by where the knowledge lives today.
When a Claude Skill Never Fires: Six Causes, in Diagnostic Order
The cruelest failure mode is a broken skill whose slash command works perfectly. Malformed frontmatter still loads the body, so /my-skill runs fine while Claude has no description to match against — and you conclude the skill is healthy. Here is the order to check things in.
I Checked the Viral "65% to 94%" Claude Stat
A skill file inspired by Andrej Karpathy is circulating with a big accuracy claim attached. I went to the repo. There is no benchmark. The idea underneath it is still the most useful thing I have changed about how I prompt.