sync-metadata

Reconcile task metadata between selected_benchmark_tasks.json and task.toml files.

32|4|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/sourcegraph/CodeScaleBench --skill sync-metadata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-metadata
Source: https://github.com/sourcegraph/CodeScaleBench/tree/main/skills/sync-metadata
Command: npx skills add https://github.com/sourcegraph/CodeScaleBench --skill sync-metadata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that the metadata defined in individual task.toml files accurately reflects the authoritative selected_benchmark_tasks.json registry, preventing inconsistencies and errors in task execution.

Core Features & Use Cases

  • Metadata Reconciliation: Compares task.toml files against selected_benchmark_tasks.json to detect discrepancies.
  • Drift Detection: Identifies mismatches in language, difficulty labels, or missing task.toml files.
  • Automated Fixing: Optionally updates task.toml files to align with the central registry.
  • Use Case: When onboarding new benchmark tasks, this Skill verifies that all associated metadata is correctly configured before execution, saving debugging time.

Quick Start

Run the sync metadata skill to check for any discrepancies between task.toml files and the selected_benchmark_tasks.json.

Frequently Asked Questions about sync-metadata

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

FAQPage Schema
How do I reconcile task metadata drift between task.toml files and a central JSON registry?

To reconcile task metadata drift, compare individual task.toml files against the authoritative selected_benchmark_tasks.json registry to detect and fix discrepancies like language mismatches and difficulty label inconsistencies.

Why does my benchmark task configuration have missing task.toml files or mismatched difficulty labels?

Missing task.toml files or mismatched difficulty labels occur when local configurations drift from the central benchmark registry. Running a metadata sync detects these inconsistencies and optionally updates the files automatically.

What is the best way to validate task metadata before executing benchmark suites?

The best way to validate task metadata before execution is to run a reconciliation check that filters by suite and outputs JSON, ensuring all task.toml files accurately reflect the selected_benchmark_tasks.json registry.

Can I filter metadata reconciliation results by suite and output in JSON format?

Yes, you can filter metadata reconciliation results by suite and output them in JSON format. This allows targeted analysis of specific benchmark suites and easier programmatic processing of detected drift.

Does metadata sync automatically fix language mismatches in benchmark task configurations?

Yes, metadata sync automatically fixes language mismatches by optionally updating task.toml files to align with the language specifications defined in the authoritative selected_benchmark_tasks.json registry.

When do I need to sync metadata for benchmark tasks?

You need to sync metadata for benchmark tasks when onboarding new tasks or before execution, ensuring all associated metadata in task.toml files is correctly configured and preventing debugging time caused by configuration drift.