cs-agent-setup
Set up a working CodeSpring agent
Produce a working agent, not a dashboard-shaped collection of drafts. The completion artifact is a short AGENT_SETUP.md receipt in the application repo plus a real session whose replay proves the model and expected tools ran.
Assume the person does not know what an agent, model, provider key, model ID, skill, knowledge base, MCP server, tool, API key, session or published revision is. Explain the plain-English noun before asking them to use it. Give one dashboard action at a time in this form:
In the top bar, choose Acme / development. In the left sidebar, open Models. Under Provider keys, click Add key. This stores the provider account that pays for model calls; it does not choose the model for your agent yet. Success looks like a row marked active.
Never say only “publish it”, “change the model”, or “add the tool”. Name the page, section, button, exact resource and environment, then say what visible result confirms the step.
The two-layer rule
The skill must be technically complete without making the person become technical.
Behind the scenes: exact
The coding agent tracks versions, IDs, environment boundaries, API scopes, schemas, revisions, event cursors, tool contracts, origins and proof. It reads the installed SDK and application code, runs safe commands itself, and preserves the complete detail in AGENT_SETUP.md.