documentation
documentation copied to clipboard
Mycroft.AI documentation for all public facing technical components.
For an unknown reason, I had an issue with the order of the adds_context and removes_context when working with the "Using context to enable Intents" part of the "conversational-context.md" guide...
I've been looking around and haven't found a document that seems to detail what a dev should do to make thier skills compatible with MSM. Can we get a link...
The section [Add a Git submodule for your Skill](https://mycroft.ai/documentation/skills/skill-submission/#add-a-git-submodule-for-your-skill) should be updated as it does not completely agree with or reflect confirmed naming standard for skills. Authoritative references: https://github.com/MycroftAI/mycroft-skills#4-add-your-skill-as-a-submodule https://community.mycroft.ai/t/skill-naming-format/2349/5
Mycroft has an internal event scheduler mechanism, referred to in this forum discussion: https://community.mycroft.ai/t/running-background-processes-with-skills/2986/4?u=jrwarwick Would benefit greatly from general introduction, "does-and-don'ts" for usage, some simple examples. For now, it looks...
The [description of the dialog directory and its contents](https://mycroft.ai/documentation/skills/introduction-developing-skills/#dialog-directory) does a good job of introducing basic mechanism and parts and illustrating usage, but it makes no mention of the double-curly-brace...
## Provide documentation on naming packages and skills with the word 'Mycroft' From @zackwelch in Mycroft Chat: > An official prohibition of plug-in or add-on packages from using "mycroft" in...
the language support docs make a few wrong assumptions: - wakeword must be in new language - pocketsphinx models must be downloaded - pocketsphinx offline STT prs must be merged...
The pages that describe signing up for a Mycroft account need to document clearly: (1) why Mycroft needs to have an account on some server outside the home, (2) exactly...