Write Skill descriptions in third person with explicit 'what + when' — it's the discovery key among 100+ skills

Claude Docs·medium signalXBlueskyLinkedInCopy link

Claude selects a Skill purely from its name and description at startup, so the description must state both what it does and the specific triggers/contexts for using it, always in third person ('Extracts text and tables from PDFs… Use when…'), never first/second person, which causes discovery failures. Pair this with gerund-form names (processing-pdfs, analyzing-spreadsheets) for a consistent, greppable library. A vague 'helps with documents' description means the Skill silently never fires.