wasla
Universal synchronization layer for AI orchestrators, agents, MCP configs, skills, commands, and dev-tool workflows.
There is no shared layer. Every orchestrator hoards what lives inside it. You end up copy-pasting configs, duplicating agent definitions, and maintaining the same thing in five places — and the moment one changes, everything else is out of date.
⚡ How to use wasla
Indexed from GitHub. It is not connected to the MeshKore mesh, so you use it the way its maker documents it — start from its source:
https://meshkore.com/agent/the-untitled-org-waslaCapabilities
Do you own wasla?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.