Real actions in your product, without writing code.
Frigade uses your product the way a user would, then turns the actions it can take into Skills. Review them, switch on what you want, and the assistant runs them for your users.
How should I refund this order?
Sometimes the user just wants it done.
Frigade is great at guiding users through your product, and a lot of the time that is exactly what they need. But sometimes a user does not care how something gets done. They have a result in mind, and they just want it to happen.
Skills are how Frigade gets it done. It learns the actions your product can take and runs them for the user, so they skip the workflow and go straight to the result. No steps to follow, no code to write, just the outcome inside your product.
How a Skill goes live.
Frigade uses your product
Frigade works through your product the way a user would, and the actions it can take become Skills.
You turn on what you want
You review those Skills and switch on the ones you want. No code, nothing on until you say so.
Your users just ask
When a user asks, the assistant runs the right Skill with their permissions and answers with the result.
The things your users come to do.
A Skill is whatever your product can do, so it looks different in each one. The examples below span a few kinds of tools.
You stay in control.
It runs in the user's session
A Skill executes client-side, as the signed-in user, with their permissions. The assistant cannot do anything the user could not do themselves. No spoofed cookies, no server-side tokens.
It confirms before it changes anything
Reads happen on their own. Before the assistant creates, changes, or removes anything, it checks with the user first.
Nothing on until you turn it on
No Skill runs until you review it and switch it on. You decide what the assistant can touch.
Security on your terms
Self-host in your own environment with your own LLM keys, so nothing your users do has to leave it. SOC 2 Type II, GDPR, and SSO are there when you need them.
No Skill for it? Tell Frigade with code.
Skills cover the actions Frigade can reach on its own. For anything it cannot, or a flow you want to define exactly, add your own with a tool call through the SDK, and the assistant runs it like any other Skill.
Most teams never write one. Skills cover the everyday actions out of the box.
A function you control
You define the inputs, the guardrails, and exactly what runs. The assistant only calls it when the conversation calls for it.
Runs like any other Skill
Custom tool calls sit right next to the Skills Frigade discovered, with the same confirmation and permission model.
Typed and reviewable
Tool calls live in your codebase and deploy the way the rest of your product does, so nothing is guessed at runtime.
assistant.ts
Skills build on the rest of the assistant.
Skills run on the same assistant that answers questions and guides users. When a Skill returns data, the assistant renders it as your product's own UI, a card, a table, or a confirmation, picked to fit the answer.