When designing a skill, I first think of how it will be used. Skills are tightly focused, all signal, no noise, packages of mental models. They are the principle distilled with some specifics woven in. Skills must not be bloated, since they are designed to compose with other skills dynamically. Similar to a knowledge graph or zettelkasten notebook, skills are index cards of functionality. They are written to be maximally effective and salient. Skills occur at many levels of abstraction: - specific knowledge "Testing with Deno" - specific practice "SWOT Analysis", "Technical Review" - mental m…