Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →svd-ai-lab/sim-cli
Cross-solver operating discipline for sim-cli workflows — tool choice, input classification, acceptance semantics, and escalation rules that apply across solvers. Use alongside the solver's own plugin skill, which is self-contained for solver-specific work; this skill carries only the shared rules.
Passed 18 of 21 test cases with the skill, and 7 of 21 without it.
and 15 more in the full report
12 fixed8 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before running `sim check explicit_solver`, the command outputs `profile: deprecated`. What action should be taken before launching the solver job?
| Checked | Without skill | With skill |
|---|---|---|
| Requires halting execution when the solver profile is deprecated | Missed | Passed |
The instructions your model reads when the skill loads.
You are working in a sim-cli-enabled solver workflow. Use the sim
runtime where it adds control and observability, and compose solver-native
tools directly where they are the right primitive. This skill carries the
cross-solver discipline — the rules that hold across sim-cli workflows,
regardless of which solver you drive.
The solver's plugin skill is self-contained for solver-specific work: solver hard constraints, dependency chains, snippets, workflows, SDK/solver notes. It does not depend on loading this skill — but it should stay consistent with the discipline below. If a rule applies to more than one solver, it belongs here, not in a plugin skill.
The plugin skill tells you which model the solver uses. Choose the narrowest correct execution primitive; sim-cli is composable, not a universal wrapper.
| Model | Used by | Lifecycle |
|---|---|---|
| Persistent session | Drivers that hold a live process open | sim connect → sim exec × N → sim inspect → sim disconnect |
| sim-wrapped one-shot batch | Plugin wrappers that add linting, profile-aware invocation, parsing, history, or safer execution | sim check → sim run → parse_output/logs → evaluate |
| Native/tool one-shot batch | Ready solver decks/scripts, vendor batch commands, project pipelines, or post-processing tools where native execution is the right primitive | version/profile probe → native command/script → parse artifacts/logs → evaluate |
sim-cli does not try to wrap every solver operation, executable flag,
vendor batch mode, or post-processing script. Use sim when it adds a stable
control plane: solver discovery and profile checks, live sessions, bounded
exec / inspect loops, history/log capture, parsing, screenshots, or shared
agent discipline. If the artifact is already a solver-native deck/script and
the solver's own batch command is the right execution primitive, call that
native command directly instead of forcing it through sim run. Preserve
stdout/stderr, generated files, and acceptance evidence just as carefully.
Use sim run when the plugin skill says it is the canonical one-shot path or
when the wrapper adds real value. Otherwise, keep the sim-cli discipline while
composing the solver's native tools directly.
test cases passed, vs 7 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.