How to master Ultron in one weekend

Most people open Ultron in a browser tab, ask a few questions, decide AI is not ready yet, and never learn they were using the weakest version of it the whole time.

This guide walks you through 6 weekend steps that take Ultron from a chat tool to a real teammate. No coding. No overwhelm. Just two afternoons.

No coding required. Just plain English the whole way.

Step 1: install Ultron

The installed version of Ultron can read your files, send your emails, post in your team chat, and run scheduled jobs. Same Ultron under the hood, way more capability.

Install in 3 steps:

• Go to ultron.ai/install
• Copy the one-line install command for your operating system
• Paste it into Terminal (Mac or Linux) or PowerShell (Windows) and press enter

Launch it. When the install finishes, type ultron in your terminal and press enter. A browser tab opens for you to log in. Authorize, return to the terminal, and you are in.

Test it. Type what can you do in this folder? and press enter. Ultron lists everything it can read, write, and run from where you ran the command.

Full docs live at docs.ultron.com/quickstart.

Step 2: pick the right Ultron for the job

Ultron shows up in four places. Each is built for a different job. Picking the right one is half the work.

1. Chat (ultron.ai) Quick questions, brainstorming, throwaway thinking. Inside Chat there is a feature called Projects, a folder where you can attach files and keep a recurring conversation that always remembers them.

2. Ultron Design (ultron.ai/design) Released April 2026. Built for people without a design background. Describe what you want, Ultron builds the first draft, and you refine inline. Exports to presentation, PDF, and HTML formats.

3. Ultron Cowork Task hand-off. You describe a job, Ultron works on it independently in the background, and delivers a finished result.

4. Ultron on your machine The version you just installed. Skills, MCPs, scheduled Routines, the whole automation layer.

Decision shortcut:

• "I have a question" goes to Chat
• "I need a design or visual" goes to Ultron Design
• "I need a task done in the background" goes to Ultron Cowork
• "I want to automate something forever" goes to the installed version

Step 3: save your prompts as skills

Every reel script needs the same setup prompt. Every email needs the same voice rules. Every spreadsheet analysis needs the same KPI list. Retyping each one from scratch wastes the best part of your day.

A skill fixes this. A skill is a small file Ultron reads automatically the moment a task matches its description.

Where skills live:

• ~/.ultron/skills/ for skills available in every project
• .ultron/skills/ (inside any folder) for project-specific skills

File format:

Each skill is a folder with a SKILL.md file inside. The file has a short frontmatter header that tells Ultron when to fire it, then a body with the actual instructions.

Example: a brand-voice skill at ~/.ultron/skills/brand-voice/SKILL.md

Three skills to write this weekend:

• brand-voice (above) catches AI cliché in everything you write
• summary takes any long document, transcript, or article and gives you the 5 most important takeaways
• planner given a goal, breaks it into a weekly action plan with dates and dependencies

Each takes 10 minutes to write. Saves an hour a day.

Trigger a skill manually: type /skill-name (for example, /brand-voice). Otherwise Ultron auto-fires it when the task matches.

Pro tip: start every skill description with the words "Use whenever" or "Use when". Clarity in the description equals reliability in the trigger.

Step 4: schedule Ultron to run while you sleep (Routines)

The biggest leverage shows up when Ultron works without you opening anything.

The feature is called Routines. It runs on Ultron's cloud, not your laptop. You describe a recurring job, set the schedule, and walk away. Laptop can be off. Phone in another room. The job still runs.

Requirements: Ultron Pro, Max, Team, or Enterprise with Ultron on the web enabled.

Set up your first Routine:

• Open the installed version (type ultron in terminal)
• Type /schedule followed by a plain-English description. Examples:
• /schedule daily inbox triage at 7am
• /schedule weekly project recap every Friday at 4pm
• /schedule monthly P&L summary on the 1st of each month
• Ultron walks you through the rest (what data to pull, where to deliver the output, what format)
• Confirm. The Routine is live.

Useful follow-up commands:

• /schedule list to see all your active Routines
• /schedule update to change an existing one
• /schedule run to trigger immediately for testing

You can also manage Routines visually at ultron.ai/routines. The web interface lets you trigger them from API calls or code-host events on top of the schedule.

Example Routine worth wiring up: every weekday at 7am, Ultron pulls your Meta ad spend, ROAS, and top 3 creatives from yesterday. It writes a one-paragraph summary of what changed. It drops that in your team chat. You read it with breakfast.

Other Routines worth setting up:

• Daily inbox triage (every morning, summarize unread email, flag anything urgent)
• Weekly content recap (every Friday, what shipped plus what is overdue plus next week's priorities)
• Monthly P&L (every 1st, pull payments and ad spend, write a one-page financial summary)

Step 5: plug Ultron into the apps you already use (MCPs)

Skills are how Ultron knows what to do. MCPs are how Ultron reaches into the apps that hold your work.

MCP stands for Model Context Protocol. In plain English, an MCP is a cable that connects Ultron to a tool you already use. With MCPs installed, you stop copying and pasting between tabs. Ultron reads from your notes app, posts in your team chat, pulls from your payments platform, and writes to your cloud storage, directly.

To install your first MCP:

• In your terminal, type ultron mcp add <tool> (using the name of the app you want)
• Ultron walks you through the auth flow. Log in, authorize, done.
• Test it. Type pull my latest content board and tell me what is missing

Pick MCPs by problem, not by hype.

The mistake every new user makes is installing 15 MCPs they will never use. Do not. Ask one question: what do I do every week that makes me open three or more tabs? Connect those tools first.

Common starter MCPs:

• Notes and docs app: content boards, project trackers, knowledge base
• Email: inbox triage, draft replies, summarize threads
• Team chat: read channels, post messages, summarize discussions
• Cloud storage: read and write files
• Payments platform: pull revenue, list customers, track payments
• Code host: issues, PRs, commits

Browse the full directory of available MCP servers online. New servers are added weekly.

Example prompts after install:

• "Pull last month's revenue and post it in #wins" runs in 4 seconds
• "Draft a reply to every unread email tagged 'client'" runs in 12 seconds
• "Summarize this week's content board and flag what is overdue" runs in 20 seconds

Step 6: write your ULTRON.md

This is the file that makes everything else click. Skills, MCPs, and Routines all work better when ULTRON.md is in place.

ULTRON.md is the foundation file Ultron reads automatically every single session. It is where you tell Ultron who you are, what you do, what you are working on, and how you like to be talked to.

Three valid locations:

• ~/.ultron/ULTRON.md global, loads in every project
• ./ULTRON.md project root, loads in that folder only
• ./.ultron/ULTRON.md alternative project location

Project-level rules take precedence over global. You can have both.

To create yours:

• Open any plain-text editor
• Create a new file called ULTRON.md
• Save it in ~/.ultron/ (your home directory)
• Use the template below

Paste-ready template:

When to use ULTRON.md vs a skill:

Use ULTRON.md for persistent instructions every session (who you are, voice, defaults). Use skills for task-specific workflows that load on demand (writing a script, auditing an ad, generating a carousel).

Size guidance: target under 200 lines per ULTRON.md. Longer works, but tighter loads faster.

Bonus: a per-project ULTRON.md.

If you work across multiple projects, give each one its own folder and its own ULTRON.md. Open the folder, and Ultron becomes that project's brain. Same setup, different context.

Quick reference