Skip to content
Black Friday 50% off + 15,000 credits Ends Nov 30 Ends Nov 30 see the deal
Black Friday15,000 free credits + 50% offends Nov 30

Teach the agent how your team builds.

A skill is a folder the agent reads before it works — a SKILL.md file plus whatever supporting files it needs. Write your Elementor conventions, brand rules or QA checklist once and the agent follows them on every site it touches. Author, edit and duplicate your own skills from inside the plugin.

OUTCOME DRIVEN

Ship More Client Sites Without Hiring More People*

Outsourced
In-House
Agency Partners
WPOS

*Comparing 1 Operator + WPOS to 1× dedicated resource per category.

“WPOS enables AI to be used directly inside WordPress, saving countless hours.”

It completely changes the way my agency builds and manages websites.

Anthony D.
Anthony D. CEO, Amplus Agency 5/5 · Verified review on G2
57 Sites, One Agency
42s Build, Check, Verify
50,000 Page Store, One Site
TEACHING THE AGENT
WITH SKILLS
WITH PROMPTS ALONE
Where your conventions live
A SKILL.md file you own
In someone's head
What one contains
SKILL.md plus supporting files
A single pasted message
Starting the next site
The agent already knows them
Explain it again
Who can author them
Anyone on the team, in the plugin
Whoever wrote the prompt
Built-in skills
Read-only — duplicate to customise
Page builders they apply to
Elementor, Divi, Gutenberg
Elementor, Divi, Gutenberg
Where they are stored
On your WPOS account, not one install
Nowhere

Skills, answered.

What a skill is, where it lives, and how it changes what the agent does on your sites.

See the docs

A folder the agent reads before it works: a SKILL.md file plus any supporting files it needs. You author, edit, duplicate and delete your own skills from inside the plugin, and each one can hold up to 100KB of instructions.

Same idea, applied to WordPress. A skill is a plain-text instruction file the agent loads before it acts, so a convention you write once — your Elementor patterns, your brand rules, your review checklist — gets followed every time instead of being re-explained.

Built-in skills are read-only, so an update can never overwrite your work. Duplicate one and you get an editable copy that belongs to you.

On your WPOS account rather than inside one WordPress database, so they travel with you across the sites you run instead of being trapped in a single install.

Skills are instructions rather than templates, so they apply to whatever the agent is doing — and it works with Elementor, Divi and Gutenberg. A skill describing your layout conventions applies in all three.

That is 10Web's home turf: it markets a 90+ PageSpeed score as part of its managed hosting stack. WPOS does not manage your hosting, so performance stays a function of the host and stack you chose.

Working with skills

Built in, or written by your team

Skills are specialized abilities the agent on your site can use. They are how it gets reliably good at a specific job, like building a UI, researching in the browser or summarizing activity from a connected tool, instead of figuring it out from scratch each time.

There are two kinds. Built-in skills ship with WPOS, ready to use; examples include browser research, a component library precondition and connector activity summaries. Custom skills are your own: add a skill folder with a starter SKILL.md file that describes a procedure specific to how your team works. In the Skills surface you can browse and search installed and recommended skills and filter them by category, with built-in and custom badges showing which is which.

A good first skill is something your team already explains again and again: the way you structure an Elementor page, the brand rules a client signed off, or the checklist a site must pass before it goes live. Write it once as a checklist and the agent runs it the same way on every site you manage. Add one skill and every site you manage gets it.

Skills sit alongside two other kinds of memory, each with one job. Skills teach the agent a procedure. The Playbook tells it about one particular site: its tone, its rules and the things to avoid, kept as short, specific notes the agent reads before it works. The Design System holds the look and feel. Keeping them apart means a procedure you write for one client can be reused on the next without carrying the first client’s rules along with it.

Skills are where an agency’s repeatable know-how lives. The more you encode the way your team does a task into a skill, the more consistent the agent’s output becomes across every site you operate, and the less of that knowledge depends on one person remembering it.

Writing your own

What goes into a skill, and where it lives

A skill is a folder the agent reads before it works: a SKILL.md file that describes the procedure, plus any supporting files it needs. You author, edit, duplicate and delete your own skills from inside the plugin, and each one can hold up to 100KB of instructions.

Built-in skills are read-only, so an update can never overwrite your work. To change one, duplicate it and you get an editable copy that belongs to you.

Skills are stored on your WPOS account rather than inside one WordPress database, so they travel with you across the sites you run instead of being trapped in a single install. And because they are instructions rather than templates, they apply to whatever the agent is doing in Elementor, Divi or Gutenberg: a skill describing your layout conventions works in all three.

Keep the site-specific details out of the skill. Rules for one client, such as “never change the header menu without asking”, belong in that site’s Playbook, where the agent reads them before every chat. The skill then stays a clean procedure you can reuse on the next client without editing it first.

Where to start: open Skills in the Command Center to see what is installed and recommended, read one of the built-in skills to see how a procedure is written, then duplicate it and adapt it to your own conventions instead of starting from a blank file. The Playbook opens from the same new tab launcher and is edited like a document; its changes apply to the next conversation, and when the agent updates it itself, an activity card in the chat shows what changed.

Skills also keep work consistent as the team grows: a procedure written as a skill is followed the same way whichever operator starts the chat and whichever client site it runs on. Because a skill is plain text, it is easy to review. Read the SKILL.md before you rely on it, and update it when your conventions change, so every site picks up the new version.

Black Fridayends Nov 30

Start free with 15,000 credits.

Three times the usual 5,000, no card needed. Then 50% off your site licences for 2 months with FRIDAY50.

Claim 15,000 credits