email and list_connected_accounts. Others are almost entirely methodology — Meta Hook Engineering grants only three read tools and is 90% standing rules about how to write ad hooks. Most are somewhere in between.
The standing rules are what make skills more than a tool list. A skill can enforce hard constraints — never fabricate metrics, cost is in micros not dollars, draft-only never auto-send, recommendation-only never deploy — that hold for the entire conversation. Without the skill installed, those constraints don’t exist.
Skills vs. work plans
These solve different problems and they compose.
Reach for a skill when the reusable thing is judgment and standing rules — “here’s how we evaluate quality, always apply this lens.” Reach for a work plan when the reusable thing is a sequence with checkpoints — “do these five steps in this order, stop here for my approval.”
They connect at the step level: a work plan step can declare the skills it needs, and launching the plan auto-installs them. Mature capabilities often ship as both — Meta Ads has skills and plans that sequence them.
Built-in skills
AgentWeb ships a catalog of skills built and vetted by professional marketers and founders — the same people who built the work plans. These cover paid ads (Google, Meta, LinkedIn), organic content (LinkedIn posts, X/Twitter), outbound (email, LinkedIn outreach, cross-channel sequences), CRM and lead management, SEO, meeting intelligence, and more. You don’t need to install these manually for most work. When you ask Emma to do something, she installs the relevant skills automatically. But knowing they exist helps when you want to be specific — ask Emma “what skills do you have for Meta ads?” and she’ll list them with what each one does.Create a skill
There are two paths.Conversational: ask Emma to build it
The best skills come from work you’ve already refined. When you and Emma have developed a process that works — you’ve iterated on the rules, corrected the edge cases, and the output is consistently what you want — ask her to save it. “Make this a skill” or “Save this as a skill called [name]” works. Emma composes the skill from what you’ve built together: the rules become the system prompt, and the tools you used become the tool grants. Example — a blog review SOP: You’ve been working with Emma to review blog articles before publication. Over several conversations, you’ve dialed in the checklist: every post must reference at least one ICP persona from Market Strategy, the CTA must match the campaign goal, no unsupported claims, tone must match founder voice in Brand Guidelines, and the post must be under 1,200 words. Once that checklist is stable, say: “Make this a skill called Blog Review SOP. Every time I ask you to review a blog post, apply these rules.” Emma saves it. Next time you start a new conversation and say “review this blog post,” install the skill first — or ask Emma to install it — and she applies the full checklist without you repeating it.This is a skill because the reusable thing is judgment, not a sequence. The value is the standing rules — the checklist Emma applies every time. If your review also needed ordered steps with approval gates between them (“first check structure, then let me approve before checking tone”), that would be a work plan instead. Many SOPs could go either way; choose based on whether the order and checkpoints matter or just the rules.
Manual: build it in Settings
Go to Settings → Skills and create the skill directly. This gives you control over each field:
The manual path is better when you’re writing rules from scratch rather than capturing something you’ve already done, or when you want to edit the system prompt directly.
Skill sharing
Default: shared with your whole organization
If you belong to an organization, a skill is visible to every member of it the moment you save it. There is no per-skill privacy step and no share action to take — creating a skill stamps it with your organization, and org-wide skill sharing is on by default. Teammates see it in their own Settings → Skills list, tagged “Shared by [your name]”, and can install it in their conversations. The Private badge on a skill means “not published to all AgentWeb users.” It does not mean hidden from your organization. If you aren’t in an organization, your skills are yours alone — there’s no one to fan them out to.Turn org-wide skill sharing off
Skill sharing is one org-wide switch, not a per-skill setting. An org owner or admin can turn it off at Settings → Organization → Org-wide Sharing with the Skills toggle; plain members can’t change it and don’t see the section. With it off, each member sees only their own skills in Settings → Skills. Treat that toggle as a visibility setting, not access control. It hides other members’ skills from the lists; it does not lock a skill a teammate has already found, because Agent Mode still installs any skill carrying your organization’s ID. Keeping secrets out of skills is the protection that holds.Share with all AgentWeb users
If your skill would be valuable beyond your organization, you can submit it for review to share with the entire AgentWeb user community. Submit from Settings → Skills. The AgentWeb team reviews submissions before they go live platform-wide. Not every submission is accepted — the bar is whether the skill is general enough to be useful across different businesses and industries, rather than specific to one organization’s workflow.Tips for writing good skills
- Be specific in the system prompt. “Review content for quality” is too vague. “Check that every claim has a source, the CTA matches the campaign goal, and the word count is under 1,200” is a skill.
- State what the skill must NOT do. The best built-in skills include explicit constraints — never fabricate metrics, never auto-send, never deploy without approval. Negative rules prevent the failures that positive rules miss.
- Grant only the tools the skill needs. A blog review skill that can also send emails will eventually send an email.
- Name it for retrieval. Emma matches skill names when you ask her to install one. “Blog Review SOP” beats “My Content Quality Checker v2.”
- Test in a fresh conversation. The skill that worked when you built it had the full conversation context. A fresh chat with only the skill installed shows you what’s actually in the system prompt versus what was in your head.
Troubleshooting
Emma doesn't seem to be following the skill's rules
Emma doesn't seem to be following the skill's rules
The skill may not be installed in this conversation. Ask “what skills are active right now?” Skills don’t persist across chats — you need to install them each time, or use a work plan that installs them automatically.
The skill works in the conversation where I built it but not in a new one
The skill works in the conversation where I built it but not in a new one
The original conversation had context the skill doesn’t capture — your corrections, examples, and clarifications lived in the chat, not in the system prompt. Open the skill in Settings → Skills, read the system prompt, and add what’s missing.
I can't find a skill I created
I can't find a skill I created
Your skills appear in Settings → Skills. In conversation, ask Emma to “list my skills” or “find the skill called [name].”
My teammate can't see a skill I created
My teammate can't see a skill I created
They only see it if they’re in the same organization and org-wide skill sharing is on. An owner or admin can check the Skills toggle under Settings → Organization → Org-wide Sharing.
My platform submission was rejected
My platform submission was rejected
The bar for platform-wide publication is generality — the skill needs to work across different businesses. Rework it to be less specific to your org, or keep it as an org-shared skill where it’s already useful.
Next steps
- Work plans — ordered workflows that can auto-install skills per step.
- Agent Mode — where you build and run skills.
- Report a bug — if a skill isn’t working as expected.