CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shinka-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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced workflow with strong validation and feedback loops appropriate to a batch CLI skill. The main improvement is splitting the detailed model-validation reference into a separate file and trimming background prose.

Suggestions

Move the detailed model-membership validation rules (evo.llm_models, meta, prompt, embedding checks) into a references/ file and link to it from the workflow to improve progressive disclosure.

Trim the 'What is ShinkaEvolve?' paragraph and keep only the repo/paper links as a one-line reference to reduce background context tokens.

Consider extracting the full `shinka_run` flag matrix into a reference snippet so the main workflow stays scannable.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes competence, but the 'What is ShinkaEvolve?' background paragraph and repo/paper links are context that could be trimmed without losing actionability.

4 / 5

Actionability

Provides fully executable, copy-paste-ready `shinka_run` invocations with concrete flags and values, plus a concrete next-batch example covering the common cases.

5 / 5

Workflow Clarity

A 7-step sequence with a model-availability validation checklist, a confirm-with-user checkpoint, output verification, a stop-and-ask feedback loop, and an explicit batch control policy for a batch operation skill.

5 / 5

Progressive Disclosure

Sections are well-organized with no bundle files referenced, but the detailed inlined model-validation rules block reads like reference material and the skill exceeds 50 lines, so the simple-skill exception to reach 5 does not apply.

4 / 5

Total

18

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description that clearly states both what the skill does and when to use it, with concrete tooling and argument references. Minor room for broader trigger-term coverage.

DimensionReasoningScore

Specificity

Names the tool (`shinka_run` CLI), inputs (`evaluate.py` + `initial.<ext>`), and specific required arguments (`--results_dir`, generation count, namespaced overrides), giving several concrete parameters rather than a list of distinct actions.

4 / 5

Completeness

Explicitly answers both what (run existing ShinkaEvolve tasks via the CLI from a task directory) and when ('Use when an agent needs to launch async evolution runs quickly with required...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural domain phrasings ('launch async evolution runs quickly', 'ShinkaEvolve tasks', 'shinka_run CLI') that a user of this framework would say, though synonym/extension breadth is limited.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (ShinkaEvolve's `shinka_run` CLI) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

SakanaAI/ShinkaEvolve

Path

skills/shinka-run/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.