Builds one image that tells the story of a technical piece of work: what was noticed, what was wrong, what was done and why each step works, where every number comes from, and what it achieved and taught.

Produces Mermaid diagrams for technical processes and structures. This is the fast, syntax-driven counterpart to `content-diagrams`: same visual-clarity standards, but built on a language that already guarantees correct geometry, so the effort goes into picking the right diagram type and a readable,

A compression skill. The summary must work as a reliable technical/legal proxy for the source — someone reading only the summary should walk away with the same names, numbers, and logical progression they'd get from the full text, just faster.

Turn a scientific paper, technical article, report, blog post, abstract, or research notes into an English LinkedIn post, plus three candidate hooks. Use this whenever the user shares a paper, arXiv link, abstract, PDF, research summary, or technical write-up and asks to "write a LinkedIn post", "post about this paper", "summarize this for LinkedIn", or wants to communicate a research finding to a professional English-speaking audience. Trigger it even when the user just drops a paper or link and says "make a post" without naming LinkedIn, and also when they ask only for hooks. Do not use for non-scientific LinkedIn posts (career updates, anecdotes, product or project announcements), for X/Twitter posts (use tweet-post), or for Arabic posts (use linkedin-arabic-science-post).

Reads an existing skill and reports back: what it does, how it flows, whether it's well-built, whether what it teaches Claude to do is actually correct, and what to fix. Does not write the fix itself — that's skill-creator's job.