Creepy Doll

Development Setup

• git clone this repository
• Install and use Node v8.10
• Run npm install
• Make a copy of the aws-config.sample.js file and name it aws-config.js. Edit it with all of the requisite fields.
• Make a copy of the swagger.example.yaml file and name it swagger.yaml. Edit it with all of the requisite fields.

Platforms

Directory Structure

assets/ -> Media files of the skill
models/ -> Interaction model for every locale
platforms/ -> Alexa Skill and Dialogflow model
src/ -> Flow logic
.editorconfig -> IDE configuration
.eslintrc.json -> Eslint configuration
.gitattributes -> Git media files rules
.gitignore -> Git ignore rules
aws-config.sample.js -> AWS sample file for profile
gulpfile.js -> Automated tasks
LICENSE
package.json -> Dependencies
project.js -> Jovo app configuration file
README.md
swagger.example.yaml -> Sample file for swagger configuration for API Gateway

Skill information

Public name

Creepy Doll

Invocation name

creepy doll

Languages

For now, Creepy Doll is spoken in English and Spanish, looking to add more languages!

Locales (links will take you to the app in the store)

Alexa Skill

• en-US
• en-GB
• en-CA
• en-AU
• en-IN
• es-ES
• es-MX
• es-US

Google Assistant

• en-US
• en-GB
• en-CA
• en-AU
• en-IN
• es-ES
• es-419

Jovo CLI

The Jovo Command Line Interface (jovo-cli) offers the ability to create, prototype, test, and deploy your voice app quickly. To push any update, you will need this command:

jovo deploy

If you need to run the app locally, you just need to run the following command:

jovo run app/index.js -w

This will start the server and watch for changes. You will see your webhook URL in the console so you can set it in the DialogFlow and Alexa console.

Swagger file

Use this file to create/update your API Gateway configuration. This will allow you to connect your code stored in a Lambda function to the Google Assistant app.

If you need a full example of a Swagger file, follow this link

IAM settings

The API Gateway requires the IAM role to add it as a trusted relationship. For that you can modify the Trust Policy like this:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "",
      "Effect": "Allow",
      "Principal": {
        "Service": [
          "apigateway.amazonaws.com",
          "lambda.amazonaws.com"
        ]
      },
      "Action": "sts:AssumeRole"
    }
  ]
}