More documentation for using skills

Teable Discussions
1

Can you make some more examples (blog or video) how and in what cases to use skills and how to create new one. Current videos are quite short and don’t give much of info for this. Thanks in advance!

2

Thanks for the feedback! We don’t currently have the resources to make a dedicated video tutorial, so here’s a detailed written explanation instead — hope this helps.

What Skills Are & When to Use Them

A Skill is essentially a folder containing specialized instructions, scripts, and reference material for a particular type of task. Cuppy automatically calls on it when relevant, so you don’t have to re-explain the same thing every time. Common use cases:

  • Legal teams: A skill that knows your firm’s approved contract clause library, so every NDA draft pulls from vetted language instead of generic boilerplate.

  • Customer support: A skill built around your product’s specific troubleshooting decision tree, so Cuppy follows your exact escalation process instead of giving generic advice.

  • Data teams: A skill that knows your company’s specific database schema and naming conventions, so SQL Cuppy writes actually matches your tables.

  • Marketing teams: A skill with your brand tone guide + banned phrase list, so blog drafts don’t need three rounds of “can you make it sound more like us.”

  • Solo developers: A skill that encodes your personal QA checklist, so Cuppy runs the same testing steps every time before calling a task done.

How to Create One

Use the built-in Skill Creator to turn a repeatable workflow from your conversation with Cuppy into a reusable skill.

For example, if you frequently ask Cuppy to handle something like “email screenshot → extract lead info,” once that pattern has come up in a conversation, you can use Skill Creator to turn it into a permanent skill — then just call it with / afterward instead of re-describing the task each time.

Reference Resources

1 Like