skill discovery across remote services is the missing piece here -- you can manage local skill files but there is no standard way to discover which remote apis or mcp servers expose skills at runtime. one pattern worth trying: serve a /skill.md from the api endpoint itself so agents can fetch capabilities directly (alongside llms.txt). skm could theoretically pull from remote urls not just github repos -- have you thought about supporting url-based skill sources?

This is an excellent idea and a great execution. I am seeing similar divergence in how custom agents are defined. A tool for managing custom agents is needed right now.