Skill Creators Update

[philipp2310]

This is a collection of ideas that should (but don't have to) be improved for skill creation and maintaining.

Please feel free to add ideas by editing or commenting!

Web UI

Creation

• [x] leaving a page won't warn about lost data (talks)
• [x] installFile API called too often when not necessary
• [x] dialogTemplate order is not maintained -> intents before skill name (not important when all editing is in web UI)
• [x] encoding of umlauts failing
• [x] load skill after creation (so it is shown in the devmode afterwards!)
• [x] newly created skill has no buttons to add intents on first load
• [x] newly created skill has a button to add talks, but added talks are not visible
• [x] switch after skill creation out of skill creation screen
• [x] language is not initially set by creation

Edit

There is already a tab showing that you can edit skills via web interface, but currently there are no functionalities.

• [ ] SkillKit Test results #323
• [ ] Voice input for training data
• [ ] Automatic classification of new training data (find slots etc.)
• [ ] Add "did you mean that?" capured text to dialog Template after user review (webUI)
• [ ] removeIntent - for all lang
• [ ] removeSlotType - for all lang

Others

• [ ] installed skills and store don't use the same structure: .desc vs .description
• [ ] naming of AliceSK and install files don't match (name = skillName, author = username)
• [x] talks/dialogs missing not loaded when entering an empty language?

ToDo

• [x] general config is not scrolling

Documentation

as always!

[Psychokiller1888]

This has been started but I struggling finding the best way to present the whole thing... Tiles per skill that open a dialog? We want to be able to edit the slots and the utterances

[philipp2310]

going to a add a new multi line - but pretty formatted - input/datatype in the config.vue/configInput.vue Something like "Synonyms", one input line for text, more lines for the previous inputs and an option to delete lines.

Additionally a "NLU highlighted Input" is required, something where you can possibly mark, but for sure see the slots in a sentence.

Regarding your question: I'd say, yes, tiles per skill to keep a common feel to the installed skills and the skill store. Open in a dialog - maybe, as there is lots of information, I'd argue for a full screen edit mode.

[philipp2310]

'skillIntents': { "defaultValue": [], "dataType" : "userList", "subType" : "string", "description" : "The intents this skill will be able to handle", "category" : "details", "allowDouble" : false }

---> Only the frontend possibility to add lists

[philipp2310]

next step: add logic

[Psychokiller1888]

Wow!

[philipp2310]

About editing in the UI and sending to github + creating a PR to the Alice repo:

New Skills will only be available in the users github: They are always locked for updates. "Create PR" will somehow propose that skill for project-alice-assistant.

Editing an existing Skill will start from the main project-alice-assistant repo. -> Clone to raspi (happened on install) -> Create a fork in the users account

• [x] what happens when the fork already exists or the repo exists because the user was the initial creator? How should changes between the fork and the local version be handled -> don't overwrite the users changes at all cost! Maybe a "AliceSkillKit-Branch". Changes to that might be lost, the user should never edit this manually.

• [x] make sure the existing fork has the newest software version, but don't overwrite! -> Change the local version to sync with that fork -> Upload changes to the users fork -> Allow PR creation via UI (-> Popup asking for reason for changes, version, min Alice Version....)

• [x] how to handle users that aren't on the latest version? Allow checkout of old versions of a skill???

[philipp2310]

Required functions

(please feel free to edit this comment!)

Modify

The only option available if the skill is not yet marked for modification.

• set the modified flag in the skill
  • • [x] blocks automatic updates from origin (maybe merge/rebase instead of pull for auto update??)
• check if user is working on the newest version of the skill
  • • [ ] handling of old versions: allow editing of old version, PR will still be created for master and therefor potentially only for later versions of Alice.
• • [x] git-API: check if custom fork already exists
  • • [x] if not exists:
  • • [x] git-API: Create a fork in the users repository, named "AliceSKskill{{skillName}}" to make sure this repository is only used by AliceSK, manual forks don't intervene and Alice can delete/overwrite how ever she likes without deleting the users stuff)
  • if exists:
  • Popup:
    • "Drop previous changes or try to merge?"
  • revert fork or rebase origin
• • [x] git remote add AliceSK 'linkUserRepo'
• • [x] git checkout AliceSK master
• • [x] git pull (AliceSK)

Create PR

Only available when there is already an official repo docs Create a Pull Request for the pending changes towards origin

• [x] Popup
  • [x] make sure you have your latest changes committed!
  • [ ] changelog?
  • [ ] new min. Alice Version?
  • [ ] new skill Version?
• [ ] git merge/rebase origin (manual for now)
• [ ] git push AliceSK (manual for now)
• [x] open git: create PR

Propose Skill

Only available when there is no official repo Create an issue on PA repository proposing the skill for the store.

• check skill (run AliceSK)
• Popup
  • Read rules?
  • Input additional Information "Why this skill should be added" or "about this skill... but not in the included description"
• create Issue with fixed template showing basically the *.install information +?

(save) Update / Merge Official

Only available when there is already an official repo Pull the latest changes from origin and add them to the local skill

• git merge/rebase origin

Push to fork

Push the local changes to the users repository

• • [ ] Popup:
  • Please provide your commit message!
• • [x] git add .
• • [x] git commit -m "xxx"
• • [x] git push AliceSK

Pull from fork

Pull the changes from the users repository (when collaborating?)

• Popup:
  • "You will lose your local changes and revert to latest version on your repository"
• git stash
• git clear
• git pull AliceSK OR
• git rebase/merge AliceSK

Revert

Only available when there is already an official repo Revert all changes the user did

• [ ] Popup:
  • "You will lose your changes and revert to latest version in the store"
• git stash
• git clear
• git pull origin
• git remote remove AliceSK
• • [x] git checkout -set-upstream=origin/master
• • [x] unset "modified" flag of the skill

New Skill

The only function here listed that is NOT a button on the "cloud"-Tab in DEVMODE. This function is called on initial creation of skill creation.

• skills start with "modified" flag in Alice
• local creation of all files
• creation of github repository with name "AliceSK_new(?)skill{{skillname}}" to prevent same name when later editing that skill (always fork from alice?)