Welcome to the Bot Framework Tools repository, which is the home for a set of tools for developers building bots with the Microsoft Bot Framework
Перейти к файлу
seaen 9b8915a0c6 Readme updates 2018-05-02 11:43:15 -07:00
.github
AzureCli address comments around readme 2018-04-30 14:51:26 -07:00
Chatdown fix card attachments 2018-05-01 20:12:01 -07:00
Dispatch updated version 2018-05-01 12:59:24 -07:00
LUIS Merge pull request #127 from mgbennet/patch-uppercase 2018-05-01 19:44:18 -07:00
LUISGen add copyright notices 2018-05-01 18:36:24 -07:00
Ludown npm publish. moving negative tests to its own folder 2018-04-30 19:01:01 -07:00
MSBot add copyright notices 2018-05-01 18:36:24 -07:00
QnAMaker Merge pull request #127 from mgbennet/patch-uppercase 2018-05-01 19:44:18 -07:00
ludown/examples/Nagative tests npm publish. moving negative tests to its own folder 2018-04-30 19:01:01 -07:00
.editorconfig
.eslintrc.json
.gitattributes
.gitignore update git ignore to ignore build folder 2018-04-29 01:51:54 -07:00
LICENSE
README.md Readme updates 2018-05-02 11:43:15 -07:00

README.md

Bot Builder tools

This repository contains code for Bot Builder tools. Bot Builder tools are designed to cover end-to-end bot development workflow and include the following tools -

  • npm version Chatdown: Create mockups of bot conversation transcripts
  • npm version MSBot: Create and manage your bot configuration file
  • npm version LUDown: Bootstrap language understanding using markdown files
  • npm version LUIS: Create and manage your LUIS.ai application
  • npm version QnAMaker: Create and manage QnAMaker.ai Knowledge Base.
  • npm version Dispatch: Bring disparate language understanding models to work together for your bot
  • npm version LUISGen: Generate C# class or Typescript interface over a LUIS model.

To install all CLI tools:

npm install -g chatdown msbot ludown luis-apis qnamaker botdispatch luisgen

Please see here for an overview of the end-to-end development workflow. Please see here for an example end to end development workflow using Bot Builder tools.

Before writing code, review the bot designguidelinesfor best practices and identify the needs for your bot: will a basic bot be enough or whether it should have more sophisticated capabilities, such as speech,language understanding,QnA, or the ability to extract knowledge from different sources and provide intelligent answers. This is also the phase where you might want to create mockup of conversations between the user and the bot for the specific scenarios your bot will support. Chatdown is the tool built for this purpose. You can author .chat files that mockup the conversations and then use chatdown CLI to convert them into rich transcripts.

As you build your bot, you may also need to integrate AI services like LUIS.ai for language understanding, QnAMaker.ai for your bot to respond to simple questions in a Q&A format, and more. You can bootstrap language understanding for your bot using LUDown.

The tools are designed to work together. You can then use LUIS CLI and / or the QnAMaker CLI tools to create your LUIS.ai models and QnAMaker knowledge base.

As your bot grows in sophistication, Dispatch CLI can help create and evaluate LUIS models used to dispatch intent across multiple bot modules such as LUIS models, QnA knowledge bases and others (added to dispatch as a file type).

Throughout your Build phase, you can use MSBot CLI to create and keep your bot configuration file updated with all relevant service references.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Reporting Security Issues

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

License

Copyright (c) Microsoft Corporation. All rights reserved.

Licensed under the MIT License.