Galaxy Query Generation (Repo Copy)

Generate natural-language Galaxy tool-recommendation queries for benchmarking.

2|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/goeckslab/galaxy-tool-recommendation-agent-benchmark --skill galaxy-query-generation-repo-copy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Galaxy Query Generation (Repo Copy)
Source: https://github.com/goeckslab/galaxy-tool-recommendation-agent-benchmark/tree/main/skills/galaxy-query-generation
Command: npx skills add https://github.com/goeckslab/galaxy-tool-recommendation-agent-benchmark --skill galaxy-query-generation-repo-copy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repo-local standard for writing Galaxy tool-recommendation queries used in benchmarking, ensuring consistency and quality across datasets and tutorials.

Core Features & Use Cases

  • Repo-local copy of the Codex skill with enforced rules for natural-language queries that request a tool recommendation.
  • Enforces constraints to avoid tutorial/GTN mentions, dataset/file references, and leakage of tool names or IDs in the query line.
  • Supports generation of both science-first and tool-first queries for benchmarking workflows in Galaxy environments.

Quick Start

Craft a natural-language query that asks for a Galaxy tool recommendation without mentioning tutorials, datasets, or specific tool names.

Frequently Asked Questions about Galaxy Query Generation (Repo Copy)

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

FAQPage Schema
What is a Galaxy tool-recommendation query for benchmarking?

A Galaxy tool-recommendation query is a natural-language prompt describing an input data type, goal, and expected output to request a tool recommendation. It is used for benchmarking across science-first and tool-first scenarios in the v1 benchmark.

How do I write a natural-language query for Galaxy tool recommendations?

Write a natural-language query that asks for a Galaxy tool recommendation by describing your input data type, analysis goal, and expected output. Avoid mentioning tutorials, datasets, or specific tool names to ensure query quality and consistency.

What distinguishes science-first from tool-first benchmarking queries in Galaxy?

Science-first benchmarking queries focus on the analytical goal and input data type, while tool-first queries start from a specific tool recommendation request. Both scenarios require describing the expected output without leaking tool names or IDs in the query line.

Can I reference specific datasets or tutorials in a Galaxy benchmark query?

No, Galaxy benchmark queries must not reference tutorials, datasets, or specific file names. The enforced constraints ensure queries remain generic and realistic by describing the data type and goal without leaking dataset-specific information or tutorial context.

When should I use a stable tool identifier in a Galaxy query?

Use a stable tool identifier in a Galaxy query only when the tool-first scenario explicitly requires referencing a specific tool. The identifier must be stable and should not leak the tool name or ID directly into the natural-language query line itself.

Does the Galaxy query generation skill support workflows outside the v1 benchmark?

The skill is specifically designed to generate queries covering science-first and tool-first scenarios across the v1 benchmark. It enforces a repo-local standard for consistency, ensuring query quality for benchmarking workflows in Galaxy environments.