update-langfuse-staging-server-prompt

Push Langfuse prompts to staging with production requiring explicit confirmation.

6|1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/pwv-vc/agentcribs-community --skill update-langfuse-staging-server-prompt-pwv-vc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-langfuse-staging-server-prompt
Source: https://github.com/pwv-vc/agentcribs-community/tree/main/resources/tearsheets/arsenal/dot-claude/skills/update-langfuse-staging-server-prompt
Command: npx skills add https://github.com/pwv-vc/agentcribs-community --skill update-langfuse-staging-server-prompt-pwv-vc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests.

What problem does it solve?

Push Langfuse prompts to the staging server by default and to production only with explicit confirmation. This skill provides a safe, auditable workflow to push prompts to Langfuse staging server with safety checks and human-review gates.

Core Features & Use Cases

  • Safe staging pushes by default with automatic credential checks and environment isolation
  • Production pushes require explicit confirmation and human review
  • Reads prompts from docs/cached_prompts and creates new prompt versions via the Langfuse API without auto-labeling
  • Supports auditing and traceability of prompt deployments between environments

Quick Start

Push a specified prompt to the staging Langfuse server using a brief commit message.

Frequently Asked Questions about update-langfuse-staging-server-prompt

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

FAQPage Schema
How do I safely push Langfuse prompts to a staging server?

To safely push Langfuse prompts to staging, this skill validates credentials, reads prompts from docs/cached_prompts, and creates new prompt versions via the Langfuse API without automatic labeling.

Can I deploy Langfuse prompts directly to production?

Deploying Langfuse prompts to production requires explicit confirmation and human review gates, ensuring a safe and auditable workflow compared to automatic staging pushes.

Does pushing Langfuse prompt versions apply labels automatically?

No, pushing Langfuse prompt versions does not apply labels automatically. The skill creates new versions via the API without auto-labeling to ensure deployment safety.

What is the best way to audit prompt deployments across environments?

The best way to audit prompt deployments is using a workflow with environment isolation and human-review gates. This skill supports traceability between staging and production pushes.

Do I need the requests library to deploy prompts to Langfuse?

Yes, you need the requests library. This skill depends on it to interact with the Langfuse API for validating credentials and creating new prompt versions.

Where does this skill read prompts from before pushing to Langfuse?

The skill reads prompts from the docs/cached_prompts directory before validating credentials and pushing the prompt versions to the Langfuse staging or production servers.