Teach it once, and it works that way every time
A skill is a written instruction an agent follows: your clause checklist, your house style, the way your team formats a client report. Write it down once and every agent that has the skill does the job your way.
A skill is a folder with instructions in it
Nothing exotic. A name, a description of when to use it, and the instructions themselves in plain Markdown. An agent reads it the way a new colleague would read a handover note.
Where a job needs more than prose, a skill can carry helper code alongside the instructions, and the agent uses that instead of working it out from scratch each time.
13 skills ship with Mantaq
Five are available to every workspace. The other eight come with an app, and only appear for people whose account can actually reach it.
Available to everyone
company-searchSearch everything the workspace has connectedbrowserRead pages and use a browser to reach what has no APIpptxRead and produce PowerPoint decksimage-generationGenerate and edit imagescraft-documentationAnswer questions about how the platform itself worksArrive with a connected app
An administrator connects the app; the skill then shows up for the people whose own credentials reach it, and stays hidden for everyone else.
gmailGmailgoogle-driveDrive, Docs, Sheets and Slidesgoogle-calendarGoogle CalendarslackSlacknotionNotionlinearLineargithubGitHubhubspotHubSpotThe ones that matter are the ones you write
Built-in skills handle the generic work. The skills that make agents useful are the ones carrying how your company actually does things.
Write it down
Take the checklist that currently lives in one person's head, or in a document nobody opens, and write it as instructions. If a new starter could follow it, an agent can.
Upload it
An administrator uploads the skill as a bundle. Mantaq checks it is valid before it can be used, and records a checksum so you can tell whether what is running is what you uploaded.
Share it
A skill is shared like an agent: with a person, a group or the workspace, as an editor who can change it or a viewer who can only use it.
Skills arrive with the sandbox
Skills are not baked into an image somewhere. They are pushed into the sandbox when a session starts, so editing a skill changes the next run rather than requiring anything to be rebuilt or redeployed.
Correct it once
When an agent gets something wrong in a way that will recur, the fix belongs in a skill rather than in that one conversation. Change the instruction and every agent using it follows the new version.
Credentials stay out of it
A skill never carries secrets. App-backed skills reach their app through the same egress proxy the agent uses, which attaches credentials on the way out.
Start with the thing you keep explaining
Whatever you find yourself repeating to every new starter is usually the first skill worth writing down.