shinka-inspect
Shinka Inspect Skill
Extract the strongest programs from a Shinka run and package them into a context file that coding agents can load directly.
When to Use
Use this skill when:
- A run already produced a results directory and SQLite database
- You want to inspect top-performing programs before launching the next batch
- You want a compact context artifact instead of manually browsing the DB
Do not use this skill when:
- You still need to scaffold a task (
shinka-setup) - You need to run evolution batches (
shinka-run)
What it does
- Uses
shinka.utils.load_programs_to_dfto read program records - Ranks programs by
combined_score - Selects top-
kcorrect programs (fallback to top-koverall if no correct rows) - Writes one Markdown bundle with metadata, ranking table, feedback, and code snippets
More from sakanaai/shinkaevolve
shinka-setup
Create ShinkaEvolve task scaffolds from a target directory and task description, producing `evaluate.py` and `initial.<ext>` (multi-language). Use when asked to set up new ShinkaEvolve tasks, evaluation harnesses, or baseline programs for ShinkaEvolve.
109shinka-run
Run existing ShinkaEvolve tasks with the `shinka_run` CLI from a task directory (`evaluate.py` + `initial.<ext>`). Use when an agent needs to launch async evolution runs quickly with required `--results_dir`, generation count, and strict namespaced keyword overrides.
109shinka-convert
Convert an existing codebase in the current working directory into a ShinkaEvolve task directory by snapshotting the relevant code, adding evolve blocks, and generating `evaluate.py` plus Shinka runner/config files. Use when the user wants to optimize existing code with Shinka instead of creating a brand-new task from a natural-language description.
107