gregstewart / alexa-gadgetzan-gazette Goto Github PK

Need to handle built in intents

• Help
• Stop
• Cancel

Other:

• With no value provided for the "Game" slot, the skill returns an error.

if (req.body.request.type === 'IntentRequest' &&
           req.body.request.intent.name === 'GadgetzanGazette') {

    if (!req.body.request.intent.slots.Day ||
        !req.body.request.intent.slots.Day.value) {
      // Handle this error by producing a response like:
      // "Hmm, what day do you want to have news for?"
    }

Also think about how to handle a game that isn't in the list

1. Your skill does not meet our invocation name requirements for formatting. The invocation name must contain only lower-case alphabetic characters, spaces between words, possessive apostrophes (for example, “sam’s science trivia”), or periods used in abbreviations (for example, “a. b. c.”). Other characters like numbers must be spelled out. For example, “twenty one”.

Please correct the invocation name as suggested below:

blizzardnewsflash => blizzard news flash

Please review our documentation on choosing an invocation name and update your invocation name and example phrases accordingly.

2. When invoking the "BlizzardNewsFlash" intent with the "Heroes of the Storm" value for the {GAME} slot, the skill’s response is irrelevant to the request. Please see test case 4.2 from our Submission Checklist for guidance on intent responses.

Steps to reproduce:

User: "Alexa launch blizzardnewsflash"
Skill: "You can ask me for todays Blizzard news"
User: "what is today news for heroes of the storm"
Skill: "Sorry the Blizzard News Flash has no news!"

Please note, that this slot value is working fine when using one-shot requests.

1. The example phrases that you choose to present to users in the companion app must be included in your sample utterances. These sample utterances should not include the wake word or any relevant launch phrasing.

   Please include your example phrase in the sample utterances as shown below:

   GadgetzanGazette {Date} blizzard news

   For more information about the words included in our supported launch phrases, please see: https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/supported-phrases-to-begin-a-conversation

2. If user input is required after launching the skill with no intent, a welcome prompt must be provided which describes what users can ask of the skill and the session must remain open for a user response. If the session closes after launching the skill, a core functionality must be completed without prompting users to speak. Also the welcome phrase must be appropriate to the context of the skill’s functionality as defined in its description. Please see test case 4.1 from our Submission Checklist for guidance on session management

   Example:

   User: "Alexa, open gadgetzan gazette".
   Skill: "Hmm Why not ask me to give you the latest Blizzard news?"
   

   and the session is closed.

   Ideally, the welcome prompt must be provided which describes what users can ask of the skill and the session must remain open for a user response

The example phrases that you choose to present to users in the companion app must be included in your sample utterances. These sample utterances should not include the wake word or any relevant launch phrasing.

Please include your example phrase in the sample utterances as shown below:

GadgetzanGazette {Date} blizzard news

For more information about the words included in our supported launch phrases, please see:

https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/supported-phrases-to-begin-a-conversation

If user input is required after launching the skill with no intent, a welcome prompt must be provided which describes what users can ask of the skill and the session must remain open for a user response. If the session closes after launching the skill, a core functionality must be completed without prompting users to speak. Also the welcome phrase must be appropriate to the context of the skill’s functionality as defined in its description. Please see test case 4.1 from our Submission Checklist for guidance on session management

Example:

User: "Alexa, open gadgetzan gazette".

Skill: "Hmm Why not ask me to give you the latest Blizzard news?" and the session is closed.

Ideally, the welcome prompt must be provided which describes what users can ask of the skill and the session must remain open for a user response.

The skill end-point is not validating the signatures for incoming requests and is accepting requests with an empty signature URL. Please make sure that your signature validation is correct. To reject an invalid request with an invalid signature or certificate, the skill should respond with HTTP status code 400 (Bad Request) in the response.

Please refer to the following documentation on how to build your Alexa Skill as a web service and validate requests and signatures.

https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/developing-an-alexa-skill-as-a-web-service#verifying-the-signature-certificate-url

As per

Response Format

This section documents the format of the response that your service returns. The service for an Alexa skill must send its response in JSON format.

Note the following size limitations for the response:

The outputSpeech response cannot exceed 8000 characters.
All of the text included in a card cannot exceed 8000 characters. This includes the title, content, text, and image URLs.
An image URL (smallImageUrl or largeImageUrl) cannot exceed 2000 characters.
The total size of your response cannot exceed 24 kilobytes.

Which is causing the the skill to fail.