Skip to content
Early access

Early access: 90% off your first 3 months on Solo and Team. Ends Nov 16, 2026. What’s includedDetails

Agent setup

For the agent setting itself up: connect, verify, read the docs, write yourself a skill.

guide~2 minVerified v0.237.0

Goal

Learn the platform once, then keep durable instructions for later work.

What you'll have

A verified connection and a short skill in your harness: the app that runs your model and tools.

Needs

The person has asked you to connect. You need remote MCP support or the product skill. Connecting authorizes setup, not a first publication.

Steps

Step 1: Connect

If super_whoami is available, continue. Otherwise follow Connect your agent for the harness. The MCP address is https://superartifacts.app/mcp. Let the person approve OAuth sign-in; use a dashboard API key only when the harness needs one. Never print the key or build token files by hand.

Step 2: Verify

Call super_whoami itself. Report the handle and environment. If it fails, read the returned code and fix; a 401 needs sign-in. Stop for human sign-in when necessary.

Step 3: Read the documentation

Start at /llms.txt. Each docs page also has a .md address. Read publishing, versions, sharing, data, collections, live pages, agents, webhooks, templates, secrets and signatures.

Read /skill/SKILL.md for the page's data contract and MCP tools for argument shapes. super_help supplies focused help; agent guides cover schemas, versions, secrets and signatures.

Step 4: Write yourself a skill

Use your harness's durable skill or instruction location. Keep these rules:

  • Ask before adding data collection, inviting people or widening access.
  • Publish with visibility: "private" when private was requested. Omission uses the workspace default on creation; updates keep the existing audience.
  • Return the URL from every publication. Reuse the slug for another version. Use super_artifacts with open: true to inspect privately.
  • Visitor answers need a publish-time policy; editable workspace records need a collection. Browser storage stays in that browser.
  • A policy field keeps its first type. Defining a collection replaces its whole model: resend every field to keep.
  • Check whether a timed-out write already happened before retrying. Follow returned fix, accepts and next guidance.

Check it worked

The connection names the right workspace, your durable instructions are saved, and setup has published nothing.

If not

Explain what your harness cannot persist or connect. Do not substitute an unverified connection.

Variations

REST and SDK access is a paid-plan entitlement. Current deployment configuration records the plan check without refusing Free requests. MCP and skills stay free.

Next

Wait for the person's build request.

Keep it fresh

Refresh your skill when an unfamiliar tool, field or error appears.