@kaleidorg/mind 0.4.0 → 0.5.0

package/dist/skills/registry.js.map

@@ -1 +1 @@
-{"version":3,"file":"registry.js","sourceRoot":"","sources":["../../src/skills/registry.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAIH,yEAAyE;AACzE,MAAM,CAAC,MAAM,mBAAmB,GAAG,sBAAsB,CAAC;AAE1D;;;;;;;;;;;GAWG;AACH,oEAAoE;AACpE,SAAS,OAAO,CAAC,CAAS;IACxB,MAAM,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,CAAC;IACnB,IAAI,CAAC,CAAC,CAAC,UAAU,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,UAAU,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,EAAE,CAAC;QACrF,OAAO,CAAC,CAAC,KAAK,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC;IACxB,CAAC;IACD,OAAO,CAAC,CAAC;AACX,CAAC;AAED,MAAM,UAAU,UAAU,CAAC,QAAgB,EAAE,UAA6B;IACxE,MAAM,EAAE,GAAG,QAAQ,CAAC,KAAK,CAAC,0CAA0C,CAAC,CAAC;IACtE,MAAM,IAAI,GAA2B,EAAE,CAAC;IACxC,IAAI,IAAI,GAAG,QAAQ,CAAC;IACpB,IAAI,EAAE,EAAE,CAAC;QACP,IAAI,GAAG,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;QACnB,KAAK,MAAM,IAAI,IAAI,CAAC,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC;YAC7C,0EAA0E;YAC1E,0EAA0E;YAC1E,MAAM,CAAC,GAAG,IAAI,CAAC,KAAK,CAAC,uCAAuC,CAAC,CAAC;YAC9D,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;gBAAE,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,CAAC,GAAG,OAAO,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC;QAChE,CAAC;IACH,CAAC;IACD,MAAM,IAAI,GAAG,CAAC,CAAU,EAAE,EAAE,CAC1B,CAAC;QACC,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,MAAM,CAAC,OAAO,CAAC;QACnD,CAAC,CAAC,SAAS,CAAC;IAEhB,IAAI,CAAC,IAAI,CAAC,IAAI;QAAE,MAAM,IAAI,KAAK,CAAC,wCAAwC,CAAC,CAAC;IAE1E,8DAA8D;IAC9D,MAAM,KAAK,GAAG,IAAI,GAAG,CAAC,CAAC,MAAM,EAAE,aAAa,EAAE,OAAO,EAAE,UAAU,CAAC,CAAC,CAAC;IACpE,MAAM,QAAQ,GAA2B,EAAE,CAAC;IAC5C,KAAK,MAAM,CAAC,CAAC,EAAE,CAAC,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,IAAI,CAAC;QAAE,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC;YAAE,QAAQ,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC;IAE9E,OAAO;QACL,IAAI,EAAE,IAAI,CAAC,IAAI;QACf,WAAW,EAAE,IAAI,CAAC,WAAW,IAAI,EAAE;QACnC,YAAY,EAAE,IAAI,CAAC,IAAI,EAAE;QACzB,KAAK,EAAE,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC;QACvB,QAAQ,EAAE,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC;QAC7B,QAAQ,EAAE,MAAM,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,SAAS;QAC7D,UAAU,EAAE,UAAU,IAAI,UAAU,CAAC,MAAM,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,SAAS;KACrE,CAAC;AACJ,CAAC;AAED,0DAA0D;AAC1D,MAAM,SAAS,GAAG,IAAI,GAAG,CAAC;IACxB,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM;IAC1E,MAAM,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,QAAQ,EAAE,OAAO,EAAE,KAAK,EAAE,KAAK;IAC3E,MAAM,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,EAAE,MAAM;CAC/D,CAAC,CAAC;AAEH,qDAAqD;AACrD,SAAS,QAAQ,CAAC,CAAS;IACzB,OAAO,CAAC,CAAC,OAAO,CAAC,qBAAqB,EAAE,MAAM,CAAC,CAAC;AAClD,CAAC;AAED;;;;;GAKG;AACH,SAAS,cAAc,CAAC,KAAa,EAAE,OAAe;IACpD,MAAM,CAAC,GAAG,OAAO,CAAC,WAAW,EAAE,CAAC,IAAI,EAAE,CAAC;IACvC,IAAI,CAAC,CAAC;QAAE,OAAO,KAAK,CAAC;IACrB,OAAO,IAAI,MAAM,CAAC,MAAM,QAAQ,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;AACxD,CAAC;AAED,kFAAkF;AAClF,MAAM,CAAC,MAAM,eAAe,GAAkB;IAC5C,MAAM,CAAC,KAAK,EAAE,MAAM;QAClB,MAAM,CAAC,GAAG,KAAK,CAAC,WAAW,EAAE,CAAC;QAC9B,MAAM,KAAK,GAAG,IAAI,GAAG,CACnB,CAAC,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,GAAG,CAAC,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAChE,CAAC;QACF,IAAI,IAAI,GAAiB,IAAI,CAAC;QAC9B,IAAI,SAAS,GAAG,CAAC,CAAC;QAClB,KAAK,MAAM,KAAK,IAAI,MAAM,EAAE,CAAC;YAC3B,MAAM,QAAQ,GAAG,GAAG,KAAK,CAAC,WAAW,IAAI,CAAC,KAAK,CAAC,QAAQ,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,WAAW,EAAE,CAAC;YAC1F,MAAM,QAAQ,GAAG,QAAQ,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,GAAG,CAAC,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC;YACxF,IAAI,KAAK,GAAG,CAAC,CAAC;YACd,KAAK,MAAM,CAAC,IAAI,QAAQ;gBAAE,IAAI,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC;oBAAE,KAAK,IAAI,CAAC,CAAC;YACvD,qEAAqE;YACrE,qEAAqE;YACrE,qDAAqD;YACrD,KAAK,MAAM,CAAC,IAAI,KAAK,CAAC,QAAQ,IAAI,EAAE;gBAAE,IAAI,cAAc,CAAC,CAAC,EAAE,CAAC,CAAC;oBAAE,KAAK,IAAI,CAAC,CAAC;YAC3E,IAAI,KAAK,GAAG,SAAS,EAAE,CAAC;gBACtB,SAAS,GAAG,KAAK,CAAC;gBAClB,IAAI,GAAG,KAAK,CAAC;YACf,CAAC;QACH,CAAC;QACD,+DAA+D;QAC/D,OAAO,SAAS,IAAI,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,IAAI,CAAC;IACtC,CAAC;CACF,CAAC;AAEF,MAAM,OAAO,aAAa;IACP,MAAM,GAAY,EAAE,CAAC;IACrB,QAAQ,CAAgB;IAEzC,YAAY,SAAkB,EAAE,EAAE,WAA0B,eAAe;QACzE,IAAI,CAAC,MAAM,GAAG,CAAC,GAAG,MAAM,CAAC,CAAC;QAC1B,IAAI,CAAC,QAAQ,GAAG,QAAQ,CAAC;IAC3B,CAAC;IAED,GAAG,CAAC,KAAY;QACd,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;QACxB,OAAO,IAAI,CAAC;IACd,CAAC;IAED,uEAAuE;IACvE,WAAW,CAAC,QAAgB,EAAE,UAA6B;QACzD,OAAO,IAAI,CAAC,GAAG,CAAC,UAAU,CAAC,QAAQ,EAAE,UAAU,CAAC,CAAC,CAAC;IACpD,CAAC;IAED,yEAAyE;IACzE,UAAU;QACR,OAAO,IAAI,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,CAAC,EAAE,EAAE,CAC/B,CAAC,CAAC,CAAC,UAAU,IAAI,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,EAAE,GAAG,CAAC,EAAE,KAAK,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,CAC3D,CAAC;IACJ,CAAC;IAED,yEAAyE;IACzE,SAAS,CAAC,IAAY,EAAE,KAAc;QACpC,MAAM,IAAI,GAAG,IAAI,CAAC,OAAO,CAAC,eAAe,EAAE,EAAE,CAAC,CAAC;QAC/C,KAAK,MAAM,CAAC,IAAI,IAAI,CAAC,MAAM,EAAE,CAAC;YAC5B,IAAI,KAAK,IAAI,CAAC,CAAC,IAAI,KAAK,KAAK;gBAAE,SAAS;YACxC,MAAM,GAAG,GAAG,CAAC,CAAC,CAAC,UAAU,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,IAAI,IAAI,CAAC,CAAC,IAAI,KAAK,IAAI,CAAC,CAAC;YACjF,IAAI,GAAG;gBAAE,OAAO,GAAG,CAAC;QACtB,CAAC;QACD,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,IAAI;QACF,OAAO,CAAC,GAAG,IAAI,CAAC,MAAM,CAAC,CAAC;IAC1B,CAAC;IAED,GAAG,CAAC,IAAY;QACd,OAAO,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,IAAI,CAAC,CAAC;IAClD,CAAC;IAED,8DAA8D;IAC9D,MAAM,CAAC,KAAa;QAClB,OAAO,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,KAAK,EAAE,IAAI,CAAC,MAAM,CAAC,CAAC;IAClD,CAAC;IAED;;;;OAIG;IACH,OAAO,CAAC,IAAY,EAAE,KAAmB;QACvC,IAAI,CAAC,KAAK;YAAE,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,CAAC;QAEpC,IAAI,MAAM,GAAG,GAAG,IAAI,wBAAwB,KAAK,CAAC,IAAI,KAAK,KAAK,CAAC,YAAY,EAAE,CAAC,IAAI,EAAE,CAAC;QAEvF,2EAA2E;QAC3E,6DAA6D;QAC7D,MAAM,IAAI,GAAG,KAAK,CAAC,UAAU,IAAI,EAAE,CAAC;QACpC,IAAI,IAAI,CAAC,MAAM,EAAE,CAAC;YAChB,MAAM,KAAK,GAAG,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;YACjD,MAAM;gBACJ,mEAAmE,KAAK,IAAI;oBAC5E,+CAA+C,mBAAmB,cAAc;oBAChF,2BAA2B,IAAI,CAAC,CAAC,CAAE,CAAC,IAAI,+BAA+B,CAAC;QAC5E,CAAC;QAED,wEAAwE;QACxE,MAAM,YAAY,GAAG,KAAK,CAAC,KAAK;YAC9B,CAAC,CAAC,IAAI,CAAC,MAAM;gBACX,CAAC,CAAC,CAAC,GAAG,KAAK,CAAC,KAAK,EAAE,mBAAmB,CAAC;gBACvC,CAAC,CAAC,KAAK,CAAC,KAAK;YACf,CAAC,CAAC,SAAS,CAAC;QACd,OAAO,EAAE,MAAM,EAAE,YAAY,EAAE,CAAC;IAClC,CAAC;CACF"}
+{"version":3,"file":"registry.js","sourceRoot":"","sources":["../../src/skills/registry.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAMH,yEAAyE;AACzE,MAAM,CAAC,MAAM,mBAAmB,GAAG,sBAAsB,CAAC;AAE1D;;;;;;;;;;;GAWG;AACH,oEAAoE;AACpE,SAAS,OAAO,CAAC,CAAS;IACxB,MAAM,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,CAAC;IACnB,IAAI,CAAC,CAAC,CAAC,UAAU,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,UAAU,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,EAAE,CAAC;QACrF,OAAO,CAAC,CAAC,KAAK,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC;IACxB,CAAC;IACD,OAAO,CAAC,CAAC;AACX,CAAC;AAED,MAAM,UAAU,UAAU,CAAC,QAAgB,EAAE,UAA6B;IACxE,MAAM,EAAE,GAAG,QAAQ,CAAC,KAAK,CAAC,0CAA0C,CAAC,CAAC;IACtE,MAAM,IAAI,GAA2B,EAAE,CAAC;IACxC,IAAI,IAAI,GAAG,QAAQ,CAAC;IACpB,IAAI,EAAE,EAAE,CAAC;QACP,IAAI,GAAG,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;QACnB,KAAK,MAAM,IAAI,IAAI,CAAC,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC;YAC7C,0EAA0E;YAC1E,0EAA0E;YAC1E,MAAM,CAAC,GAAG,IAAI,CAAC,KAAK,CAAC,uCAAuC,CAAC,CAAC;YAC9D,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;gBAAE,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,CAAC,GAAG,OAAO,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC;QAChE,CAAC;IACH,CAAC;IACD,MAAM,IAAI,GAAG,CAAC,CAAU,EAAE,EAAE,CAC1B,CAAC;QACC,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,MAAM,CAAC,OAAO,CAAC;QACnD,CAAC,CAAC,SAAS,CAAC;IAEhB,IAAI,CAAC,IAAI,CAAC,IAAI;QAAE,MAAM,IAAI,KAAK,CAAC,wCAAwC,CAAC,CAAC;IAE1E,8DAA8D;IAC9D,MAAM,KAAK,GAAG,IAAI,GAAG,CAAC,CAAC,MAAM,EAAE,aAAa,EAAE,OAAO,EAAE,UAAU,CAAC,CAAC,CAAC;IACpE,MAAM,QAAQ,GAA2B,EAAE,CAAC;IAC5C,KAAK,MAAM,CAAC,CAAC,EAAE,CAAC,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,IAAI,CAAC;QAAE,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC;YAAE,QAAQ,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC;IAE9E,OAAO;QACL,IAAI,EAAE,IAAI,CAAC,IAAI;QACf,WAAW,EAAE,IAAI,CAAC,WAAW,IAAI,EAAE;QACnC,YAAY,EAAE,IAAI,CAAC,IAAI,EAAE;QACzB,KAAK,EAAE,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC;QACvB,QAAQ,EAAE,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC;QAC7B,QAAQ,EAAE,MAAM,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,SAAS;QAC7D,UAAU,EAAE,UAAU,IAAI,UAAU,CAAC,MAAM,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,SAAS;KACrE,CAAC;AACJ,CAAC;AAED,0DAA0D;AAC1D,MAAM,SAAS,GAAG,IAAI,GAAG,CAAC;IACxB,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM;IAC1E,MAAM,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,QAAQ,EAAE,OAAO,EAAE,KAAK,EAAE,KAAK;IAC3E,MAAM,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,EAAE,MAAM;CAC/D,CAAC,CAAC;AAEH,qDAAqD;AACrD,SAAS,QAAQ,CAAC,CAAS;IACzB,OAAO,CAAC,CAAC,OAAO,CAAC,qBAAqB,EAAE,MAAM,CAAC,CAAC;AAClD,CAAC;AAED;;;;;GAKG;AACH,SAAS,cAAc,CAAC,KAAa,EAAE,OAAe;IACpD,MAAM,CAAC,GAAG,OAAO,CAAC,WAAW,EAAE,CAAC,IAAI,EAAE,CAAC;IACvC,IAAI,CAAC,CAAC;QAAE,OAAO,KAAK,CAAC;IACrB,OAAO,IAAI,MAAM,CAAC,MAAM,QAAQ,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;AACxD,CAAC;AAED;;;GAGG;AACH,MAAM,CAAC,MAAM,eAAe,GAAkB;IAC5C,MAAM,CAAC,KAAK,EAAE,MAAM;QAClB,MAAM,CAAC,GAAG,KAAK,CAAC,WAAW,EAAE,CAAC;QAC9B,MAAM,KAAK,GAAG,IAAI,GAAG,CACnB,CAAC,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,GAAG,CAAC,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAChE,CAAC;QACF,IAAI,IAAI,GAAiB,IAAI,CAAC;QAC9B,IAAI,SAAS,GAAG,CAAC,CAAC;QAClB,KAAK,MAAM,KAAK,IAAI,MAAM,EAAE,CAAC;YAC3B,MAAM,QAAQ,GAAG,GAAG,KAAK,CAAC,WAAW,IAAI,CAAC,KAAK,CAAC,QAAQ,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,WAAW,EAAE,CAAC;YAC1F,MAAM,QAAQ,GAAG,QAAQ,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,GAAG,CAAC,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC;YACxF,IAAI,KAAK,GAAG,CAAC,CAAC;YACd,KAAK,MAAM,CAAC,IAAI,QAAQ;gBAAE,IAAI,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC;oBAAE,KAAK,IAAI,CAAC,CAAC;YACvD,qEAAqE;YACrE,qEAAqE;YACrE,qDAAqD;YACrD,KAAK,MAAM,CAAC,IAAI,KAAK,CAAC,QAAQ,IAAI,EAAE;gBAAE,IAAI,cAAc,CAAC,CAAC,EAAE,CAAC,CAAC;oBAAE,KAAK,IAAI,CAAC,CAAC;YAE3E,qEAAqE;YACrE,uEAAuE;YACvE,mCAAmC;YACnC,IAAI,2GAA2G,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC;gBACxH,MAAM,SAAS,GAAG,CAAC,KAAK,CAAC,WAAW,GAAG,GAAG,GAAG,CAAC,KAAK,CAAC,QAAQ,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,WAAW,EAAE,CAAC;gBAC7F,IAAI,iGAAiG,CAAC,IAAI,CAAC,SAAS,CAAC;oBAAE,KAAK,IAAI,GAAG,CAAC;YACtI,CAAC;YAED,IAAI,KAAK,GAAG,SAAS,EAAE,CAAC;gBACtB,SAAS,GAAG,KAAK,CAAC;gBAClB,IAAI,GAAG,KAAK,CAAC;YACf,CAAC;QACH,CAAC;QACD,+DAA+D;QAC/D,OAAO,SAAS,IAAI,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,IAAI,CAAC;IACtC,CAAC;CACF,CAAC;AAEF;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,UAAU,4BAA4B,CAC1C,UAA8B,EAC9B,QAA2D,EAAE;IAE7D,mEAAmE;IACnE,oEAAoE;IACpE,iEAAiE;IACjE,kEAAkE;IAClE,kEAAkE;IAClE,KAAK,UAAU,CAAC,CAAC,gDAAgD;IACjE,OAAO,eAAe,CAAC;AACzB,CAAC;AAED,MAAM,OAAO,aAAa;IACP,MAAM,GAAY,EAAE,CAAC;IACrB,QAAQ,CAAgB;IAEzC,YAAY,SAAkB,EAAE,EAAE,WAA0B,eAAe;QACzE,IAAI,CAAC,MAAM,GAAG,CAAC,GAAG,MAAM,CAAC,CAAC;QAC1B,IAAI,CAAC,QAAQ,GAAG,QAAQ,CAAC;IAC3B,CAAC;IAED,GAAG,CAAC,KAAY;QACd,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;QACxB,OAAO,IAAI,CAAC;IACd,CAAC;IAED,uEAAuE;IACvE,WAAW,CAAC,QAAgB,EAAE,UAA6B;QACzD,OAAO,IAAI,CAAC,GAAG,CAAC,UAAU,CAAC,QAAQ,EAAE,UAAU,CAAC,CAAC,CAAC;IACpD,CAAC;IAED,yEAAyE;IACzE,UAAU;QACR,OAAO,IAAI,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,CAAC,EAAE,EAAE,CAC/B,CAAC,CAAC,CAAC,UAAU,IAAI,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,EAAE,GAAG,CAAC,EAAE,KAAK,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,CAC3D,CAAC;IACJ,CAAC;IAED,yEAAyE;IACzE,SAAS,CAAC,IAAY,EAAE,KAAc;QACpC,MAAM,IAAI,GAAG,IAAI,CAAC,OAAO,CAAC,eAAe,EAAE,EAAE,CAAC,CAAC;QAC/C,KAAK,MAAM,CAAC,IAAI,IAAI,CAAC,MAAM,EAAE,CAAC;YAC5B,IAAI,KAAK,IAAI,CAAC,CAAC,IAAI,KAAK,KAAK;gBAAE,SAAS;YACxC,MAAM,GAAG,GAAG,CAAC,CAAC,CAAC,UAAU,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,IAAI,IAAI,CAAC,CAAC,IAAI,KAAK,IAAI,CAAC,CAAC;YACjF,IAAI,GAAG;gBAAE,OAAO,GAAG,CAAC;QACtB,CAAC;QACD,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,IAAI;QACF,OAAO,CAAC,GAAG,IAAI,CAAC,MAAM,CAAC,CAAC;IAC1B,CAAC;IAED,GAAG,CAAC,IAAY;QACd,OAAO,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,IAAI,CAAC,CAAC;IAClD,CAAC;IAED,8DAA8D;IAC9D,MAAM,CAAC,KAAa;QAClB,OAAO,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,KAAK,EAAE,IAAI,CAAC,MAAM,CAAC,CAAC;IAClD,CAAC;IAED;;;;OAIG;IACH,OAAO,CAAC,IAAY,EAAE,KAAmB;QACvC,IAAI,CAAC,KAAK;YAAE,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,CAAC;QAEpC,IAAI,MAAM,GAAG,GAAG,IAAI,wBAAwB,KAAK,CAAC,IAAI,KAAK,KAAK,CAAC,YAAY,EAAE,CAAC,IAAI,EAAE,CAAC;QAEvF,2EAA2E;QAC3E,6DAA6D;QAC7D,MAAM,IAAI,GAAG,KAAK,CAAC,UAAU,IAAI,EAAE,CAAC;QACpC,IAAI,IAAI,CAAC,MAAM,EAAE,CAAC;YAChB,MAAM,KAAK,GAAG,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;YACjD,MAAM;gBACJ,mEAAmE,KAAK,IAAI;oBAC5E,+CAA+C,mBAAmB,cAAc;oBAChF,2BAA2B,IAAI,CAAC,CAAC,CAAE,CAAC,IAAI,+BAA+B,CAAC;QAC5E,CAAC;QAED,wEAAwE;QACxE,MAAM,YAAY,GAAG,KAAK,CAAC,KAAK;YAC9B,CAAC,CAAC,IAAI,CAAC,MAAM;gBACX,CAAC,CAAC,CAAC,GAAG,KAAK,CAAC,KAAK,EAAE,mBAAmB,CAAC;gBACvC,CAAC,CAAC,KAAK,CAAC,KAAK;YACf,CAAC,CAAC,SAAS,CAAC;QACd,OAAO,EAAE,MAAM,EAAE,YAAY,EAAE,CAAC;IAClC,CAAC;CACF"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kaleidorg/mind",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "Local-first reasoning + function-calling engine for KaleidoSwap. QVAC-powered.",
   "license": "Apache-2.0",
   "type": "module",

package/skills/README.md

@@ -75,5 +75,8 @@ Then per query: `const skill = registry.select(query)` →
   tools (in-process WDK on mobile, MCP on desktop).
 - **merchant-finder/** — find Bitcoin-accepting merchants via BTC Map. Live
   data when the host injects a fetch + location; bundled offline list otherwise.
+  Intentionally model-leveraging (updated playbook + pluggable selectors) for
+  natural language understanding of vague location queries, context use,
+  post-processing results, and hybrid RAG.
 - **paid-data/** — fetch L402-paywalled resources via `fetch_paid_resource`.
 - **kaleido-trading/** — prices, quotes, atomic swaps, LSP channels.

package/skills/kaleido-lsps/SKILL.md

@@ -1,56 +1,114 @@
 ---
 name: kaleido-lsps
-description: "Buy inbound Lightning channel capacity from a Lightning Service Provider (LSPS1). Quote, estimate fees, and create a channel order. Triggers when the user wants inbound liquidity, can't receive a payment, needs a channel, or asks about LSP fees."
-tools: lsp_get_info, lsp_get_network_info, lsp_estimate_fees, lsp_create_order, lsp_get_order
-triggers: inbound, liquidity, channel order, lsp, lsps1, receive limit, can't receive, open channel
+description: "Buy inbound Lightning channel capacity from a Lightning Service Provider (LSPS1). Quote a channel, estimate fees, place a channel order, and check order status. Triggers when the user wants inbound liquidity, says they can't receive a payment, needs a channel, asks about LSP fees, or wants to check the status of a channel order / LSP order."
+tools: lsp_get_info, lsp_get_network_info, lsp_estimate_fees, lsp_create_order, lsp_get_order, rln_get_node_info, rln_pay_invoice
+triggers: inbound, liquidity, channel order, lsp, lsps1, receive limit, can't receive, open channel, channel from, check status, order status, check the order, channel status, lsp status, check my channel
 metadata:
   author: kaleidoswap
-  version: "0.1.0"
+  version: "0.2.0"
 ---
 
 # Lightning channel orders (LSPS1)
 
 Buy inbound Lightning channel capacity from a Lightning Service Provider when
-the user can't receive a payment (no inbound liquidity) or wants a bigger
-receive limit. The host binds these to whichever LSP it talks to — the
-KaleidoSwap maker by default, but the contract is LSP-agnostic (`lsp_*`).
+the user can't receive a payment, wants a bigger receive limit, or just wants
+to open a new channel from the LSP. The host binds these to whichever LSP it
+talks to — the KaleidoSwap maker by default. Tool names are LSP-agnostic
+(`lsp_*`), so the same skill works against any LSPS1-compliant LSP.
 
-## Critical rules
+## Critical rules — these override everything else
 
-You have **no knowledge of LSP fees, channel sizes, or order status**. Every
-number, capacity, fee, or order id in your reply MUST come from a tool result
-returned in the CURRENT turn. Never quote a fee from memory. Never claim an
-order completed without calling `lsp_get_order`. Never reuse a number from a
-previous turn.
+You have **no knowledge** of LSP capabilities, fees, channel sizes, or order
+status. Every number, capacity, fee, order id, or invoice in your reply MUST
+come from a tool result returned in the CURRENT turn. Never quote a fee from
+memory. Never claim an order completed without calling `lsp_get_order`.
+Never reuse a number from a previous turn.
 
 **Calling the tool IS the answer.** Don't write "the LSP info is fetched with
-`lsp_get_info`" — call it.
-
-If a tool needs a required argument the user didn't give (e.g. an `order_id`
-when polling), ASK. Don't loop the same failing call.
-
-## Flow
-
-1. **Check the LSP first.** Call `lsp_get_info` once per session to learn the
-   min/max channel size and the fee structure. Use those numbers to validate
-   the user's request (e.g. "200k sats" against `min_channel_sat`).
-2. **Estimate before ordering.** Call `lsp_estimate_fees` with the desired
-   `lsp_balance_sat`. Surface the total cost explicitly — never hide it.
-3. **Show + confirm.** State: inbound capacity requested, total fee, expiry
-   (if applicable), and the LSP node URI from `lsp_get_network_info` (so the
-   user knows the counterparty). The next step is spend-gated.
-4. **Create the order.** Call `lsp_create_order` with the same parameters.
-   The host pauses for explicit confirmation. Returns an `order_id` and a
-   Lightning invoice the user must pay to lock the order.
-5. **Track it.** Poll `lsp_get_order` until the channel opens (status
-   `completed`) or fails. Report the outcome plainly.
-
-## Rules
-
-- **Re-estimate when parameters change.** Don't reuse an estimate across
-  different channel sizes or expiries.
-- **Never invent capacity / fees / pubkeys.** Tool results are the truth.
-- **Lightning over on-chain for ordering.** LSPS1 orders are paid by
-  Lightning invoice; if Lightning isn't available, say so and stop.
-- **A channel order is not the same as a payment.** Make this explicit when
-  the user confuses them.
+`lsp_get_info`" — call it. Don't reveal tool names in your reply; describe
+what you're doing in plain language.
+
+If a tool needs a required argument the user didn't give (e.g. `client_pubkey`
+when creating an order — get it from `rln_get_node_info`), resolve it via the
+appropriate read tool. Don't ask the user for a pubkey.
+
+## Asset codes
+
+The same conventions as trading apply:
+- `BTC` (sats) — the default for "inbound liquidity" / "channel capacity".
+- `USDT` / `XAUT` — for RGB asset channels (uses `asset_id` + `lsp_asset_amount`).
+
+## Tools and the flow
+
+### Step 1 — `lsp_get_info`
+No args. Returns the LSP's `OrderOptions` (min/max channel size, min/max
+expiry, etc.) and the `assets` list. **Call it once before estimating** so you
+can validate the user's request against the LSP's limits.
+
+If the user wants 1M sats inbound but `max_initial_lsp_balance_sat` is 500k,
+say so plainly and offer the maximum — don't push through and let the maker
+reject it.
+
+### Step 2 — `lsp_estimate_fees` (read-only)
+Required args: `lsp_balance_sat`, `client_balance_sat`, `channel_expiry_blocks`.
+
+Defaults you can use silently if the user didn't specify:
+- `client_balance_sat: 0` (pure inbound order — most common)
+- `channel_expiry_blocks: 4320` (~30 days)
+
+Returns `{setup_fee, capacity_fee, duration_fee, total_fee}` — surface
+`total_fee` to the user and the breakdown when relevant.
+
+### Step 3 — `rln_get_node_info`
+No args. Returns `{pubkey, ...}`. **Pubkey is required by `lsp_create_order` —
+fetch it deterministically. Never invent a pubkey.**
+
+### Step 4 — `lsp_create_order` 🔒 spend
+Required args: `client_pubkey` (from step 3), `lsp_balance_sat`. The maker
+also expects `client_balance_sat`, `required_channel_confirmations`,
+`funding_confirms_within_blocks`, `channel_expiry_blocks`, `announce_channel`
+— the host adapter fills sensible defaults (1, 6, 4320, true) when the user
+didn't specify, so just pass the values the user actually named.
+
+Returns:
+- `order_id`
+- `access_token` (save it — required for `lsp_get_order`)
+- `payment.bolt11.invoice` — Lightning invoice to pay
+- `payment.bolt11.order_total_sat` — the sats that need to flow
+- `payment.onchain.address` — optional on-chain fallback
+- `order_state: "CREATED"`
+
+### Step 5 — Pay the invoice with `rln_pay_invoice`
+Hand the `payment.bolt11.invoice` to `rln_pay_invoice`. This is a separate
+spend gate at the wallet contract; the user confirms paying the LSP.
+
+### Step 6 — `lsp_get_order` (poll)
+**Args: `order_id`, `access_token` (BOTH required — never omit either).**
+`order_state` progresses `CREATED → CHANNEL_OPENING → COMPLETED` (or `FAILED`).
+Poll until terminal. Always pass the exact order_id and access_token from the
+previous `lsp_create_order` result (or from the summary that listed them).
+Report the outcome plainly with the new channel id from `channel.channel_id` if present.
+
+## Don'ts
+
+- Don't invent capacity, fees, pubkeys, order_ids, or invoices.
+- Don't reuse a number from a previous turn — re-estimate when parameters
+  change (different size or expiry).
+- Don't describe how a tool works — call it.
+- Don't pay a Lightning invoice without confirming the amount + LSP — the
+  spend gate at `rln_pay_invoice` shows the user the destination.
+- Don't claim an order completed without polling `lsp_get_order` with BOTH
+  `order_id` and `access_token` and seeing `order_state: COMPLETED`.
+- Never call `lsp_get_order` with only the access_token or only the order_id.
+  Always extract the exact values from the previous turn's summary (the one that
+  said "order_id=... access_token=...") and pass them as separate arguments.
+- Don't ask the user for their node pubkey — fetch it from `rln_get_node_info`.
+
+## When the deterministic recipe handles it
+
+For requests like "I need 500k inbound" or "buy a channel from the LSP", the
+`kaleidoswap-channel-order` recipe drives the whole chain (get_info →
+estimate_fees → get_node_info → create_order → pay_invoice) with a single
+confirmation gate showing the real fee. Use the agentic flow here only when
+the recipe didn't fire — typically for read-only questions ("what does the
+LSP offer?") or partial flows ("estimate fees for 200k inbound").

package/skills/kaleido-trading/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: kaleido-trading
-description: "Trade on KaleidoSwap — quote and execute swaps between BTC and RGB assets (USDT, XAUT). Get assets and pairs, pull an executable quote, place a market order, or track an atomic swap end-to-end. Triggers when the user wants a price, a quote, to swap or trade assets, or to rebalance between BTC and stablecoins."
-tools: get_price, fiat_to_sats, kaleidoswap_get_assets, kaleidoswap_get_pairs, kaleidoswap_get_quote, kaleidoswap_get_nodeinfo, kaleidoswap_place_order, kaleidoswap_get_order_status, kaleidoswap_get_order_history
+description: "Trade on KaleidoSwap — quote and execute swaps between BTC and RGB assets (USDT, XAUT). Get assets and pairs, pull an executable quote, place a market order, or track an atomic swap end-to-end. Triggers when the user wants a quote, to swap or trade assets, or to rebalance between BTC and stablecoins."
+tools: kaleidoswap_get_assets, kaleidoswap_get_pairs, kaleidoswap_get_quote, kaleidoswap_get_nodeinfo, kaleidoswap_place_order, kaleidoswap_get_order_status, kaleidoswap_get_order_history
 triggers: quote, swap, trade, rebalance, slippage, pair, pairs, usdt, xaut, kaleidoswap, rfq
 metadata:
   author: kaleidoswap
-  version: "0.3.0"
+  version: "0.4.0"
 ---
 
 # KaleidoSwap trading
@@ -20,10 +20,9 @@ You have **no knowledge** of any price, quote, fee, pair, or order. Every
 number, pair, or quote id in your reply MUST come from a tool result returned
 in the CURRENT turn:
 
-- "What's the BTC price?" → call `get_price` and state the number it returns.
 - "What pairs are listed?" → call `kaleidoswap_get_pairs` and list them.
 - "Quote 100k sats to USDT" → call `kaleidoswap_get_quote(BTC, USDT, 100000)`,
-  then state the receive amount + fees from the result.
+  then state the receive amount + fee from the result.
 
 **Calling the tool IS the answer.** Never write "the pairs are listed using
 kaleidoswap_get_pairs" or "the function returns the quote" — just call it.
@@ -31,9 +30,14 @@ kaleidoswap_get_pairs" or "the function returns the quote" — just call it.
 **Never reuse a number across turns.** If the user asks a new question, the
 previous turn's quote, price, or fee is irrelevant — fetch fresh.
 
-**Never invent a quote.** Without a `quote_id` and `receive_amount` returned
+**Never invent a quote.** Without an `rfq_id` and a `to_asset.amount` returned
 this turn, you do not have a quote. Say so and re-quote.
 
+This skill is for tradeable pair quotes on the maker. It does NOT do generic
+"what is bitcoin worth in USD" spot prices — that's the wallet's job. If the
+user asks for a plain BTC price (not a swap), say you can quote a swap and ask
+which pair + amount.
+
 ## Asset codes (canonical)
 
 Only these codes are accepted:
@@ -52,47 +56,93 @@ Use when the user asks "what can I trade", "list pairs", "what's available",
 or before quoting an unfamiliar pair.
 
 ### `kaleidoswap_get_quote` — REQUIRES `amount`
-Required args: `from_asset` AND `to_asset` AND `amount`. The maker rejects
-calls missing any of these.
-
-**If the user didn't give an amount, ASK for it. Do not call the tool with
-from/to alone.**
-
-Examples:
-- "Quote 100k sats to USDT" → `{from_asset: "BTC", to_asset: "USDT", amount: 100000}`
-- "What's the USDT/BTC rate?" → ask: "How many USDT do you want to swap?"
-  (no amount → no quote possible).
-- "Buy 50 USDT of BTC" → `{from_asset: "USDT", to_asset: "BTC", amount: 50}`
-  (USDT is what's being spent).
+Required args: `from_asset` AND `to_asset` AND `amount`. The maker rejects a
+quote that has no amount.
+
+**If the user didn't give an amount, ASK for it. Do NOT call the tool with
+from/to alone, and do NOT make up an amount.**
+
+`amount` is in the smallest unit of `from_asset`. Use the EXACT number the user
+typed (scaled if they used "k"/"m"/"M" shorthand: 100k → 100000, 2m → 2000000).
+**Never** copy an amount from a previous turn or from these instructions.
+
+Critical unit-and-leg anchor:
+- If the user says **sats** or **satoshis** anywhere, the BTC leg is implied
+  (sats = the smallest unit of BTC). `BTC` is always `from_asset` OR `to_asset`
+  depending on the verb.
+- "X sats TO Y" → `from_asset: "BTC"`, `to_asset: "Y"`, `amount: X-as-sats`.
+- "X Y TO BTC" (Y ∈ {USDT, XAUT}) → `from_asset: "Y"`, `to_asset: "BTC"`,
+  `amount: X-in-Y-units`.
+- "buy Z of A with B" → spent = B → `from_asset: "B"`, received = A → `to_asset: "A"`,
+  `amount: <amount of B the user wants to spend>`.
+- "rate of X to Y" with NO number → no amount → ASK: "How much do you want to
+  swap?" → do NOT call the tool yet.
+
+### Reading the quote response
+
+`kaleidoswap_get_quote` returns ready-to-read display fields — **use them
+verbatim. Do NOT do any arithmetic yourself.** The response looks like:
+
+```
+{
+  "rfq_id": "<id>",
+  "from_amount_display": "100,000 BTC-sats",   ← what the user spends
+  "to_amount_display":   "0.063176 USDT",       ← what the user receives
+  "fee_display":         "0.000638 USDT",        ← the fee
+  "expires_at": <epoch>,
+  ...raw numeric fields you should ignore...
+}
+```
+
+To state the answer, copy the strings:
+- Receive amount → `to_amount_display`.
+- Fee → `fee_display`.
+- `rfq_id` is the quote handle (needed to place the swap), short-lived (~60s) —
+  mention it expires soon.
+
+**Read `to_amount_display` / `fee_display` exactly as given.** Do NOT compute
+`amount ÷ 10^precision`, do NOT restate the raw `price`/`amount` integers, and
+do NOT copy the numbers from this document — they are placeholders. The only
+correct numbers are the `*_display` strings in the CURRENT tool result.
+
+A good reply: *"100,000 sats → <to_amount_display> (fee <fee_display>). Quote
+<rfq_id> is valid ~60s — want me to place it?"*
 
 ### `kaleidoswap_place_order(quote_id)` 🔒 spend
-Only after `kaleidoswap_get_quote` returned a `quote_id` THIS turn, and only
-when the user has explicitly approved the amount + direction.
+Only after `kaleidoswap_get_quote` returned an `rfq_id` THIS turn, and only when
+the user has explicitly approved the amount + direction. Pass the `rfq_id` as
+`quote_id`.
+
+**Save the `order_id` AND `access_token` from the result** — you will need both
+for polling status later.
 
-### `kaleidoswap_get_order_status(order_id)`
-Poll after placing an order. Report status plainly — pending, settling,
+### `kaleidoswap_get_order_status(order_id, access_token)`
+Poll after placing an order. **Pass both the order_id and the access_token**
+(saved from place_order). Report status plainly — pending, settling,
 completed, failed.
 
 ## Flow
 
 1. **Pick a pair** — skip when obvious (`BTC/USDT`, `BTC/XAUT`).
-2. **Quote** — `kaleidoswap_get_quote`. REQUIRES amount.
-3. **Show + confirm** — surface pair, direction, amount in, expected out,
-   fees, slippage. **Never hide cost** — a small model must not abbreviate
-   fees out of the message.
+2. **Quote** — `kaleidoswap_get_quote`. REQUIRES amount; ask if missing.
+3. **Read + present** — compute the receive amount + fee from the response (see
+   "Reading the quote response"). **Never hide cost.**
 4. **Place** — spend-gated by the engine. The host pauses for the user.
-5. **Track** — poll `kaleidoswap_get_order_status` until it terminates.
+5. **Track** — poll `kaleidoswap_get_order_status(order_id, access_token)` (use both values saved from place_order) until it terminates.
 
 ## Don'ts
 
-- Don't invent prices, quotes, quote_ids, or order_ids.
+- Don't invent prices, quotes, rfq_ids, or order_ids.
 - Don't reuse a number from a previous turn.
 - Don't describe how a tool works — call it.
 - Don't call `kaleidoswap_get_quote` with from/to only — ask for the amount.
+- Don't make up an amount the user didn't give.
+- Don't do unit math or restate raw integers — read the `*_display` strings.
+- Don't copy numbers from the skill docs — only the current tool result is real.
 - Don't accept `XAU` as `XAUT` or `USD` as `USDT` silently — confirm.
 - Don't retry the same failing tool call in a loop. If a call fails, read the
   error and either ask the user, fix the args, or stop.
 
-For the atomic-swap flow (trust-minimised cross-asset swap that the maker
-can't settle from balance), use the `kaleido-trading` atomic recipe — the
-agentic chain is not safe to plan on a 0.6B model.
+For the full atomic-swap flow (init → whitelist on the RGB node → execute), a
+deterministic recipe drives the chain — the agentic loop is not safe to plan a
+multi-step, two-service swap on a small model.

package/skills/merchant-finder/SKILL.md

@@ -1,87 +1,117 @@
 ---
 name: merchant-finder
-description: "Find Bitcoin-accepting merchants near the user using live BTC Map data and the device's real location. Triggers when the user asks where to spend Bitcoin, for a shop, store, restaurant, cafe, bar, or ATM that accepts Bitcoin, or for merchants nearby."
-tools: find_merchant_locations, get_merchant_info
-triggers: merchant, merchants, shop, shops, store, stores, restaurant, restaurants, cafe, cafes, bar, bars, atm, atms, accept, accepts, accepting, nearby, near me, around, place, places, spend, find, pizza, food, coffee, bitcoin map, btcmap
+description: "Find Bitcoin-accepting merchants near the user using live BTC Map data and the device's real location. Triggers when the user asks where to spend Bitcoin, buy pizza/food with sats or bitcoin, eat at restaurants/cafes paying with sats, for a shop, store, restaurant, cafe, bar, or ATM that accepts Bitcoin, or for merchants nearby or in a city like turin."
+tools: find_merchant_locations
+triggers: merchant, merchants, shop, shops, store, stores, restaurant, restaurants, cafe, cafes, bar, bars, atm, atms, accept, accepts, accepting, nearby, near me, around, place, places, spend, find, pizza, pizz, food, coffee, eat, dinner, lunch, buy, bitcoin map, btcmap
 metadata:
   author: kaleidoswap
-  version: "0.2.0"
+  version: "0.3.0"
   homepage: "https://btcmap.org"
 ---
 
 # Merchant finder
 
 Discover places that accept Bitcoin payments — cafés, restaurants, bars, shops,
-and ATMs. Live BTC Map data when the host injects a fetcher + location;
-otherwise a small offline list keeps the skill answerable.
-
-## Critical rule — never answer from memory
-
-You have **no knowledge of any merchant**. Every place, name, address and
-distance in your reply MUST come from a `find_merchant_locations` result
-returned in the CURRENT turn. **Call `find_merchant_locations` for every
-place question**, even if a similar question was answered earlier — do NOT
-reuse or adapt a previous answer. Never invent a merchant.
-
-## How to call the tools
-
-1. **Start with `find_merchant_locations`.** Pass ONLY the fields the user
-   actually named — do not invent constraints:
-
-   - `query` — a specific thing the user named (e.g. `"tapas"`, `"coffee"`,
-     `"pizza"`). Omit when they only said "near me" or only named a place.
-
-   - `category` — must be EXACTLY one of: `restaurant`, `cafe`, `bar`, `shop`,
-     `grocery`, `lodging`, `atm`. **Anything else is invalid — leave it empty.**
-     The words "merchant", "merchants", "place", "places", "store", "stores"
-     are NOT categories — they're the generic noun for what you're searching
-     for, so they belong in `query` at best, never in `category`.
-
-   - `near_address` — a city, neighbourhood, or address (e.g. `"Milan"`,
-     `"Bitcoin Beach, El Salvador"`). Use this any time the user names a
-     location instead of "near me".
-
-   - `radius_km` — **omit unless the user names a specific number.** The
-     default (5 km) is a sensible search radius for a city. Don't pick a
-     small radius (1, 2, 3) yourself — city-wide searches need 5+.
-
-   - `limit` — 1–20, default 10. Omit unless the user names a count.
-
-   Examples (positive):
-   - "where can I spend btc near me" → `find_merchant_locations({})`
-   - "find merchants in Milan" → `find_merchant_locations({ near_address: "Milan" })`
-     ↑ no `category` — "merchants" is NOT a category.
-   - "cafes in Lisbon" → `find_merchant_locations({ category: "cafe", near_address: "Lisbon" })`
-   - "pizza places in Switzerland that take bitcoin" →
-     `find_merchant_locations({ query: "pizza", near_address: "Switzerland" })`
-     ↑ "places" is NOT a category — pizza goes in `query`.
-   - "lightning bars in NYC, within 2 km" →
-     `find_merchant_locations({ category: "bar", near_address: "New York", radius_km: 2 })`
-     ↑ user explicitly said "2 km" → set radius_km.
-
-   Examples (anti — do NOT do these):
-   - ❌ `category: "merchant"` (not a category)
-   - ❌ `category: "place"` (not a category)
-   - ❌ `radius_km: 2` when the user didn't say "2 km" — you're picking a
-     too-small radius and the result will be empty.
+and ATMs. **Live BTC Map data only** — when the host has not injected a fetcher
+or cannot resolve a location, the tool returns `{success:false, error}`; relay
+that error to the user verbatim instead of inventing places.
+
+## Critical rules (read first)
+
+1. **Never answer from memory.** You have NO knowledge of any merchant. Every
+   place, name, address and distance in your reply MUST come from a
+   result returned by the merchant search tool in the CURRENT turn. Use the
+   merchant search tool for every place question, even if a similar one
+   was answered earlier — do NOT reuse a previous answer. Never invent a
+   merchant. Do not mention the exact name of the tool in your text reply
+   to the user.
+2. **List, don't pick.** A "where can I…" / "find merchants" question is a
+   LIST question. Show every merchant the tool returned (cap at the first ~5
+   if there are many), ONE LINE EACH. Never collapse a list of 10 to one
+   example. The host's "keep replies short" guidance applies to prose, not to
+   a list the user explicitly asked for.
+3. **Prefer minimal arguments; use understanding when mapping.** When the user
+   speaks naturally, map their words to the available fields intelligently but
+   conservatively. When in doubt, pass FEWER fields rather than guessing. The
+   tool and the live data (plus any RAG hits you also fetch) are the source of
+   truth — your job is to get the right starting call and then reason over
+   what comes back.
+
+## Using your understanding (the model is meant to help here)
+
+- Translate vague or natural language into the best minimal call:
+  - "coffee near the station", "grab a bite", "something to eat" → `query: "coffee"` or `"food"` / `"pizza"` (or leave descriptive terms in `query`); consider `category: "cafe"` or `"restaurant"` only when it clearly fits one of the allowed values.
+  - "near me for lunch" or "around here" → start with empty or just a broad `query`; let the device location do the work. You may infer a reasonable city from prior turns ("you mentioned Lugano earlier") and pass `near_address`.
+  - "ATMs or shops that take lightning" → `query: "atm"` or separate calls, or put "atm shop lightning" in `query`.
+  - "the cheaper ones", "with websites", "open late", "good for dinner" → use the tool first (possibly broad), then in the same or follow-up turn use the returned list + any other context/memory to filter, rank or describe. Do not fabricate entries.
+  - **Critical for currency terms**: "where can I spend sats in turin", "bitcoin merchants in X", "places that accept crypto" are generic spend requests. **Do not** put "sats", "btc", "bitcoin", "spend" into `query` or invent a `category` (e.g. "shop"). Use only `near_address` (or empty). Putting currency words in query almost always returns zero results because the data source already only contains Bitcoin-accepting places.
+
+- Multi-turn and post-processing: After the merchant search tool returns a list you may (and should) reason over it: rank by distance or relevance to the user's phrasing, surface `phone`/`website`/`opening_hours` when present, note accepts_lightning, suggest next actions ("want directions or to check one?"), or combine with `search_knowledge` / memory results if merchants have been ingested for the area.
+
+- Hybrid live + RAG: If a `search_knowledge` tool is available and a merchant corpus is loaded, you can use both the live finder (for freshness + distance) and search for background on an area or previously-seen places. Present live results as the actionable list.
+
+- Context is fair game for *formulating the call or summarizing results* (e.g. previous city mentioned, user's preference for Lightning). It is never a substitute for calling the tool for the actual current list of places.
+
+## How to call the tool
+
+1. **Start with the merchant search tool.** Map the user's words to fields using the guidance above. The schema accepts:
+
+   - `query` — free-text the user effectively named or implied (e.g. "coffee", "pizza", "food", "tapas", "atm"). Good place for terms that don't match a strict category. **Omit entirely** for generic "spend sats", "where can I spend", "merchants", "places to spend bitcoin", or "accept crypto". **Never** put "sats", "sat", "bitcoin", "btc", "crypto", "spend", or similar currency/verb terms here — the data source is already Bitcoin-only and this will usually return zero results.
+
+   - `category` — **exactly one** of the allowed values when it fits cleanly: `restaurant`, `cafe`, `bar`, `shop`, `grocery`, `lodging`, `atm`. Leave empty otherwise. **For any generic "spend sats / where can I spend bitcoin / merchants in X" request, leave category empty.** Do not guess a category just because the user wants to spend. Generic nouns like "merchant", "place", "store" belong in `query` (or omitted), never as the category.
+
+   - `near_address` — city / neighborhood / address when the user named a place instead of (or in addition to) "near me". The host will geocode it.
+
+   - `radius_km` — only when the user gave a specific distance ("within 2 km"). Default (5 km) is already reasonable for a city; the backend applies a sensible bound.
+
+   - `limit` — only when the user named a count (1–20).
+
+   Positive examples (using understanding):
+   - "where can I spend btc near me" → use the tool with `{}`
+   - "where can I spend sats in turin" → use the tool with `{ near_address: "Turin" }`   ← generic spend → minimal args, no query, no category
+   - "where can I spend btc in Lugano" → use the tool with `{ near_address: "Lugano" }`
+   - "cafes in Lisbon" → use the tool with `{ category: "cafe", near_address: "Lisbon" }`
+   - "pizza places in Switzerland that take bitcoin" → use the tool with `{ query: "pizza", near_address: "Switzerland" }`
+   - "lightning bars in NYC, within 2 km" → use the tool with `{ category: "bar", near_address: "New York", radius_km: 2 }`
+   - "coffee near the station" or "grab a bite around here" → use the tool with `{ query: "coffee" }` or `{ query: "food" }` (let location come from device or prior context)
+   - "ATMs or shops that take sats in the center" → first use the tool with `query: "atm shop"` + appropriate near_address; then reason over results.
+
+   Things that are still wrong (schema or data reasons):
+   - `category: "merchant"` or `"place"` (invalid per schema).
+   - `query: "sats"`, `"btc"`, `"bitcoin"`, or any currency/spend verb (the dataset is already Bitcoin-only; these filters return nothing or almost nothing useful. "Spend sats" is a generic merchant request, not a filter term).
+   - Guessing a tiny `radius_km` the user never mentioned (results will be empty).
+   - Inventing a `category` (like "shop") for a completely generic "where can I spend sats" query — use no category and let the data speak.
+   - Adding constraints the user did not name when a minimal call would have returned more relevant places.
+
+   **Real bad example that causes zero results**:
+   - "where can I spend sats in turin" → bad: use query "sats" + category "shop"
+     ( "sats" in query + guessed category over-filters everything; correct is just the near_address or nothing).
 
 2. **Present the results.** Each row carries:
    - `name`, `category`, `address`
    - `distance_m` when present — show in metres or km
    - `accepts_bitcoin` / `accepts_lightning` — relevant because Lightning is
      fastest for small payments
-   - `phone`, `website`, `opening_hours` when present — surface if asked
+   - `phone`, `website`, `opening_hours` when present — surface if asked or relevant
 
-3. **Use `get_merchant_info` only when** the user asks for more detail on one
-   specific result. Pass `merchant_id` (preferred) or `merchant_name`.
+3. **Handling failures.** If the tool returns `{success:false, error}`, relay
+   the error as-is and stop. Common cases:
+   - "Merchant search is unavailable…" → the host has no BTC Map adapter.
+   - "Could not locate \"X\"…" → geocoding failed; ask the user for a nearby
+     city or check the spelling.
+   - "Could not determine your location…" → no `near_address` was passed and
+     the device has no GPS / default location.
+
+   Do NOT retry with invented data, and do NOT pretend you know merchants in
+   the area. There is no offline fallback — a failure means no data.
 
 ## Reply style
 
-- Be concise. One line per merchant works:
+- **List, don't fabricate.** Show the merchants the tool actually returned (first ~5–8 is fine for long lists), one line each. You may add a short prose lead or helpful follow-up ("These are sorted by distance. The first two have websites.") but the names, categories, addresses and distances must come from the tool result in this turn.
+- One line per merchant (example):
   `Name — category, address (X m away, accepts: lightning, onchain)`.
-- If the result `source` is `offline`, say so plainly — it means the live
-  BTC Map fetch wasn't available, so the list is limited.
-- If `find_merchant_locations` returns zero merchants, say so — don't invent
-  places. Suggest widening `radius_km` or trying `near_address`.
-- When the user says "near me" and `precise_location` is false, mention which
-  fallback location was used so they know it's not their actual GPS.
+- If zero merchants: say so plainly. Suggest widening radius or trying a `near_address`. Do not invent alternatives.
+- When `precise_location` is false for a "near me" result, mention the fallback area that was used.
+- After showing the list you are free to reason, rank, or ask a clarifying follow-up using the data + conversation context.
+
+**Remember**: the live merchant search tool (plus any RAG merchant documents you also search) are the only sources of place information. Your value is excellent intent → arg mapping on the way in, and helpful reasoning / presentation on the way out. Do not name the tool in your user-facing reply.