4.5 Rules of Command name/ Skill name

  1. The skill invocation name must not infringe upon the intellectual property rights of an entity or a person. 
  2. One-word invocation names are not allowed, 
  3. Invocation names that include names of people or places (for example, “Molly“, “Seattle“) are not allowed, unless they contain other words (for example, “Molly’s horoscope” “Seattle spotlight“, “Sam’s market“).
  4. Two-word invocation names are not allowed if one of the words is a definite article (“the“), indefinite article (“a”, “an”) or preposition (“for”, “to”, “of,” “about,” “up,” “by,” “at,” “off,” “with“). For example, “a bicycle“, “an espresso“, “to amuse“, “for fun“.
  5. The invocation name must not contain any of the Alexa skill launch phrases and connecting words.
  6. Launch phrases include “run“, “start“, “play“, “resume“, “use“, “launch“, “ask“, “open“, “tell“, “load“, “begin” and “enable“.
  7. Connecting words include “to,” “from,” “in,” “using,” “with,” “about,” “for,” “that,” “by,” “if,” “and,” “whether.” See Understanding How Users Invoke Custom Skills to learn more about launch phrases and connecting words.
  8. The invocation name must not contain the wake words “Alexa“, “Amazon“, “Echo” or the words “skill” or “app“.
  9. The invocation name must contain only lower-case alphabetic characters, spaces between words, and possessive apostrophes (for example “Sam’s science trivia“). Other characters like numbers must be spelled out (for example “twenty one“). The name must be easy to pronounce correctly and be phonetically distinct to avoid being misinterpreted as other similar-sounding words.
  10. Periods are also permissible in invocation names containing acronyms or abbreviations that are pronounced as a series of individual letters, as in “NPR”, where the letters should be all lowercase and separated by periods and spaces (for example “n. p. r.”). However, if the abbreviation is pronounced as a word, as in “NASA”, then it should be all lowercase but not contain periods or spaces (for example “Nasa”).
  11. The invocation name cannot spell out phonemes. For example, a skill titled “AWS Facts” would need “AWS” represented as “a. w. s. ” and NOT “ay double u ess.”
  12. The invocation name must not create confusion with existing Alexa features. If your skill invocations overlap with common Alexa commands, users may get confused by Alexa’s response and not enable your skill. For example, if your invocation name is too similar to the built-in “weather” command, Alexa may sometimes respond with your skill and sometimes respond with the built-in weather feature, providing inconsistent user experience.
  13. The invocation name must be written in each language you choose to support. For example, the German version of your skill must have an invocation name written in German. If your skill is published in a non-English marketplace, the invocation name may contain English words if these words are commonly used (for example, if proper nouns, like names and places, are used). In those cases, use the English spelling of those words. In cases where spelling differs between the local language and English, use the spelling of the local language (example: use “radioplayer” in a German skill–not “radio player“).
  14. The invocation name should be distinctive to ensure users can enable your skill. Invocation names that are too generic may be rejected during the skill certification process, or result in lower discoverability.