メニュー
Set up Spell from a fresh checkout and verify prerequisites, CLI smoke tests, and available model provider authorization. Use when helping a user get to a runnable checkout, configure API provider access, or try the first Spell example.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Navigate and develop the Spell source code. Use when modifying Spell internals, investigating evaluator/runtime/provider behavior, finding the right source files, updating tests, or explaining how the implementation fits together.
Set up Spell from a fresh checkout and run the first smoke tests or examples. Use when a user asks to install Spell, get started, verify the CLI, configure provider credentials, choose a first example, or try Spell for the first time.
Use Spell from the CLI, the Clojure API, and the Python benchmark adapter. Use when writing commands, embedding Spell in Clojure, calling Spell from benchmark Python code, or checking current API vocabulary.
Configure custom Spell agent and model profiles. Use when creating or modifying .agent.edn files, choosing namespaces, changing system prompts, wiring sub-agents, selecting provider-prefixed models, or doing agent smoke tests.
Navigate and develop the Spell source code. Use when modifying Spell internals, investigating evaluator/runtime/provider behavior, finding the right source files, updating tests, or explaining how the implementation fits together.
Create, inspect, or modify Spell model profiles and agent profile files. Use when the user asks to configure providers, add or change `.agent.edn` files, expose namespaces, define sub-agents, adjust budgets, or use `spell.api/run`.
| name | spell-setup |
| description | Set up Spell from a fresh checkout and verify prerequisites, CLI smoke tests, and available model provider authorization. Use when helping a user get to a runnable checkout, configure API provider access, or try the first Spell example. |
Spell runs from the checkout; there is no package installation step for normal use. The goal is a checkout that can run bin/spell -h, pass a no-provider smoke test, and identify which live model providers are ready.
Check Java, the Clojure CLI, and the Spell wrapper:
java -version
clj -Sdescribe
bin/spell -h
Spell expects Java 11+ and the Clojure CLI. On macOS, if clj is missing, recommend:
brew install clojure/tools/clojure
No build step is required for normal CLI use. bin/spell runs the Clojure CLI entry point with clj -M:run.
Run:
bin/spell -t "Return a short greeting"
The -t flag uses the test provider and verifies Java, Clojure, dependency resolution, and the Spell CLI path without making an LLM API call.
Before asking the user to configure a provider, check whether any supported live authorization is already present. Do not print secret values.
test -n "${OPENAI_API_KEY:-}" && echo "OPENAI_API_KEY is set" || echo "OPENAI_API_KEY is not set"
test -n "${ANTHROPIC_API_KEY:-}" && echo "ANTHROPIC_API_KEY is set" || echo "ANTHROPIC_API_KEY is not set"
test -n "${FIREWORKS_API_KEY:-}" && echo "FIREWORKS_API_KEY is set" || echo "FIREWORKS_API_KEY is not set"
test -f "$HOME/.codex/auth.json" && echo "Codex auth exists" || echo "Codex auth not found"
If one or more are configured, tell the user they are ready to use those provider paths:
codex-tc:<model>OPENAI_API_KEY: openai-tc:<model>ANTHROPIC_API_KEY: anthropic-tc:<model>FIREWORKS_API_KEY: fireworks-tc:<model>If none are configured, ask whether the user wants to set one up now. Give concise setup instructions:
OPENAI_API_KEY in the shell or shell profile.ANTHROPIC_API_KEY in the shell or shell profile.FIREWORKS_API_KEY in the shell or shell profile.codex once so ~/.codex/auth.json exists.Do not edit shell startup files unless the user explicitly asks. Model names must be exact; check provider docs before adding or recommending new model strings.
After authorization is available, try a small live task with the matching provider:
bin/spell -m openai-tc:gpt-5.4 -e hello-world