Set up the ASK CLI to Use Alexa Conversations Description Language
With the Alexa Skills Kit Command Line Interface (ASK CLI), you can use Alexa Conversations Description Language (ACDL) to build and deploy turn-by-turn Alexa Conversations skills. Alexa Conversations uses deep learning to create Alexa skills in which dialog flows naturally between Alexa and the user.
ask. However, command line messages might refer to
ask. For ACDL, always use
Before you install and configure the ASK CLI, you must meet the following requirements.
Accounts and permissions
- Amazon developer account – If you don't already have an Amazon developer account, sign up at developer.amazon.com.
- AWS account – If you don't already have an Amazon Web Services (AWS) account, sign up at aws.amazon.com/account.
- Update to the latest release of Node.js (version 18.12 or later).
- For version control, use the latest release of Git (version 2.38 or later).
- Update your Java development environment to the latest stable release (version 17 or later).
- Migrate to version 2 of the AWS Command Line Interface (AWS CLI).
Use the latest version of VS Code (version 1.70 or later).
To install the latest version of VS Code
- Open VS Code.
- On the Code tab, click Help.
- Click Check for Updates.
Steps to install and configure the ASK CLI
To install and configure the ASK CLI, complete the following steps. Then use ACDL to create Alexa Conversations skills on the command line.
Step 1: Install the ASK CLI
In this step, you use npm to install the version of the ASK CLI that supports Alexa Conversations. For details, see Quick Start: Alexa Skills Kit Command Line Interface (ASK CLI).
To install the ASK CLI beta version
Before you install the ASK CLI beta, you must uninstall the public version. At the command prompt, enter the following command.
npm uninstall -g ask-cli
To install the beta version of the ASK CLI, enter the following command.
npm install -g ask-cli-x
Step 2: Configure the ASK CLI
In this step, you configure the ASK CLI to link to your Amazon developer account. This configuration verifies your identity so you can access ASK CLI resources.
To configure the ASK CLI to recognize your developer account
To link the ASK CLI to your developer account, enter the following command.
- Choose the default profile, or enter a name to create a new profile.
- To grant permission to link your AWS profile to your ASK CLI skill, select the checkbox.
- Go to the AWS Key Management Service, and sign in as an IAM user.
- Choose a symmetric access key (a single 256-bit secret encryption key), and then click Save and Continue.
Step 3: (Optional) Install the ASK Toolkit for VS Code
In this step, you install the ASK Toolkit for Visual Studio (VS) Code version 2.10 or later, or you update your existing extension to the latest version. The toolkit provides a syntax highlighter and dedicated VS Code workspace in which to create and test Alexa skills. The ACDL syntax highlighter is currently available only for VS Code.
To install the ASK Toolkit for VS Code
Open VS Code, and then click Code > Preferences > Extensions.
Search for the Alexa Skills Kit (ASK) Toolkit extension.
Click the gear icon, and then click Install another version > 2.10.
To enable the extension, close and then reopen VS Code.
Troubleshooting ASK CLI installation
If you have trouble with ASK CLI installation, try the following suggestions.
When you try to install the ASK CLI, you get an error message similar to the following example.
npm ERR! code ENOENT npm ERR! syscall rename npm ERR! path /Users/username/.nvm/versions/node/v17.4.0/lib/node_modules/.staging/ask-cli-e209bd51/node_modules/@babel/generator/node_modules/source-map npm ERR! dest /Users/username/.nvm/versions/node/v17.4.0/lib/node_modules/.staging/source-map-4818842b npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, rename '/Users/username/.nvm/versions/node/v17.4.0/lib/node_modules/.staging/ask-cli-e209bd51/node_modules/@babel/generator/node_modules/source-map' -> '/Users/username/.nvm/versions/node/v17.4.0/lib/node_modules/.staging/source-map-4818842b' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: npm ERR! /Users/username/.npm/_logs/2022-02-09T04_38_12_058Z-debug.log
Make sure you have the latest npm package, which is version 8.5 or later.
To make sure your npm package is up to date
At the command prompt, enter the following command.
sudo npm i -g npm
package-lockfrom your JSON file, enter the following commands.
rm package-lock.json npm i sudo npm i -g .
To switch to the last functional version of npm, enter the following commands.
sudo npm i -g firstname.lastname@example.org npm -v 8.5.1 rm package-lock.json npm i sudo npm i -g .
Issue: AWS error message
When you try to install the ASK CLI, you get an AWS error message, such as a notice that your account couldn't be linked.
If you receive an AWS error message, sign in to your AWS account, and check the configuration.
To check your AWS configuration
- Sign in to your AWS account and verify the following items:
Issue: Other error message
When you try to install the ASK CLI, you receive an error message not listed in this document.
Make sure you didn't miss anything in the installation, review the general instructions for installing the ASK CLI.