Self-learning
It learns your web app by using it, and keeps up as you ship
Give Skavelo your app’s address and, for signed in screens, a test account. It opens every screen, notes what each button and field does, and drafts walkthroughs for the tasks it finds. Then it re-learns on a schedule or after each deploy, reading only what changed.
What a learning run does
Step 1
You add your app
Its address, plus a test account if screens sit behind a login. Help docs, files and notes are optional extras.
Step 2
It explores
It opens each page, menu, tab and dialog it can reach, the way a new hire clicks around on their first day.
Step 3
It maps and drafts
It records the buttons and fields on every screen, notes what people are likely to ask there, and drafts walkthroughs.
Step 4
It keeps up
It re-learns on a schedule or after each deploy, and rereads only the pages that changed.
Safe to point at your real app
Blocks changes
While it learns, every request that would save, send or delete anything is blocked.
Skips risky options
Options like log out and delete are never clicked, so the run stays signed in and your data stays as it was.
Learns from what you give it
Public sites and help docs need no account. A test account with sample data and finished setup lets it learn the signed in screens best.
Docs, files and notes too
Add help docs, files and team notes for what the screens can’t show, like policies or the reasons behind a setting.
Shows what it opened
Each run has an activity log of what it opened on each screen, and lists anything it couldn’t reach, so you know what to add.
Rereads only what changed
Pages that haven’t changed are skipped, so re-learning after a deploy is quick.
When it re-learns
Every week
The default on Starter and above. You can switch to every day.
After each deploy
Your deploy pipeline calls the Skavelo API with an API key, and the run rereads what changed.
When you choose
Learn now in the dashboard. On Free, re-learning is once a month this way.
Questions
Set it up with Learning runs in the help center.
- Do we have to give Skavelo a login to our app?
- No. It can learn from your public pages, help docs, files and notes on their own. A test account lets it learn your signed in screens and draft walkthroughs for them.
- Will it change anything in our app while it learns?
- No. It opens pages, menus, tabs and dialogs to see what’s in them, but blocks every request that would save, send or delete anything, and skips options like log out or delete.
- How long does learning take?
- A small app takes a minute or two. Later runs reread only the pages that changed.
- How does it re-learn after a deploy?
- Add a step to your deploy pipeline that calls the Skavelo API with an API key. The run skips unchanged pages, so it’s cheap to call on every deploy. Automatic re-learning is on Starter and above.
- What if it can’t reach a screen?
- The run lists it. Give the test account access, finish its setup, or add a note or file covering that screen.
- Does Skavelo train AI models on our data?
- No. Your data and your users’ conversations never train AI models.
Add your app’s address and watch it learn. A small app takes a minute or two.
Start free