The text fields you provide in the Developer Studio determine how your app is discovered in the Orceum Store and what users need to know before installing it. Getting these right is critical for a smooth user experience.

​
App Description

Your app’s description is shown to users in the Orceum Store, installation screens, and conversation surfaces. Think of it as your app store listing: 
{
  "description": "Manage your tasks and reminders. Create, update, and track todos with natural language — just tell Orceum what you need done."
}
Guidelines:
  • Keep it concise (1-3 sentences max).
  • Focus on what the user can do with your app.
  • Use plain language and avoid technical jargon.
  • Mention the service by name (e.g., “Sync with Todoist”, “Manage Notion pages”).
Orceum’s AI-powered search in the Store heavily relies on this description to match user intent. The better your description, the more accurately users can discover your app.

​
Pre-Install Instructions

You can display important information to users before they install your app. Use this for prerequisites, warnings, or setup steps. You can configure this in the Developer Studio under your app settings. When to use Pre-Install Instructions:
  • Prerequisites: “Requires Admin role on the target workspace.”
  • Credentials: “Go to Settings → API → Generate Key to get your token.”
  • Permissions: “This app requires read/write access to all your files.”
  • Pricing: “Requires a Premium plan on our service.”
When configured, the installation UI will display these instructions before the user is prompted to click “Install” or provide their credentials.

​
Action-Level Descriptions

If you are building a Native or Skill app, each action’s description in your manifest is incredibly important. The assistant reads these to decide which action to execute when chatting with the user. 
{
  "name": "create_task",
  "description": "Creates a task"
}
This tells the AI nothing useful. When would it choose this over any other “create” action?

​
Parameter Descriptions

Do not skip describing the parameters of your actions. The AI relies on these descriptions to extract information from the user’s message correctly: 
{
  "name": "due_date",
  "type": "string",
  "description": "Due date in ISO 8601 format (YYYY-MM-DD), e.g. 2024-12-31. Leave empty for tasks with no deadline.",
  "required": false
}