Description Skill

Generate or improve business-friendly descriptions for analytics objects using available context. Use this skill when users want to add or enhance descriptions for metrics, attributes, facts, or other analytics objects to make them more understandable and discoverable.

Experimental Feature

This is an experimental feature that is still under active development. Its behavior may change in future releases, or the feature may be removed.

How It Works

The Description skill analyzes analytics objects and their context to generate or improve business-friendly descriptions. When activated, the assistant:

  1. Loads the object and its direct children to gather context
  2. Analyzes the object’s definition, relationships, and usage
  3. Generates a clear, business-friendly description
  4. Uses available metadata and context to ensure accuracy
  5. Provides descriptions that help users understand what the object represents

The skill uses available context from the object definition, related objects, and workspace metadata to create descriptions that are both accurate and accessible to business users.

Examples

Adding a description:

User: "Add a description to the Gross Margin metric"
Assistant: [Loads metric context, generates description, updates object]

Improving descriptions:

User: "Make the Customer Segment attribute description more clear"
Assistant: [Analyzes current description, improves clarity, updates]

Generating descriptions:

User: "Generate descriptions for metrics that don't have them"
Assistant: [Finds objects without descriptions, generates appropriate text]

Other use cases:

  • “Add a description to the Revenue metric”
  • “Describe what this attribute represents”
  • “Make the description for Sales Amount more business-friendly”
  • “Improve the description to be clearer”
  • “Create descriptions based on the object definitions”

Limitations

  • Requires appropriate permissions to update object metadata
  • Description quality depends on available context and object definitions
  • May not capture all business nuances without additional user input
  • Works best when objects have clear definitions and relationships