Fig Expert Packages and Skills
Expert packages and skills give Fig a head start on your work: packaged expertise, reusable methods, and a library that grows with your team.

Most AI products start the same way for everyone: a blank chat box. You explain who you are, what you are working on, which tools you use, the tone and format you want and what good looks like. Then you do it again in the next conversation.
Expert packages and skills remove that repetition. You set Fig up once for a kind of work, and that setup is there whenever you need it.
Expert packages
An expert package is a version of Fig set up for a specific job, workflow or domain. A sales package can know how you qualify accounts. A marketing package can know your positioning and content style. A finance package can know your reporting format. A recruiting package can know how you evaluate candidates.
A package can include:
- Instructions for how to work
- Skills for repeatable workflows
- Connectors to the tools that matter
- Templates, examples or reference files
- Standards for reports, drafts and analyses
The aim is simple: you should not have to explain your company, your role and your preferred format every time you ask for help.
Skills
Skills are the building blocks inside a package. A skill teaches Fig how to do one kind of work: a workflow, a checklist, a writing style, a research process, a report template or the steps for using a connected tool.
A customer research skill, for example, can teach Fig to read interview notes, group feedback into themes, separate real signal from one-off comments and turn the result into a product memo. A launch writing skill can teach Fig to draft release posts in your company's voice, at the right length and structure.
A prompt helps once. A skill keeps working across conversations.
Building your own
Different people need different setups. A founder might want a package for investor updates, hiring, customer follow-ups and weekly planning. A designer might want one for critique, user research and Figma handoff. A product manager might want one for feedback synthesis, product specs, launch planning and roadmap reviews.
You can start from an existing package or build one around work you repeat often. A good rule of thumb: if you keep giving Fig the same instructions, they should become a skill. If a set of skills, connectors and templates always go together, they should become a package.
Over time, a team ends up with a library of setups that capture how its best people work, and everyone can use them.


