After building a growing set of GitHub Copilot skills across areas such as Azure API Management, infrastructure as code authoring, and diagram generation with tools like Excalidraw and Draw.io, I have found that the difference between a skill that is genuinely useful and one that quietly disappoints usually comes down to a small number of design choices. Most of those choices...

If you have been building GitHub Copilot agents and skills for any length of time, you eventually run into the same problem: creating them is the easy part. Sharing them properly is where the real friction starts. At first, the workaround feels reasonable. You build a useful agent for Terraform provider upgrades. You add a skill for architecture reviews. Maybe you create anot...

There is a point where diagramming starts to feel like admin. You are in the middle of thinking through an architecture, a delivery workflow, or a system interaction. The shape of it is clear enough in your head, but getting it into a diagram means stopping what you are doing, opening another tool, dragging boxes around, lining arrows up, fixing spacing, and then exporting so...

One of the things that used to slow me down when designing Azure architectures was the pricing question. You sketch out a solution, choose the services, think through HA, security, networking, and how it will land in Terraform or Bicep, and then someone asks: what does this actually cost? That is usually where the flow breaks. You alt-tab to the Azure Pricing Calculator…