← ClaudeAtlas

simmer-setuplisted

Setup subskill for simmer. Inspects the artifact or workspace, infers evaluation contracts and search space, proposes a complete assessment to the user, and produces a setup brief after confirmation. Conversational, not form-based — the agent does the work of understanding the problem, then presents what it found. Do not invoke directly — called by simmer orchestrator.
waseemnasir2k26/skynetlabs-all-claude-code · ★ 0 · AI & Automation · score 62
Install: claude install-skill waseemnasir2k26/skynetlabs-all-claude-code
# Simmer Setup Inspect the artifact, infer what "better" means and how to measure it, propose an assessment to the user, produce the setup brief that drives the entire refinement loop. **Core principle:** Inspect first, infer second, propose third, confirm last. The agent does the thinking — the user validates, adjusts, or overrides. Never ask the user to describe something the agent can read. ## Phase 1: Identify and Inspect ### Identify the Artifact Look for: - A file path mentioned or open in context - Text pasted by the user - A directory path or workspace - A description of something to generate from scratch (seedless mode) If ambiguous, ask once: ``` What are we refining? 1. A file (give me the path) 2. Something you'll paste 3. A workspace/directory (give me the path) 4. Generate from a description (I'll create the starting point) ``` Set mode and artifact type: | Mode | Artifact Type | When | |------|--------------|------| | **from-file** | single-file | User provides a file path | | **from-paste** | single-file | User pastes content | | **from-workspace** | workspace | User provides a directory path | | **seedless** | single-file or workspace | User describes what to create | ### Inspect the Artifact **For single-file (from-file or from-paste):** - Read the file/content - Identify what kind of artifact it is (prose, code, prompt, config, etc.) - Note any evaluator references (test commands, benchmark scripts mentioned in comments) - Note any output format