Skip to main content
Athena gives you building blocks from chat and saved Skills to Agents, AOPs (Agent Operating Procedures), Automations, User Interfaces, and full Applications. Start with the simplest step that does the job, and move to the next step only when you need what it adds. A method saved as a Skill, or an AOP that runs every week, often does the whole job without an app.

Where do I start?

Each step on Athena adds a new capability and can use the steps above it. Start at the top of the table and move down a step only when you hit the reason in the last column.
A staircase of seven steps going down from left to right. Chat: ask a question or get a task done. Skill: save how your team does a task. Agent: give your team someone to message. AOP: run the same task again and again on its own. Automation: run set steps with sign-offs and a spending cap. User Interface: show your data on a simple screen. Application: build a full app that people sign in to. An arrow down the side reads go down a step only when you need more. Footer: each step can use the ones above it.
You keep what you build as you move down the table: Agents and AOPs use your Skills, Automations call your AOPs and Agents, and Applications can start an AOP and read its result.

How do I learn each step?

Athena 101 walks you through chat, Skills, Agents, AOPs, and Applications hands-on with sample files. You build a single project, a freight dispute desk, so taking the lessons in order shows how the steps fit together. Use the product guides in the table for Automations and User Interfaces. Before people rely on what you built, read Test it before you trust it.

What does a full build look like?

Athena lets you combine these building blocks into a complete workflow, such as this invoice exception desk for a finance team. You can run the desk before you build the screen: the Automation runs each night and the controller approves fixes in Athena. Add the Application when analysts need a dedicated place to work through the list.

Which parts does an app use?

When you build an app on Athena, four questions help you pick the right parts for running code, doing the work, storing data, and reaching other systems.
Four questions, each with its parts. Where does it run? User Interface, a simple screen with no server; Computer, where Athena builds and tests; Application, the finished app people use. What does the work? Chat, one-off tasks; AOP, the same task again and again; Automation, set steps in a set order; Agent, a teammate people can message. Where is the data kept? Database, when the app saves records; Spreadsheet, when people check the numbers. How does it reach other systems? Lakehouse, a copy for analysis; Connector or MCP, read or change the original. Application, Automation, Database and Connector or MCP are highlighted as the parts a typical app uses.
The guides on Application, Computer or User Interface, AOP, Automation or Agent, Database or spreadsheet, and Lakehouse or live connector explain each choice.

What should I use for my task?

What to plan for

Start with the lightest step that fits so you take on only the setup and maintenance you need. A Skill requires no releases, sign-in, or database management, whereas an Application includes all three. Check with your admin before you plan around Applications, Automations, the lakehouse, or databases, as your Athena setup decides which of these are available. Pick the step that covers your requirements, since each step has limits: use an Automation when you need approval steps between stages (an AOP has none), put a Skill inside an AOP or Automation when it needs to run on its own, and use an Athena-managed database when you need to stop duplicate records (a spreadsheet cannot). The linked pages explain each limit.

Questions teams ask

Describe what you need and ask which steps fit. Athena explains the options and builds with the ones you pick. Naming the step in your request gives a more predictable result.
Yes, and your data and instructions carry over. You can add a Skill to an Agent or an AOP, turn an AOP into an Automation draft, turn a User Interface into an Application, and load a spreadsheet into a database.
No. Start directly at the step that fits your job. If you already know people will enter records all day, start with an Application.

See it work

Thirty minutes, your workflow, and you leave with the work product.