arize-prompts

Manage versioned LLM prompt templates in Arize Prompt Hub.

Updated May 5, 2026
One-click install
npx skills add https://github.com/ethan-rio/skills --skill arize-prompts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arize-prompts
Source: https://github.com/ethan-rio/skills/tree/main/skills/arize/arize-prompts
Command: npx skills add https://github.com/ethan-rio/skills --skill arize-prompts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing LLM prompt templates in Arize Prompt Hub manually is error-prone and time-consuming, especially when tracking versions, applying production/staging labels, and ensuring prompts are correctly configured for deployment in LLM applications.

Core Features & Use Cases

  • Prompt Authoring & Import: Create new prompt templates with {variable} placeholders from scratch, or import existing prompts from application code or LLM traces to persist them in the Hub.
  • Version & Label Management: Track immutable prompt versions, apply production or staging labels to point applications to the correct prompt version without code changes, and duplicate or delete prompts as needed.
  • Use Case: A machine learning team can use this skill to refine a customer support prompt across multiple iterations, promote tested versions to production, and avoid hardcoding version IDs in their application code.

Quick Start

Use the arize-prompts skill to create a new customer support prompt template with a {question} variable and save it to your Arize Prompt Hub space.

Frequently Asked Questions about arize-prompts

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

FAQPage Schema
How do I manage versioned LLM prompt templates without hardcoding version IDs?

Managing versioned LLM prompt templates without hardcoding version IDs requires applying production or staging labels to immutable prompt versions. This allows you to point applications to the correct prompt version dynamically without modifying code.

How do I import existing LLM prompts from application code into a prompt hub?

Importing existing LLM prompts from application code or LLM traces into a prompt hub involves extracting the prompt text and persisting it as a new template. You can then author these templates with variable placeholders for centralized management.

What is the best way to track immutable prompt history for production LLM applications?

Tracking immutable prompt history for production LLM applications is best achieved through prompt versioning combined with production and staging labels. This ensures tested iterations are safely promoted while maintaining a strict, unchangeable version history.

Does Arize Prompt Hub support variable placeholders for prompt authoring?

Yes, Arize Prompt Hub supports prompt authoring with variable placeholders. This feature allows you to create dynamic prompt templates by enforcing correct variable formatting, explicit provider specification, and model specification for deployment.

Why does prompt management fail when manually tracking versions and labels?

Manual prompt management fails because tracking versions, applying production or staging labels, and configuring deployment settings by hand is error-prone and time-consuming. Automating these workflows enforces correct formatting and immutable version history to prevent deployment errors.