Send capabilities to Alexa Skill using SMAPI Connector

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I’m always frustrated when […] We are trying to inspect the audioPlayer from our Alexa skill using invocation through the SMAPI. When we send an intent that returns an audioPlayer response we expect it to return the response with the audio asset url. However we get this response:

 "outputSpeech": {
      "type": "SSML",
      "ssml": "<speak>Hm, I'm sorry but I can't do that on this device.</speak>"
    }

We believe this is because the basic capabilities have not been defined in the request to the skill using the invocation-request-template.json.

Describe the solution you’d like The ability to define the capabilities within the JSON config or the convo.txt context so we can send the capabilities to the alexa skill. So we can go from sending this request without the capabilities:

  "version": "1.0",
  "session": {
    "new": false,
    "sessionId": "97d4d9d0-8dca-11e9-a036-e15e61ac4dae",
    "application": {
      "applicationId": "amzn1.ask.skill.ccc19cb0-0ffd-4425-bfc0-594d44e8beda"
    },
    "attributes": {},
    "user": {
      "userId": "botium-core-test-user"
    }
  },
  "context": {
    "AudioPlayer": {
      "playerActivity": "IDLE"
    },
    "Display": {
      "token": ""
    },
    "System": {
      "application": {
        "applicationId": "amzn1.ask.skill.ccc19cb0-0ffd-4425-bfc0-594d44e8beda"
      },
      "user": {
        "userId": "botium-core-test-user"
      }
    }
  },
  "request": {
    "type": "IntentRequest",
    "requestId": "98529550-8dca-11e9-a036-e15e61ac4dae",
    "timestamp": "2019-06-13T11:01:28.997Z",
    "locale": "en-GB",
    "intent": {
      "name": "NewsIntent",
      "confirmationStatus": "NONE",
      "slots": {}
    }
  }
}

to this request with the capabilities:

{
  "version": "1.0",
  "session": {
    "new": false,
    "sessionId": "97d4d9d0-8dca-11e9-a036-e15e61ac4dae",
    "application": {
      "applicationId": "amzn1.ask.skill.ccc19cb0-0ffd-4425-bfc0-594d44e8beda"
    },
    "attributes": {},
    "user": {
      "userId": "botium-core-test-user"
    }
  },
  "context": {
    "AudioPlayer": {
      "playerActivity": "IDLE"
    },
    "Display": {
      "token": ""
    },
    "System": {
      "application": {
        "applicationId": "amzn1.ask.skill.ccc19cb0-0ffd-4425-bfc0-594d44e8beda"
      },
      "user": {
        "userId": "botium-core-test-user"
      },
      "device": {
        "deviceId": "amzn1.ask.device.AFRXExxx",
        "supportedInterfaces": {
          "AudioPlayer": {},
          "Display": {
            "templateVersion": "1.0",
            "markupVersion": "1.0"
          },
          "Alexa.Presentation.APL": {
            "runtime": {
              "maxVersion": "1.0"
            }
          }
        }
    }
  },
  "request": {
    "type": "IntentRequest",
    "requestId": "98529550-8dca-11e9-a036-e15e61ac4dae",
    "timestamp": "2019-06-13T11:01:28.997Z",
    "locale": "en-GB",
    "intent": {
      "name": "NewsIntent",
      "confirmationStatus": "NONE",
      "slots": {}
    }
  }
}

Describe alternatives you’ve considered A clear and concise description of any alternative solutions or features you’ve considered. We have considered just hitting the SMAPI directly with these intents to see what we get but doesn’t work well and means not using botium at all which is not prefered.

[codeforequity-at]

thanks for the good feature description. I added it to our internal backlog (BOT-657) and to the next sprint (as we consider this to be an important feature).

[codeforequity-at]

It is available in the latest Botium builds now (including Botium CLI and Botium Box)

@StoutyAlex We have a discord channel for Botium developer now - pls contact us at our website for receiving an invitation!