Evo 2 NIM

Use Evo 2 for DNA generation and, locally, layer-output extraction. Load supplemental files only when needed:

• references/api.md: exact schemas, layer names, Docker flags, hardware notes.
• references/science.md: genomic use cases, limits, and interpretation.
• references/parameters.md: generation/forward parameter effects.
• references/validation.md: DNA, probability, timing, and tensor checks.
• references/examples.md: compact hosted/local request patterns.

Instructions

For generation, use scripts/generate.py to execute the request, validate the response, and save its artifacts. Resolve the script path relative to this skill's directory and choose an output directory in the user's workspace. Use the user's sequence and requested parameters; the example below is only a smoke test.

1. Select the requested mode. For hosted generation, go directly to the generation example; Docker setup and local forward passes are separate tasks.
2. When the user asks to run generation, execute the client and inspect its exit status and result. Writing a script alone does not complete that request.
3. Report the generated DNA (or its file for long sequences), actual elapsed_ms, sampled-probability summary, seed, and artifact paths from the successful run. Read the saved response or metrics if any result is unclear.

If the request or validation fails, report the actual failure and any diagnostic files. Do not replace an unavailable API response with example values. For a code-only request, provide the command without making an inference call.

Choose Mode

Honor NIM_API_MODE when it is set. Accepted values are hosted and local. If it is unset, treat an explicit EVO2_NIM_URL as local; otherwise ask when the requested mode is unclear:

Hosted NVIDIA API or local Docker Evo 2 NIM?