agentleFS
coval-aicoval-ai/coval-external-skills/skills/test-cases/huggingface-import/SKILL.md

huggingface-import

Skill3 starsChanged 17 days agoMITView on GitHub

Import datasets from HuggingFace and convert them to Coval test sets. Use when the user wants to create test cases from HuggingFace dataset or repository.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Import $ARGUMENTS from HuggingFace and convert it into Coval test sets with properly structured test cases.

    line 9
  2. Very specific:

    If $ARGUMENTS is provided, navigate to it.

    line 43
  3. Distinctive:

    Ask these questions to map HuggingFace data to Coval format:

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

HuggingFace to Coval Test Set Import

Import $ARGUMENTS from HuggingFace and convert it into Coval test sets with properly structured test cases.

Coval Context

Coval is an AI evaluation platform for testing voice and conversational AI agents. It runs simulations against AI agents and measures performance with configurable metrics.

ConceptDescription
Test SetA collection of test cases, grouped by category or evaluation purpose
Test CaseA single evaluation scenario with input (prompt) and optional metadata
PersonaHigh-level user character (system prompt) - separate from test cases
AgentThe AI system being evaluated

Key distinction:

  • Persona = WHO is asking (character, traits)
  • Test Case = WHAT they ask (prompts, scenarios)

Coval API

Base URL: https://api.coval.dev/v1

Fetch the OpenAPI spec before making API calls:

# List specs (no auth)
GET https://api.coval.dev/v1/openapi

# Fetch specific spec
GET https://api.coval.dev/v1/openapi/{spec_name}

Workflow

Step 1: Identify the HuggingFace Source

If $ARGUMENTS is provided, navigate to it. Otherwise ask:

What is the HuggingFace repository, space, or dataset you want to import?

Then:

  1. Navigate to the HuggingFace source
  2. Find data files (CSV, JSON, Parquet)
  3. Examine structure and fields

Step 2: Analyze Data Structure

Report to the user:

  • Total records
  • Available fields/columns
  • Existing categorization
  • 2-3 sample records

Step 3: Interactive Field Mapping

Ask these questions to map HuggingFace data to Coval format:

Q1: Input Field

Which field contains the question/prompt for the test case input?

Q2: Categorization

How should test cases be organized into test sets?

  • By existing category field
  • Single test set
  • Custom logic

Q3: Metadata

Which fields should be preserved in metadata JSON? (Recommend: preserve original IDs like question_id)

Q4: Multi-turn (if applicable)

How to handle multi-turn conversations?

  • First turn only
  • Concatenate turns
  • Separate test cases per turn

Step 4: Generate CSVs

Create Coval-compatible CSVs:

input,metadata
"Your question here","{""question_id"": ""123"", ""source"": ""mt-bench""}"

Requirements:

  • input column MUST be first
  • Proper quote escaping (double quotes)
  • metadata as valid JSON string
  • UTF-8 encoding
  • One CSV per category (recommended)

Naming: {source}_{category}.csv

Step 5: Upload to Coval

Manual: Upload CSVs via Coval dashboard test sets page.

API: Fetch OpenAPI spec and use test set endpoints programmatically.

Common HuggingFace Sources

General Language Understanding

DatasetDescription
cais/mmlu15k+ multiple-choice questions across 57 subjects (STEM, humanities, law)
nyu-mll/glueSentence-level tasks: sentiment, entailment, linguistic acceptability
tau/commonsense_qaReasoning tests for everyday world knowledge
Rowan/hellaswagCommon-sense inference and completion

Reasoning & Problem-Solving

DatasetDescription
openai/gsm8k~8k grade-school math word problems (multi-step arithmetic)
ucinlp/dropReading comprehension with discrete operations
lukaemon/bbhBigBench Hard - challenging reasoning subset

Supporting Files

  • For Python transformation example, see examples/huggingface-import.py

Checklist

  • Identified input field
  • Determined categorization
  • Preserved original IDs in metadata
  • Proper quote escaping
  • Valid JSON in metadata
  • Separate CSVs per category

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.