This is available only in a closed beta at the moment.
A skill is a folder of instructions the TrueClicks AI assistant follows, so you don't have to re-explain the same task every time you ask for it. A skill can hold your reporting style, a negative keyword policy, or a template the assistant fills with account data.
Go to Admin > AI Assistant to open the Skills management page.
Anyone can upload and manage their own private skills. Managing the skills shared with your whole organization, including overwriting and deleting them, requires Main user or AI management permissions.
What a skill contains
Skills use the standard AI skill format, so there's nothing TrueClicks-specific about how you write one.
A
SKILL.mdfile. Required. It holds the instructions the assistant follows, and supplies the skill name and description shown in the list.Optional bundled files. A skill can hold more than one file, for example an HTML template the skill populates with data.
Packaging rules:
Upload skills as a
.zip.Text files only, up to 100 KB per zip.
One zip may hold several skills, one folder per skill.
Tip: The description is what the assistant matches against when it decides whether a skill is relevant, so spell out the trigger conditions. "Use this skill whenever the user asks for a budget pacing report" works better than "Budget pacing report skill."
Platform
Every skill is tied to one platform: Google Ads, Microsoft Ads, or Meta Ads. You pick this in the upload dialog, and it shows on each row as a chip and an icon.
Skills are available in every conversation with the AI assistant, but only for accounts on the platform you selected. A Microsoft Ads skill won't be used when you're working on a Google Ads account.
Who can see and use a skill
The Applies to setting controls where a skill is available. The Existing skills list is grouped under the two options, so you can see at a glance what's shared and what isn't.
Only me: just you can see and use the skill. Nobody else in your organization knows it exists, and nobody else can manage it. Use this for your own experiments, drafts, and anything specific to how you work.
Everyone in my organization: every user in your TrueClicks account gets the skill in their AI assistant. Use this for team playbooks and shared reporting standards.
Only Main users and users with AI management permissions can select Everyone in my organization. Without those permissions, every skill you upload is private to you.
Upload a skill
Drag a
.ziponto the Upload new skill dropzone, or click it to choose a file.Check the dialog. It's titled Upload N skills and shows a count line ("7 skills, 10 files") followed by every skill folder it found, each with its name, invocation chip, file count, and description. Expand a skill to see the files it contains.
Select a Platform. Required.
Select Applies to. This defaults to Only me, and Everyone in my organization needs Main user or AI management permissions.
Click Upload.
Important: Platform and Applies to apply to every skill in the zip. If you need different settings per skill, upload them in separate zips.
Use a skill in the AI assistant
Type / in the prompt input to see the skills available to you, then pick one from the list. Each entry shows the skill name and its description, and your private skills carry an Only me badge.
You don't have to invoke a skill by command for it to be used. The assistant also picks up relevant skills on its own.
Update or delete a skill
Skills can't be edited in place. Everything goes through the dropzone.
To change the instructions or files: download the skill, edit it, then upload it again under the same name. The new version replaces the old one.
To change the platform or Applies to setting: delete the skill and upload it again with the settings you want.
Downloads and exports come back in the same
.zipformat the dropzone accepts, so you can edit a skill locally and upload it again, or hand it to a colleague.
Deleting a skill shared with your organization removes it for everyone.
Advanced: control when a skill runs
By default, a skill works both ways: the assistant uses it on its own when it's relevant, and you can invoke it directly by typing the skill name as a command in the prompt input, for example /report-branding. Leave SKILL.md alone and that's what you get, which is the right setup for almost every skill.
In the rare case where you want tighter control, two optional settings change it:
disable-model-invocation: truestops the assistant from using the skill on its own. It then runs only when you invoke it by command.user-invocable: falseremoves the command, so the skill is only used when the assistant picks it up on its own.
The chip on each row tells you which applies:
Auto: the assistant uses the skill on its own, and the command is available.
Manual only: the skill runs only when you invoke it by command.



