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

# Skills library

> How Hugo skills work in Surfaice and where to find the full capability catalog by domain.

<Note>
  **Reference catalog — not a first-day guide.** New here? Read [What is Surfaice?](/concepts/what-is-surfaice) and [Skills (concept)](/guides/skills) first, then return to browse by domain.
</Note>

**Skills** are named playbooks Hugo follows for repeatable work. Each skill defines what to do, which tools to use, and how to format outputs — lease abstraction, permit tracking, bid leveling, morning briefings, and many other operational tasks.

Skills are **not** the same as **Apps** (structured UIs like punch-walk review or document-abstraction review). Skills tell Hugo *how* to run a workflow; Apps provide guided validation surfaces for high-stakes outputs. See [Apps & automations](/skills/apps-and-automations).

## Where skills appear in the app

In the **Skills** panel, Hugo organizes skills by scope:

| Scope            | Meaning                                                              |
| ---------------- | -------------------------------------------------------------------- |
| **Built-in**     | Catalog skills provisioned for your organization template            |
| **Company-wide** | Shared skills maintained by your Surfaice admin                      |
| **Workspace**    | Skills you or your team authored for this workspace                  |
| **Catalog**      | Installable platform skills (automation creator, contact book, etc.) |

You can also invoke skills by:

* Clicking a skill in the Skills panel
* Typing `/` in chat for slash-command autocomplete
* Asking naturally — Hugo matches your request to skill `description` and `triggers`

<Tip>
  Skill availability depends on your customer workspace template and what your administrator enabled. If a skill listed here is not in your panel, ask your Surfaice admin.
</Tip>

## Skill catalog by domain

<CardGroup cols={2}>
  <Card title="Lease & portfolio" icon="file-contract" href="/skills/lease-and-portfolio">
    Abstraction, CAM, renewals, co-tenancy, critical dates, Lucernex Q\&A.
  </Card>

  <Card title="Store development" icon="building" href="/skills/store-development">
    Permits, schedules, closeout, openings, PM/GC workloads, deal sheets.
  </Card>

  <Card title="Estimating & bids" icon="calculator" href="/skills/estimating-and-bids">
    Bid tracking, leveling, scope sheets, buyout, RFIs, change orders.
  </Card>

  <Card title="Reporting & briefings" icon="chart-bar" href="/skills/reporting">
    Daily briefs, portfolio reports, deep dives, financial rollups.
  </Card>

  <Card title="Apps & automations" icon="bolt" href="/skills/apps-and-automations">
    Document abstraction, punch walk, On Watch, recurring briefs.
  </Card>

  <Card title="Workspace admin" icon="gear" href="/skills/workspace-admin">
    Skill creator, templates, contact book, chat home, integrations.
  </Card>
</CardGroup>

## Skill contract (what every skill page should tell you)

Domain skill pages in this library follow a consistent pattern:

| Section              | What it means                                                  |
| -------------------- | -------------------------------------------------------------- |
| **Triggers**         | Example prompts that should route to this skill                |
| **Required inputs**  | Store #, PDF, date range, project name — what you must provide |
| **Expected output**  | Table, checklist, export, Preview map, or App review workbook  |
| **Review checklist** | What a human should verify before saving or sending            |

If a skill misbehaves, compare your inputs to this contract and see [Working with Hugo](/guides/working-with-hugo).

## Skills vs freeform chat

|            | Freeform chat               | Skill                                       |
| ---------- | --------------------------- | ------------------------------------------- |
| Best for   | Ad-hoc investigation        | Repeatable operational work                 |
| Inputs     | Conversational              | Often structured (store #, PDF, date range) |
| Outputs    | Answer + optional artifacts | Consistent checklists, tables, exports      |
| Governance | Workspace defaults          | Stricter step-by-step playbooks             |

## How to run a skill

<Steps>
  <Step title="Open Skills or ask Hugo">
    Pick a skill from the panel, use `/skill-name` in chat, or describe the task in natural language.
  </Step>

  <Step title="Provide inputs">
    Store number, project name, date range, or attach the PDF/email context the skill expects.
  </Step>

  <Step title="Review output">
    Check citations, tables, and draft artifacts before saving or exporting.
  </Step>

  <Step title="Save deliberately">
    Only promote outputs you accept into workspace memory or downstream systems.
  </Step>
</Steps>

## Related

* [Chat with Hugo](/guides/chat-with-hugo)
* [Use cases](/use-cases/overview)
* Marketing Skills Hub: [surfaice.pro/library](https://www.surfaice.pro/library)