Which assistants work?

Claude Code, Codex, Cursor, VS Code and Claude in the browser, on Desktop and in the app have ready-made setup in Skyller. Any other assistant that accepts a remote connection with an API key also connects.

What plan does the company need?

A plan with API access; without it, the assistant is refused right at connection. With the login, anyone in the company can connect. API keys can only be generated by the administrator or by people allowed to generate their own keys.

Can the assistant see everything in the company?

No. It uses your login and sees only what you see. A key can also be restricted to specific areas, for reading or for changes.

What is recorded for IT?

Each call, with the person, the function, the result and the duration, without the content of the arguments. The limit is 600 requests per minute per person, and each connection shows the assistant and its last use.

How is this different from Integrations?

In Integrations, Skyller uses the company's systems, such as a CRM or a spreadsheet. Here it is the other way around: the outside assistant works inside Skyller, under the same rules as the person who connected it.

Platform · Claude, Codex and other assistants

Skyller inside the assistant you already use.

Claude, Claude Code, Codex, Cursor and VS Code connect to your company's Skyller and work on boards, documents, prompts and spaces with your login, within the same permissions you have on screen.

Try it free Book a demo

See how it works

Skyller · Skyller in your assistant

Skyller in your assistant

Claude Code
Codex
Cursor
VS Code
claude.ai

Open a card on the Support board with this login error and assign it to me.

Skyller · find board “Support”read

Demonstration · illustrative data

YOUR LOGIN, YOUR PERMISSIONS

the assistant sees and does only what you see and do in Skyller

CLAUDE · CODEX · CURSOR · VS CODE

with ready-made setup, including claude.ai, Desktop and the app

SIGN IN WITH YOUR LOGIN

in Claude and Codex, with no key copied into the assistant

CONFIRMATION ON CHANGES

sending email, archiving or creating a board stop for your approval

Where this shows up in your day

Three requests that end in copy and paste today.

Developers

“Open a card on the Support board with this error.”

The developer is in Codex or Claude Code, in the middle of a fix. They ask right there, and the card appears on the team board with title, description and owner, without switching windows.

The card without leaving the editor

Analysts

“What does the travel policy say about international flights?”

In claude.ai, the analyst asks and Claude searches the company knowledge base, in the documents she can read, and answers with the right passage.

The company's knowledge in Claude

Managers

“How many tickets came in yesterday and which are late?”

The manager asks in the assistant he already uses. Skyller counts the board's cards, groups them by phase and returns the late ones, only within what he is allowed to see.

The board answered in one question

How it works

Pick the assistant, sign in and ask.

01
Pick the assistant
In Settings › Skyller in your assistant, the AI assistants tab has a card for Claude Code, Codex, Cursor, VS Code and claude.ai, with where each one runs and the step-by-step setup.
02
Sign in with your login
In claude.ai, Claude Code and Codex, the browser opens the Skyller login once. In Cursor and VS Code, the connection uses an API key you generate for yourself, with the reach you choose.
03
Ask as usual
The assistant gets the most used functions and finds the others from what you asked: boards and cards, documents, prompts, hubs and workspaces, agents, presentations, automations and the Help Center.
04
Confirm what changes
Each function arrives marked as a read or a change. Sensitive ones, such as creating or archiving a board, sending email from the card and running an automation, ask for your confirmation first.
05
Disconnect whenever you want
The Connected assistants panel shows each connection and its last use, with a Disconnect button. API keys are revoked under API keys.

Live proof

The request started in Claude Code. The email waited for you.

Starting point
Marina, from the Support team, connected Claude Code to Skyller with her login. The Support board has the phases New, In analysis, In fix and Resolved, and its own inbox.
What happens
1. 01She asks to open a card with the login error. The assistant finds the board she can see and creates card #214 in New, with her as owner; creating a card goes straight through.
2. 02Then she asks to email the customer from the board's inbox. Sending email is a sensitive action: Skyller shows the recipient, subject and card and waits for Approve.
3. 03Marina approves. The email goes out from the board's address and stays in the card history, authored as “Marina (via Claude Code)”.
Result
The work moved without switching windows, within Marina's permissions, and what left the company went through her approval.

Skyller · Request made in Claude Code

Request made in Claude Code

Email the customer from the board's inbox that the login fix ships today.

Skyller · find card “SSO login error”read

Skyller · send email from the cardchanges data

Skyller asks for confirmation before sending

To: it@aurora.com · Subject: Login fix released today · Card #214, Support board.

Demonstration · illustrative data

Waiting for your confirmation

Good to know

The outside assistant does not chat with Skyller agents: it receives the agent's persona as an instruction and answers itself.
Passwords, integration keys and system credentials never go through the assistant; they are entered on the Skyller screen.
In assistants that support Skyller's confirmation, Skyller holds the action until you approve; in the others, the assistant itself asks first, unless you allowed it to act without asking.

Company, people and board are fictional; the functions, the confirmation and the record are the product's.

To evaluate calmly

What the assistant reaches, how it connects and what the company controls.

Select a topic to see its capabilities, conditions, and limits.

Boards and cards: List, search, count and group cards; read comments; create, edit, move, archive and comment; build boards, phases, fields and automations.
Documents and help: Search the knowledge base for what you can read, summarize and analyze a document and look up the Skyller Help Center.
Prompts, agents and spaces: Gallery prompts arrive ready in the assistant, and each agent becomes an instruction with its persona. Hubs and workspaces can be searched, created and organized.
Presentations, automations and connectors: Create and edit presentations, schedule and trigger automations and use the connectors the company has already enabled, with your credential.

Frequently asked questions

What IT asks before allowing it.

Start with the team's assistant

Connect the assistant the team already opens every day.

Go to AI assistants, pick the Claude, Codex or Cursor card and make the first request to the team board.