portfolio-name-resolution

Resolve portfolio aliases to standardized SAM-prefixed names for database queries.

12|13|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/Snowflake-Labs/sfguide-agentic-ai-for-asset-management --skill portfolio-name-resolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: portfolio-name-resolution
Source: https://github.com/Snowflake-Labs/sfguide-agentic-ai-for-asset-management/tree/main/data/skills/portfolio-name-resolution
Command: npx skills add https://github.com/Snowflake-Labs/sfguide-agentic-ai-for-asset-management --skill portfolio-name-resolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity when users refer to investment portfolios by nicknames or abbreviations, ensuring that all downstream Cortex Analyst queries use the correct, standardized naming convention.

Core Features & Use Cases

  • Alias Normalization: Automatically converts informal terms like Tech, ESG, or 60/40 into their official SAM-prefixed portfolio names.
  • Ambiguity Handling: Provides a structured clarification process when a user input could map to multiple potential portfolios.
  • Use Case: A user asks for the performance of the Tech portfolio, and this skill ensures the query is executed against the SAM Technology & Infrastructure dataset.

Quick Start

Use the portfolio name resolution skill to identify the full name for the ESG Leaders portfolio.

Frequently Asked Questions about portfolio-name-resolution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map informal portfolio aliases to standardized names for database querying?

Portfolio name resolution maps informal aliases and abbreviations to standardized SAM-prefixed names. It matches user input against a predefined mapping table to ensure accurate Cortex Analyst tool execution.

What happens when a portfolio nickname could refer to multiple potential portfolios?

Ambiguity handling provides a structured clarification process when user input maps to multiple potential portfolios. This ensures the correct SAM-prefixed dataset is selected before executing downstream queries.

Why does Cortex Analyst require SAM-prefixed naming conventions for portfolio requests?

Cortex Analyst requires SAM-prefixed naming conventions to maintain data integrity across all portfolio-related requests. Strict adherence ensures queries execute against the correct standardized datasets.

Can I use this to normalize abbreviations like Tech or ESG for financial portfolio queries?

Yes, alias normalization automatically converts informal terms like Tech, ESG, or 60/40 into their official SAM-prefixed portfolio names. This ensures downstream queries target the correct datasets.

What's the best way to resolve portfolio name ambiguity before running Cortex Analyst queries?

The best way to resolve portfolio name ambiguity is using a predefined mapping table that enforces strict SAM prefix naming conventions. This eliminates informal nickname overlap before query execution.