Skip to main content
A skill is a saved playbook: a title, a description and a block of instructions that gets injected into the agent’s system prompt for that run. Use one whenever you find yourself pasting the same paragraph of context into chat repeatedly — “always check the company’s careers page”, “score every lead 1–10 against our ICP and explain why”, “format findings as a table with these columns”.

​
Premade and custom

ManyPI ships a set of system skills. On top of those you can create your own, which are private to your workspace.
Create a skill
List them with GET /api/skills — the response includes both the premade skills and your own.

​
What a skill can and cannot change

A skill shapes behaviour: what to look for, how to judge it, how to present it, what to never do. A skill cannot widen the agent’s access. Custom skills are always created with the safe tool defaults, so instructions can direct the agent but never grant it capabilities your plan or your workspace does not already have.

​
Writing a good skill

“Return a markdown table with columns Company, Fit score, Why, Source URL” beats “summarise the findings” every time.
Telling the agent what makes something not a match is usually more valuable than describing what does.
“Cite the URL you found each fact on” turns a plausible answer into a checkable one.
A skill that researches companies and writes emails and scores leads does all three worse than three separate skills.