Product · Custom AI skills

Build your own AI skill by describing it.

No agent builder, no flow charts. Tell Taskbase the job you want done, and it builds it in 5 to 10 minutes and runs it on your schedule. Change it by telling Taskbase.

Book a meeting All products

Monday 09:00 · your skill “Weekly licence buyers”

4 companies bought a licence last week and fit your ICP

Territory DACH · ICP from your playbook · contacts with contact data

Corvin Software240 employees · Zurich · 5 licences bought

Nina BaumannHead of Salesn.baumann@corvin.example
Reto AebiVP Operationsr.aebi@corvin.example
Eva MorettiSales Directore.moretti@corvin.example

Lumeo Systems410 employees · Basel · 12 licences bought

David RothChief Revenue Officerd.roth@lumeo.example
Sara LindqvistHead of Enablements.lindqvist@lumeo.example
Jonas FreiSales Managerj.frei@lumeo.example

2 more companies

Add all to HubSpotDraft the emails

The result of a skill, every Monday at 9:00. Companies, people and contact data are fictional.

5 to 10 minto build a skill, by describing what you want

1 h+saved per rep and week by one example skill: the weekly list of licence buyers

Chatis all it takes: no agent builder to learn

From a sentence to a job that runs

1Describe itSay what you want, how often and for whom, in plain words.
2Taskbase builds itIn 5 to 10 minutes, asking only for what it is missing.
3It runsOn your schedule, in Slack, Teams or Google Chat.
4Change it by chatTell Taskbase what to change, whenever you want.

No agent builder

Not another AI agent builder to learn

Many tools make you build an agent: blocks, triggers, flows. In Taskbase the builder is the chat you already use, and the skill is part of Taskbase from the first minute.

01
Just talk
Explain the job the way you would to a colleague. Taskbase turns it into a skill, and asks one question if it needs one.
02
Part of Taskbase
A skill knows your playbook, your ICP and your tools, and shows up where your people already work. See how Taskbase works for the full picture.
03
Your own data, if you allow it
If your own tool offers an API or an MCP and you allow Taskbase in, a skill can read it. Product signups, licences, usage: whatever it holds.

Build it

Say what you want, and it exists

A client with a product-led motion had no easy way to see who had bought a licence on their own. Reps would have had to dig through the CRM, find the accounts big enough to matter, then search for people and contact data. Now a rep describes the job once, and every Monday at 9:00 gets the companies that bought a licence last week and fit the ICP, with three contacts each and their contact data.

Every Monday at 9:00, send me everyone in my territory who bought a licence last week and fits our ICP. Find three contacts per company, with contact data.

Got it. Your licences sit in your own product database. Shall I read them through its MCP?

Yes, use the MCP. My territory is DACH.

Done, built in 7 minutes. I’ll run it every Monday at 09:00 and post the result here. This week 4 companies would qualify.

New skillWeekly licence buyers

Mondays 09:00Territory: DACHICP from your playbookSource: your product database

Make it Tuesdays, and only companies with more than 200 employees.

Updated. Next run: Tuesday 09:00, companies over 200 employees.

Describing a skill, and changing it. Company, territory and numbers are fictional.

The skill is built in 5 to 10 minutes, by talking to Taskbase. It saves a rep at least an hour a week.
It reads your own tool when that tool has an API or an MCP, and you allow it.
Change it any time by telling Taskbase: another day, another filter, another channel.

See how Taskbase works

Where it runs and what it reads

Your tools, your channel

A skill reads your CRM and, through an API or an MCP, your own tools, finds contacts with the data tools you connect, and delivers in the chat your reps already use.