smithery/vanman2024

promptfoo-config

promptfoo configuration patterns for prompt regression testing, multi-provider comparison, and assertion-based validation. Use when setting up prompt testing, comparing LLM providers, or creating eval pipelines.

Installation

$ npx skills add smithery/vanman2024 --skill promptfoo-config

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/vanman2024 · top by installs.

npx skills add smithery/vanman2024

Browse all from smithery/vanman2024

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash, Read, Write, Edit, Grep, Glob, WebFetch

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,477 B
  • docs SUMMARY.md 235 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

promptfoo Configuration

Skill for configuring promptfoo prompt evaluation and testing.

Overview

promptfoo enables:

  • Prompt regression testing
  • Multi-provider comparison
  • Assertion-based validation
  • HTML report generation

Use When

This skill is automatically invoked when:

  • Setting up prompt testing
  • Comparing LLM providers
  • Creating evaluation pipelines
  • Defining test assertions

Available Scripts

Script Description
scripts/init-promptfoo.sh Initialize promptfoo project
scripts/run-eval.sh Run evaluation with output

Available Templates

Template Description
templates/promptfooconfig.yaml Basic configuration
templates/multi-provider.yaml Provider comparison
templates/assertions.yaml Assertion examples

Best Practices

  1. Use YAML anchors for repeated config
  2. Store prompts in separate files
  3. Use variables for dynamic tests
  4. Set appropriate thresholds