Installing Skills & Presets

You don’t have to start from scratch. Pick up powerful packages built by other users and the UpServe team, and use them right away.

Where can I find them?

Type	Description	Example	Where to find it
Skills	Reusable work procedures	”Write to Notion”, “Send Slack message”	The Skills tab at the top
Agent presets	Behavior instructions + tools + skills bundled together	”SEO Blog Writer”, “Customer Support Bot”	Community tab sidebar → Market → Agent presets
Team presets	Organization templates of multiple agents	”Content Production Team”, “Data Analytics Team”	Community tab sidebar → Market → Team presets

Skills live under the top-level Skills tab, which splits into two screens: My Library (skills you’ve imported or created) and Explore (browse skills other people have published).

Agent presets and team presets live in the left sidebar of the Community tab. The sidebar is organized into a Lounge group (discussion feed), a Boards group, and a Market group (the preset catalog) — and the Market group has Agent presets and Team presets as separate items you can click straight into. On narrower screens (mobile/tablet), chip-style buttons at the top of the page replace the sidebar for jumping into Market and My Presets.

Near the bottom of the sidebar is a separate My Presets item. It brings together, on one screen, every agent and team preset you’ve created or installed from the Market, and lets you filter by kind (agent/team) and status (public/private/fork). Market is for browsing and picking; My Presets is for managing what you already have.

If you land directly on a skill’s or preset’s detail page — say, from a shared link — you can view it without signing in. Browsing the list views under Explore and Market still requires signing in, and clicking Import or Use to actually install something prompts you to sign in or sign up.

A private agent or team preset can be switched to public any time from My Presets with the Publish button. This is one-way — once it’s public, it can’t go back to private — so double-check the content before you flip it.

For a preset that belongs to an organization, only that organization’s owner can publish it. Deleting, republishing (syncing), and installing are unaffected by this and stay open to any member. Members without publish permission see the Publish button disabled, with a tooltip explaining why. Presets you create on a personal account (a one-person organization) aren’t affected, since you’re automatically the owner there.

If a preset you’ve published bundles skills that have since fallen behind the version your agent is currently using, its card on My Presets shows a warning. Republishing (syncing) the preset means the next person who installs it gets the up-to-date skills.

Installing a skill

1. Click the Skills tab at the top → go to the Explore sub-tab
2. Click the skill card you want
3. Click Import

Each skill card shows its category, an Official badge, a health score (%), install count, and version (vN) so you can judge what you’re importing at a glance.

Clicking import adds the skill to your library as a reference to the original. At first it points to the source skill directly; the moment you edit it through chat, it automatically branches into your own personal copy. The version you imported stays pinned — updates the original author publishes afterward will not affect you.

A confirmation appears right away and the skill lands in My Library, followed by a panel on the same screen for picking which agents to apply it to. You don’t have to decide now — you can always add the skill to an agent later from that agent’s settings. Skills that require an external service (e.g. Notion, Slack) need a connection configured before they can run.

To uninstall, click Remove on the same screen. It’s removed from My Library, and it’s also detached from every one of your agents that currently has it applied. If you’ve already edited the skill through chat and branched into your own copy, that copy is a separate item and keeps working. If the original author removes the skill entirely, the version you imported stays as-is and keeps working.

Besides picking a skill yourself, your agent can also decide mid-conversation that it needs a skill and propose installing one on its own. When that happens, an approval card appears first, and you have to confirm it before anything is actually installed. Updating an already-installed skill to a newer version can go through the same kind of confirmation. If the skill you’re installing contains scripts — or an update would newly add scripts like that — the confirmation screen shows a warning that the skill can access the browser session you’re already logged into. If you’re not sure about the author, treat that warning as your cue to think twice before approving.

Installing an agent preset

1. Community tab → left sidebar Market group → click Agent presets
2. Click the preset you want
3. Click Use

Customizable presets run a short interview chat before the agent is created. Answer a few questions and the agent will automatically shape its behavior and initial knowledge around your answers. Once the synthesis finishes, you may see a recommended skill bundle — pick the skills you want included. Until the interview finishes and the agent is created, it won’t show up in your agent list.

Closing the window mid-interview doesn’t erase your answers. They’re kept for 24 hours after your last reply — come back within that window and click Use on the same preset to pick up right where you left off. After 24 hours, the old answers are cleared and the interview starts over.

Presets without customization create the agent immediately after confirmation.

Behavior instructions, tools, and skills are all set automatically. Tweak the name and avatar afterwards in agent settings.

If a preset bundles a dedicated skill, you get the version the author last published or synced — not necessarily their latest work. If the author has since refined the skill further, they need to republish the preset before new installers receive the newer version.

Presets can be installed on any plan regardless of tier (Standard/Ultra). There is no limit on how many employees you can have running, so a newly installed one always joins ready to work.

Some presets also come with a web app the agent built. On the install confirmation screen for these, you’ll see a note like “This agent comes with a web app.” Clicking Use restores the web app too — but at a brand-new address (it doesn’t inherit the original URL), starting with no stored records. What travels is the files in the app directory — its code and static files like logos — while anything the app collected from visitors into a directory such as uploads stays behind. This feature is currently web-only — it isn’t available yet on the iOS or Android apps.

Picking one straight from the hire screen

There’s also a shortcut that skips the Market entirely. When you hire a new employee with the + Hire button at the top of the screen, the confirmation window that pops up may show a few popular official presets as “Experienced hires, ready to start today” cards.

