Is a prompt an AI model or a document template?

A prompt is the text of the request you make to Skyller. A document template is a ready-made file, such as a policy, that the company adapts and publishes; an AI model is the engine that writes the answer, from providers such as OpenAI and Anthropic.

Who can I share with?

With nobody, with invited people and groups or with the whole company; the reach is chosen for each prompt. Recipients join as readers or editors, and a private prompt does not appear in another person's library.

Do I need to know how to write prompts to create one?

Paste a text that already worked, or describe what you need and Skyller drafts the first version, suggesting which parts become fields. The review and the final decision are yours.

What happens when I delete a prompt the team uses?

Deleting archives it: it leaves the daily library and stays in the archive tab, from where it can come back. It is the same way to retire an old request without losing what the team built.

Platform · Prompts

The request that worked becomes the team's standard.

Keep the request that works, with fields to fill in. Anyone on the team uses it in the chat, without rewriting.

Talk to a specialist Try it free

See how it works

Skyller · Prepare a prompt

Prepare a prompt

Prompt with variables

Goal

Audience

Prompt content

Create an outline to {{objetivo}}. Consider the needs of {{publico}}.

Demonstration · illustrative data

FIELDS TO FILL IN

the person only completes what is missing

PRIVATE · TEAM · COMPANY

the creator chooses; private stays private

ONE CLICK IN CHAT

pick, fill in and the text enters the conversation

ARCHIVE WITHOUT LOSING

leaves the daily library and comes back from archive

Where this shows up in your day

The right way to ask lives with one person only.

Sales

The proposal that comes out different every time

Each person builds the summary their own way: the format changes, some item goes missing and the versions do not look like the same company.

The same format, always

Customer service

Answering a complaint without improvising

The tone, what can be promised and what must be escalated change with whoever answers.

The agreement, written down

Whoever is starting

“I don't know how to ask the AI”

The person opens the chat, looks at the empty box and gives up: nobody taught them where to start.

Starts from a ready one

How it works

From a text that worked to a team resource.

01
Write it or ask for help
The customer service lead pastes the reply that worked, or describes what she needs and Skyller drafts the first version.
02
Mark the gaps
What changes each time becomes a field, with label, filling hint, default value and whether it is required. The hint is what lets a colleague use it without asking.
03
Organise it
Title, description, categories and tags: that is how the team finds the prompt in search and filters.
04
Pick the reach
Private, with invited people and groups or with the whole company. Recipients join as readers or editors; only the owner changes the reach.
05
The team uses it
In the chat, the person picks the prompt, fills in what is missing and the text lands in the message box. The counter shows how many times it was used.

Live proof

The person fills in three fields. The rest is already there.

Starting point
A customer-reply prompt, created by the customer service lead and shared with the team.
What happens
1. 01In the chat, the person opens the prompt library and picks “Complaint reply”.
2. 02A short form appears: customer name, what happened and the agreed deadline.
3. 03The company name and today's date come already filled in; the final text lands in the message box, ready to send.
Result
The request comes out the same every time, in the tone the company set, and whoever uses it did not have to learn to write prompts.

Good to know

The prompt prepares the request; the person sends it, in the conversation.
A prompt is not an AI model or a document template: it is the text of the request.
The reach is chosen for each prompt; sharing with the team does not open it to the whole company.

Scene with a fictional company and customer; the field form and the automatic filling are the product's.

To evaluate calmly

What you can build, and who sees what.

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

Fields with rules: Each gap has a name, label, hint, default value and a required mark. If a required field is missing, the request is not assembled.
Some fields fill themselves: The person's, the company's and the brand's data and the date are filled in at the moment of use; the person only fills in what depends on them.
Create it with help: Describe what you need and Skyller writes the first version, suggesting the fields. The final wording is always yours.

Questions from whoever decides

What people ask before adopting it.

Next step

Take the text you rewrite every week.

Paste it into the library, mark what changes each time and share it with the team.