settingsmeta.json entry to accept either: http URL for a custom AIML file, or a large freeform text box where AIML source is pasted.
Once per skill load, retrieve the AIML file, validate contents, and then copy to ./aiml/_usercustom.aiml
Just limiting it to one file shouldn't be a big deal, nothing stopping a user from mashing together a few different topics if they wanted it to.
Its not a total point-and-click level of intuitive interface, but it does lighten the burden on users not quite ready for ssh/sftp type stuff.
Later, could be coordinated with some kind of skill that "learns" "facts" which is really just generating formatted AIML category elements and writing them out to a staged file that is eventually written to location retrievable via settings.json spec.
Just limiting it to one file shouldn't be a big deal, nothing stopping a user from mashing together a few different topics if they wanted it to.
Its not a total point-and-click level of intuitive interface, but it does lighten the burden on users not quite ready for ssh/sftp type stuff.
Later, could be coordinated with some kind of skill that "learns" "facts" which is really just generating formatted AIML category elements and writing them out to a staged file that is eventually written to location retrievable via settings.json spec.