I'm back on my Agent Skill stuff, at least for today. Someone at work flagged a change to how a harness was handling specific skill metadata a few weeks ago, which made me realize that aside from posting about it here and on the Agent Skill Implementation website, I haven't talked to people at work about how skills that are spec-compliant may not be cross-harness portable. Or all the ways the Agent Skills spec is - under-specified - and has left harness providers to implement things their own way, which means that skills that load in one harness may not load in another.
I was heavily involved in the skills program at MongoDB; I wrote a lot of tooling, process, and enablement materials for the org. But by the time I joined NVIDIA in July, their skills program was already mature, with a dedicated PM and engineering resources, and teams shipping skills autonomously. So I've had very little to do with skills at NVIDIA.
Today I'm giving a presentation for the skills working group on these harness portability and compatibility issues. If you ship skills and you've missed my posts on this, do check out the website here where I go into details: https://agentskillimplementation.com