Learn more about the platforms folder, which represents the voice platform projects, including information and language models. Usually, this folder is just used for deployment.


The platforms folder includes all the information you need to deploy the project to the respective developer platforms Amazon Alexa and Google Assistant.

Platforms Folder in a Jovo Project

At the beginning of a new project, the folder doesn't exist until you either import an existing Alexa Skill project with jovo get, or create the files from the Jovo Language Model with jovo build (see Workflows for examples).

If you only want to work with a platform specific model, for example, you want to create just an Alexa Skill, you don't necessarily need the /models folder: The /platforms folder and the jovo deploy command are enough. Go to Jovo CLI Commands to learn more about all commands.

Alexa Skill

The alexaSkill folder contains all the information of your Alexa Skill needed to deploy the skill to the Amazon Developer Portal using the Jovo CLI. The Jovo CLI supports both ASK CLI v2 and ASK CLI v1, each requiring a slightly different project structure. Read more about the migration here.


The .ask folder contains the basic deploy settings of your skill, such as your project's skillId, inside a single file, ask-states.json for v2 of the ASK CLI, config for v1. We recommend you to not make any changes to these files.



Since version 2 of the ask-cli integrates an implementation of the SMAPI, most of the skill's data is organized in the skill-package folder. A skill package might consist of your skill's manifest, interaction models and optional account-linking information.

The Alexa Interaction Models are stored inside alexaSkill/skill-package/interactionModels/custom/. For v1 of the ASK CLI, the models are located at alexaSkill/models/. They can either be built by the jovo build command (if you're making use of the Jovo Language Model), updated manually, or updated in the Amazon Developer Portal and then imported with jovo get.

For more information about Alexa Interaction Models, please see the official reference by Amazon: Custom Interaction Model Reference (Intents, Slots, Sample Utterances).


skill.json contains the publication and configuration information of your Skill. This can be either updated manually or in the Amazon Developer Portal (and then imported with the jovo get command). If you have v2 of the ASK CLI installed, the file's location is alexaSkill/skill-package/, else it's located inside alexaSkill/.


V2 of the ASK CLI requires an additional file, ask-resources.json. This file contains your project's configuration for use with the Skill Management API.

Google Action

The googleAction folder currently contains the dialogflow (as supported natural language understanding tool) folder with all the files needed to deploy the agent to Dialogflow Console using the Jovo CLI.

Google Action Folder in a Jovo Project

Please note that Jovo currently supports Dialogflow v1, which means that you can't programmatically create or update your agent. However, the jovo deploy command will create a zip which you can then import into Dialogflow.

It will be stored inside the googleAction folder:

Dialogflow Agent Export


The dialogflow folder contains the following folders:

Dialogflow Folder Structure


All the intents are saved in separate files and look like this:

It is important that "webhookUsed" is set to true for your Jovo code to be triggered when this intent is called.

The user phrases are added to a different file for each language, e.g. MyNameIsIntent_usersays_en-us.json, and look like this:


If you have defined input types, you will find the entities in separate folders as well.


This includes some agent specific information. We recommend to not change this file unless you know what you're doing.

Comments and Questions

Any specific questions? Just drop them below or join the Jovo Community Forum.

Join Our Newsletter

Be the first to get our free tutorials, courses, and other resources for voice app developers.