Pick a card and click Hire, and that preset installs immediately — since its job and tools are already set, it skips the onboarding interview a blank new hire would otherwise go through and starts chatting right away. If you skip the cards and go through with hiring a blank new employee below, it goes through the usual interview where the new hire figures out its own name and job through conversation with you.

These cards only show up when you’re hiring into your personal account — they don’t appear when hiring into an organization’s team (to put a preset into an org team, install an agent preset from the Market and then add it to the team). It’s also fine if no cards show up, or none of them fit — the confirmation button below for hiring a blank new employee always works the same regardless of these cards.

Installing a team preset

1. Community tab → left sidebar Market group → click Team presets
2. Click the team card → click Use (on a team preset you authored, the button reads Reinstall instead)
3. On the install screen, check off just the members you want → click Use

You don’t have to install the whole team. The install screen lists the team’s members (employees) with their names and tiers, and any member you’re able to install is checked by default. Uncheck anyone you don’t want — you need at least one checked to proceed. A member you’ve already installed on your account shows an “Already installed” note and starts unchecked, but you can check it again to reinstall it.

If a member has since been removed from the original team, or made private, or otherwise can no longer be installed, its checkbox is disabled with the reason shown next to it, and it’s automatically left out of your selection. If any members were left out this way, you’ll see a summary after install telling you how many and why.

The members you actually install get a fresh, fully-open connection structure — everyone can collaborate (mention) with everyone else, even if the original team had some connections blocked. This works on any plan regardless of AI employee tiers, and there is no cap on team size — every member joins ready to work.

Picking trustworthy packages

When choosing a package under Skills → Explore or in the Community Market, look for:

• 🏷️ Official badge — Built and curated by the UpServe team
• 💚 Health score (%) — A score combining real usage, success rate, and recent activity. The higher it is, the more actively and reliably the skill is being used (skills that were just published don’t show one for a while)
• 📥 Install count — Heavily-installed packages are usually proven
• 👍 Likes & comments — Reactions and notes from other users
• 🔢 Version — A higher version often means active maintenance (sort the list by ‘Most Recent’)

Next steps

• FAQ — If something behaves oddly after install
• To build your own skills or exchange them with other AgentSkills-compatible clients, see Skills & the Autonomous Skill System

---

Advanced

Read this only if you’re curious exactly how the health score is calculated, the precise scope of uninstalling, install limits, and publishing to public, or the fine print on bundled web apps and anonymous viewing.

• Health score formula: it adds up recent 7-day usage volume (log scale, up to 25 points) + success quality (success rate × 60, up to 60 points) + recency (based on last-used date, up to 15 points), capped at 100. Success rate carries the most weight but is capped at 60 points, so a skill with a high success rate can still score low if it’s rarely used or hasn’t run recently. Newly published skills don’t get a score for the first 7 days — only their install count shows.
• Uninstall scope: Remove clears the reference from My Library, detaches the skill from every one of your agents that has it applied, and decrements the original listing’s install count by 1. A personal copy created by editing through chat (which branches into a separate item) is unaffected.
• Agent/team preset install limits: a preset’s model tier (Standard/Ultra) has no effect on whether you can install it, and there is no limit on how many agents you may run at once. An install is only ever refused when you are already holding an unusually large number of agents — a ceiling far beyond normal use.
• Bundled web apps: when publishing, an author can optionally include a web app their agent built (the app directory’s files travel; stored records and visitor uploads kept in a directory such as uploads do not; if bundling is turned on but there’s no active web app, publishing is rejected). The publish screen lists the files that are not code and asks the author to confirm before it goes out. Once install finishes, restoring the web app and issuing a fresh link happen automatically while your agent prepares its first greeting. When the author later updates the preset, they can also choose to recapture the web app — if there’s no active web app at that point, the bundle is removed from the preset. Bundled web apps are web-only for now.
• Scope of anonymous viewing: the detail pages signed-out visitors see are served through a separate public-only path that only returns information that’s safe to show anyone. Fields that only make sense when signed in (like your own reaction) and internal data such as full skill source or configuration values never travel over this path.
• Scope of Publish: it only works on presets that are currently private, and has no effect on ones already public. For a preset published from an organization-owned agent or team, only that organization’s owner can flip it to public, regardless of who originally published it — a regular member’s attempt is rejected with a permission error. The rule is identical for agent presets and team presets. Deleting, republishing (syncing), and installing aren’t subject to this restriction and stay open to any member.
• Installing your own preset: if you install a preset you authored yourself (e.g. to review it), it links to the live original skill rather than the bundled copy, so you always see the latest version. That’s different from what other users get when they install (a snapshot from publish time) — keep that in mind if you’re checking the installer experience.
• Scope of the hire-screen preset cards: up to 3 candidates, ranked by popularity, drawn only from official presets that don’t need an interview (no customization). If this card list fails to load or comes back empty, only the cards disappear — the blank-hire button’s behavior is unaffected. These cards never appear when hiring into an organization’s team, since a preset installed this way lands on your personal account and can’t be reassigned into that org’s team afterward.
• Scope of team preset partial install: the member selection screen refetches availability every time it opens, so it reflects the current state even if something changed between viewing the detail page and actually installing. If none of your selected members are still installable, the install itself is rejected. Each member you install follows the same rules as a single agent preset install (a pinned snapshot, an interview if it’s customizable).
• Scope of the browser session warning: an agent’s own attempt to install a skill always needs your approval regardless of whether the skill has scripts — this warning doesn’t create that approval requirement, it just adds one more thing to weigh when you were already going to be asked. Installing directly with Import from the skill Explore screen has no such approval step, so no warning appears there either.