AI
Skills
Skills teach the Turbofy assistant how your team works: your writing style, your release process, how you name tables, the checklist for a new client. Write the instructions once, and the assistant follows them in every chat in the workspace whenever a task matches.
What a skill is
A skill is a set of written instructions with a name and a short description. The description says what the skill is for and when to use it. The instructions say how to do it.
Skills are not loaded into every message. The assistant always sees the name and description of each skill. When your request matches a description, it loads that skill’s full instructions and follows them. So you can keep many skills without slowing the assistant down or crowding its attention.
The chat’s activity list shows which skills were used, separated by commas when there are several:
Skill activation: brand-voice, release-notesOnce loaded, a skill stays active for the rest of that conversation, as long as it is on.
Skills belong to the workspace
Unlike connectors, skills are shared. A skill applies to everyone who uses the assistant in this workspace, so a team writes its conventions down once and everyone benefits.
- Anyone who can edit the workspace can add, change, turn off and delete skills.
- Skills apply only to the workspace they were created in. Other workspaces in your organization are not affected.
- Do not put passwords, API keys or personal data in a skill. Everyone in the workspace can read it. Store credentials as
Secretsinstead.
Turbofy skills
Open AI → Skills in the workspace sidebar. Under Turbofy skills you find optional skills written and maintained by Turbofy. Each card shows a switch:
- 1Turn the switch on to make the skill available to the assistant in this workspace.
- 2Turn it off again to stop the assistant from using it. This applies from the next message on, in new and existing chats.
The assistant also has built-in skills for building on Turbofy itself: apps, blocks, flows and data. They are always on and are not listed, so you cannot turn them off by accident.
Write your own skill
- 1Open
AI→Skillsand clickNew skill. - 2Enter a
Name: lowercase letters, numbers and hyphens, up to 64 characters, such asrelease-notes. Spaces and capitals are converted for you. The name must be unique in the workspace and cannot reuse a Turbofy skill’s name. - 3Write the
Description, up to 1,024 characters. Say what the skill does and when the assistant should use it. This is the only part the assistant sees before deciding to load the skill, so it matters most. - 4Write the
Instructionsin Markdown: steps, rules, examples and templates. They can be long, up to 100,000 characters. - 5Click
Create skill. It appears underWorkspace skillsand is on right away.
Example: release notes
release-notesWrites customer-facing release notes from a list of changes.
Use when asked for release notes, a changelog or a summary of
what shipped.# Release notes
1. Group changes under: New, Improved, Fixed.
2. Write one line per change, starting with a verb
("Add", "Speed up", "Fix").
3. Describe the benefit for the customer, not the code change.
4. Leave out internal refactors and dependency updates.
5. End with a one-sentence summary for the newsletter.
## Example
### New
- Export any table to CSV from the toolbar.
### Fixed
- Fix dates showing in the wrong time zone on invoices.With this skill on, a request such as the one below makes the assistant load release-notes and follow it:
Here are this week's merged changes. Turn them into
release notes for our customers.Import a SKILL.md file
Skills follow the common SKILL.md format used by other AI assistants, so you can reuse skills you already have. In the New skill dialog, choose a SKILL.md file. Turbofy fills in the name and description from the header and the instructions from the rest of the file. Review them, then save.
---
name: brand-voice
description: Writes and edits copy in the Acme brand voice. Use for
page text, emails, product descriptions and social posts.
metadata:
author: marketing
---
# Acme brand voice
- Friendly and direct. Short sentences. No jargon.
- Say "you" and "we", never "the user" or "the company".
- Use British spelling.
- Never use exclamation marks in headlines.
## Words we avoid
- "revolutionary", "seamless", "leverage"Only name and description are read from the header. Other fields, such as metadata, are ignored. A skill is one file: if a skill you import refers to extra scripts or files next to it, paste what the assistant needs into the instructions.
Turn off, edit or delete a skill
- Use the switch on a workspace skill’s card to turn it off without deleting it. The card then reads
Off: chats don't use it. Turn it on again whenever you need it. - Open the card’s menu and choose
Editto change the description or instructions. The assistant uses the new version from the next message on. - Choose
Deleteto remove the skill for everyone in the workspace.
Tips for good skills
- Put the trigger in the description: “Use when asked for …”. A vague description such as “Helpful marketing guidance” is rarely matched.
- Keep one job per skill. Separate
brand-voiceandrelease-notesskills combine better than one large “marketing” skill. - Show, don’t only tell. A short example of the result is often clearer than a page of rules.
- Write instructions as steps and checks the assistant can follow, such as “Always add a
statusfield with the values Open and Done”. - Combine skills with connectors. A
weekly-sales-reportskill can say which HubSpot pipeline to read and how to lay out the table it builds. - Test it. Ask for a matching task in a new chat and check that the activity list shows the skill.