SuiteSkills Are Just Documented Processes. Most Companies Don't Have Any.
SuiteSkills let NetSuite's AI follow your company's playbook. The catch is that most companies' playbook lives in one person's head.

Of everything NetSuite showed at SuiteWorld, SuiteSkills might be the most useful. They also make the biggest assumption.
The idea is good. You write down how your company does something once, and the AI follows it every time. The assumption is that you know how your company does it, and that someone could write it down if asked. In a lot of the accounts we work in, nobody could.
What a skill actually is
Strip away the branding and a skill is a playbook written for the AI. It captures how you do a task, who approves what, and the rules that apply. When someone asks Ask Oracle to do that task, it follows the playbook instead of guessing.
NetSuite's demos used employee onboarding, equipment provisioning, and procurement. These are processes with steps, approvals, and a right answer. The pitch is that you no longer need every employee to know the process. The skill knows it.
The catch
Someone still has to write the playbook. And in most mid-market companies, the playbook is a person.
It's the AP clerk who knows which vendors get paid early and why. The controller who knows that one customer's credit memos always need a second look. The ops lead who knows the workaround for the item that never imports right. None of it is written down, because it never had to be. Everyone just asks them.
When you try to turn that into a skill, one of two things happens. Either nobody can explain the process clearly enough to write it down, or you write it down and realize there are three versions depending on who you ask.
That second one is the more useful finding. A skill can't follow a process your team doesn't agree on. If you hand the AI a vague or contradictory playbook, you don't get automation. You get your inconsistency, applied faster and to everyone.
How to get ready
You don't need NetSuite Next turned on to start. Pick three processes and write them down this month.
- Pick ones that hurt. The processes that break when one person is out, or that generate the same question in Slack every week.
- Have the person who does it explain it out loud. Record it if you have to. Write down every "oh, except when." Those exceptions are the real process.
- Ask a second person how they do it. If the answers don't match, settle it before anything else.
- Write it as rules, not a story. Who does what, what triggers it, who approves, what counts as done. If you can't write a rule, you've found a decision someone still needs to make.
Even if you never build a single skill, you'll come out with documented processes, fewer single points of failure, and new hires who can get up to speed without shadowing someone for a month.
Bottom Line
The AI part is the easy part. NetSuite built that.
The hard part is knowing what you actually do, and no release can do that for you.
Dealing with this in your own NetSuite account?
We fix exactly these problems in production. Run a free read-only health scan, or talk to a senior NetSuite consultant who has seen it before.
Written by Mike Pagani, founder of Adaptive Solutions Group — a NetSuite consultancy based in Pittsburgh, PA. Mike has been building SuiteScript automations, integrations, and NetSuite rescue projects since 2013.