> ## Documentation Index
> Fetch the complete documentation index at: https://docs.erstan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams, capabilities & example requests

> Understand what a Team installs and how Skills and Prompts appear inside Marketplace solutions.

The Marketplace presents installable products as **Agents** and **Teams**. Skills and Prompts still provide reusable expertise and curated starting points, but they now appear inside those products as **Capabilities** and **Example requests**.

## Install a Team

A Team coordinates several Agents for an end-to-end process. One installation can add its members, capabilities, example requests, templates, and connection requirements.

Open a Team card from the [Marketplace](/marketplace/overview) and review:

| Section                    | What it shows                                                                                                      |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Team overview**          | The outcome, intended users, and install state.                                                                    |
| **Team members**           | Each Agent once, in the order defined by the Team.                                                                 |
| **How the Team works**     | The declared workflow sequence. Sequence describes flow, not management hierarchy, and does not imply a team lead. |
| **Capabilities**           | Reusable expert guidance installed with the Team.                                                                  |
| **Example requests**       | Curated ways to start using the Team without exposing standalone Prompt products.                                  |
| **Templates**              | Any reusable document or work templates included in the installation.                                              |
| **Connections and safety** | Required services, live connection status, and the declared approval posture.                                      |

<Steps>
  <Step title="Open a Team">
    Choose a Team from the combined catalog or the featured Team panel.
  </Step>

  <Step title="Review members and workflow">
    Confirm the Team covers the process you need and understand how work passes between its Agents.
  </Step>

  <Step title="Check connections and safety">
    Connect required services and verify which actions are read-only or approval-gated. Unknown access remains governed by workspace tool policies.
  </Step>

  <Step title="Install the Team">
    Select **Install team**. Existing installations offer the appropriate update or sync action instead of creating duplicates.
  </Step>
</Steps>

<Warning>
  A Team can include write-capable Agents. Those actions still use each member's own NetSuite authorization and pause wherever workspace policy requires approval. Installing a Team never grants new NetSuite permissions.
</Warning>

## How Capabilities work

A Capability is backed by a workspace Skill: reusable instructions and optional references that help an Agent perform a task consistently. The Marketplace shows the outcome and access implications rather than the internal package shape.

Installed Skills remain available in the [workspace Skill library](/skills/overview), where Builders can inspect, edit, publish, and assign them to other Agents. Hiding Skills from Marketplace browse does not remove them from installed solutions or the workspace library.

## How Example requests work

Example requests are backed by Agent starters or related Prompt records. The detail page combines and deduplicates them into one practical list. Prompt records remain available to existing installation and direct-link workflows, but they are not a separate Marketplace category.

## Single-Agent solutions

Some installations combine one Agent with a larger set of capabilities and templates. The Marketplace presents these as **Agent solutions**, with an **Install solution** action, rather than showing a duplicate bundle beside the same Agent.

## Next steps

<CardGroup cols={2}>
  <Card title="Marketplace overview" icon="store" href="/marketplace/overview">
    Browse Agents and Teams by task or business category.
  </Card>

  <Card title="Adding Agents" icon="bot" href="/marketplace/add-agents">
    Review and add a focused Agent.
  </Card>

  <Card title="Skills overview" icon="puzzle" href="/skills/overview">
    Manage the capabilities available in your workspace.
  </Card>

  <Card title="Connecting NetSuite" icon="plug" href="/connectors/netsuite">
    Configure the account and per-user authorization Agents act through.
  </Card>
</CardGroup>