Derive workflow test inputs and expected outputs from a paper.
/plugin marketplace add galaxyproject/foundry
/plugin install foundry-skills@galaxy-workflow-foundryThen invoke as:
/foundry-skills:paper-to-test-datacodex plugin marketplace add galaxyproject/foundry
codex plugin add foundry-skills@galaxy-workflow-foundryThen select with /skills or invoke explicitly as:
$paper-to-test-dataProduces: 1 artifact.
Consumes: 1 artifact.
Resolved workflow test inputs and expected outputs derived from paper evidence (URLs, file shapes, expected hashes).
{
"id": "test-data-refs",
"kind": "json",
"default_filename": "test-data-refs.json",
"description": "Resolved workflow test inputs and expected outputs derived from paper evidence (URLs, file shapes, expected hashes)."
}Free-form summary from [[summarize-paper]]; sample data and reference evidence the test fixtures derive from.
{
"id": "freeform-summary",
"description": "Free-form summary from [[summarize-paper]]; sample data and reference evidence the test fixtures derive from.",
"producers": [
"interview-to-freeform-summary",
"summarize-paper"
]
}
# paper-to-test-data
Follow the procedure below and use the artifact/reference sections as the runtime contract.
## When To Use
- Derive workflow test inputs and expected outputs from a paper.
## Inputs
- Read artifact `freeform-summary`. Produced by `interview-to-freeform-summary`, `summarize-paper`. Free-form summary from summarize-paper; sample data and reference evidence the test fixtures derive from.
## Outputs
- Write artifact `test-data-refs` as `test-data-refs.json`. Format: `json`. Resolved workflow test inputs and expected outputs derived from paper evidence (URLs, file shapes, expected hashes).
## Required Tools
- None declared. Procedure should not assume external CLIs are present.
## Load Upfront
- None declared.
## Load On Demand
- None declared.
## Validation
- None declared.
## Procedure
Read the paper free-form summary from summarize-paper and derive concrete workflow test inputs and expected outputs — resolvable URLs, file shapes, and expected hashes — emitted as `test-data-refs`.
## Feedback Mode
- Feedback mode is off unless the caller explicitly enables `--feedback` or supplies a feedback-ledger path.
- When enabled, read `_feedback.md` before doing the work and use its registered `foundry-feedback.ledger.yml` protocol.
- Preserve harness-owned run and phase state. Append only concrete observations about a canonical Foundry source asset or a related project that this run showed to be at fault; do not put ordinary workflow requirements in this ledger.
- Before reporting completion, make one explicit pass over the work you just did. Do not ask yourself whether anything was unclear — recall what happened: where you guessed at something the instructions should have settled, needed information this bundle does not carry, hit an instruction that contradicted another or contradicted the artifacts in front of you, used a packaged reference that did not cover your case, or did something the procedure never describes.
- Append an entry for each such event that clears the protocol's bar. If none do, append nothing and report `no feedback` explicitly. Silence and a clean pass are not the same thing, and nothing downstream can tell them apart unless you say which one it was.
- Pass the same ledger path to any subagent used for this work, and merge updates serially so one writer cannot overwrite another.
## Runtime Notes
- Do not read Foundry source files at runtime; use only files packaged in this skill bundle and user-supplied artifacts.
- Preserve declared artifact filenames unless the user or harness supplies explicit paths.
- Carry unresolved assumptions into the output artifact instead of silently inventing missing source evidence.