# Inspect Packrift Packingsolver Fixtures

Use this skill when an agent needs to inspect Packrift Benchmark Navigator fixture files, understand the source-to-packingsolver field map, or cite the public benchmark access layer.

## Inputs

- Start with `https://packrift-benchmark-navigator.vercel.app/llms.txt`.
- Enumerate public resources from `https://packrift-benchmark-navigator.vercel.app/sitemap.xml`.
- Use `https://packrift-benchmark-navigator.vercel.app/data/packingsolver-fixtures/instance-index.json` to find generated scenario file sets.
- Use `https://packrift-benchmark-navigator.vercel.app/data/packingsolver-fixtures/packingsolver-format-map.json` to understand how public Packrift source fields map into `bins.csv`, `items.csv`, and `parameters.csv`.
- Use `https://packrift-benchmark-navigator.vercel.app/data/packingsolver-fixtures/convert_box_packrift.py` when the task is to regenerate the packingsolver input folders from the public source CSVs.
- Use `https://packrift-benchmark-navigator.vercel.app/data/source-register.csv` for artifact-level citation review.

## Procedure

1. Read `llms.txt` and confirm the task is read-only benchmark inspection.
2. Load the instance index and choose scenarios by scenario family, not by claiming an optimal result.
3. Fetch the linked `bins.csv`, `items.csv`, and `parameters.csv` files for the selected scenario.
4. Use the format map to interpret fields and transformations.
5. Use the converter script only for local reproduction; do not treat regenerated outputs as third-party acceptance.
6. Cite the source register or specific public fixture files when reporting results.

## Boundaries

- No account, authentication flow, API key, bearer token, credentials, checkout, payment, or customer account access is required.
- Generated scenarios are not real customer orders.
- The fixture pack does not claim known optimal packing solutions.
- The resource is not proof of live inventory, freight approval, carrier-rate approval, checkout completion, or third-party endorsement.