Documentation

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? and Skills (concept) first, then return to browse by domain.

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.

Where skills appear in the app

In the Skills panel, Hugo organizes skills by scope:

ScopeMeaning
Built-inCatalog skills provisioned for your organization template
Company-wideShared skills maintained by your Surfaice admin
WorkspaceSkills you or your team authored for this workspace
CatalogInstallable 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.

Skill catalog by domain

Lease & portfolio

Abstraction, CAM, renewals, co-tenancy, critical dates, Lucernex Q&A.

Store development

Permits, schedules, closeout, openings, PM/GC workloads, deal sheets.

Estimating & bids

Bid tracking, leveling, scope sheets, buyout, RFIs, change orders.

Reporting & briefings

Daily briefs, portfolio reports, deep dives, financial rollups.

Apps & automations

Document abstraction, punch walk, On Watch, recurring briefs.

Workspace admin

Skill creator, templates, contact book, chat home, integrations.

Skill contract (what every skill page should tell you)

Domain skill pages in this library follow a consistent pattern:

SectionWhat it means
TriggersExample prompts that should route to this skill
Required inputsStore #, PDF, date range, project name — what you must provide
Expected outputTable, checklist, export, Preview map, or App review workbook
Review checklistWhat a human should verify before saving or sending

If a skill misbehaves, compare your inputs to this contract and see Working with Hugo.

Skills vs freeform chat

Freeform chatSkill
Best forAd-hoc investigationRepeatable operational work
InputsConversationalOften structured (store #, PDF, date range)
OutputsAnswer + optional artifactsConsistent checklists, tables, exports
GovernanceWorkspace defaultsStricter step-by-step playbooks

How to run a skill

Open Skills or ask Hugo

Pick a skill from the panel, use /skill-name in chat, or describe the task in natural language.

Provide inputs

Store number, project name, date range, or attach the PDF/email context the skill expects.

Review output

Check citations, tables, and draft artifacts before saving or exporting.

Save deliberately

Only promote outputs you accept into workspace memory or downstream systems.

Related