I was working on a new skill today for Jibo and I realized that many of the features could easily be missed by a new or novice user. I thought how nice it would be if Jibo could always be available to help the user in case they don’t know what’s available in a particular skill.
So my suggestion is that the Jibo Store require developers to provide a both a brief and an extended help dialogue for their skills, likely in the form of a subflow or subtree.
The brief help would be available anytime to offer up a simple description and a handful of the most common commands a skill uses. It could be automatically played when Jibo first installs the skill, or optionally by the skill itself for new family members or friends. Additionally it could be accessible at anytime if the user requests more info, e.g. “Hey Jibo, what can your 7-Minute Workout skill do?” (shameless plug). It would be no longer than 20 seconds in running time.
The extended help would be more like a guided tour of the skill, offering a more detailed description and a thorough list of commands available in the skill. It would be no longer than 2 minutes seconds in running time, but could also have additional interaction, e.g. nested queries.
Not only would this requirement inherently raise the value of all skills, but it would also make the user experience much better, especially for new users. Finally, it would have the added benefit of consistency across the platform, always giving the user a “road map” while navigating the skills.
It may be a little extra works for the developers, but it would go a long way in making Jibo a better robot.
If this is something that others agree with, I’d be happy to create a quick example template for each of the helpers.