---
title: Company
description: Give the agent the company's profile, products, brand and skills.
sidebar:
  order: 4
---

Each organization has a company space, apart from the drive. It holds what the agent needs to know about the company: its profile, products, brand and skills. Files in this space never appear in drive listings.

Everything happens through the agent. Ask, for example, "Set up our company in Siglata from our website", and it creates the profile and the folders.

## Layout [#layout]

| Path | Contents |
| :-- | :-- |
| `empresa.md` | The profile: core fields at the top and free text below. |
| `produtos/` | Product catalogs, sheets and tables. |
| `marca/` | Logos, colors, fonts and the brand guide. |
| `skills/<name>/SKILL.md` | A company skill, with its scripts in the same folder. |

`company_get` returns this index, with each file's id and path. The operations that list or create files take `space: "company"` to work there (see [MCP](/docs/en-US/agents/mcp#tools-reference)).

## The profile [#profile]

The profile is the file `empresa.md`. Its top, between two `---` lines, holds the core fields in YAML; the text below describes what the company does, its positioning, tone and audiences.

```markdown title="empresa.md"
---
name: Café Aurora
site: https://cafeaurora.com.br
instagram: "@cafeaurora"
competitors: [Grão Nobre, Serra Alta]
markets: [São Paulo, Minas Gerais]
product_source: https://cafeaurora.com.br/produtos
---

Specialty coffee roaster in Uberaba. Warm, direct tone.
```

| Field | Contents |
| :-- | :-- |
| `name` | The company name. Required. |
| `site` | The website address, starting with `https://`. |
| `instagram`, `linkedin`, `tiktok`, `youtube`, `x` | The profile on each network. |
| `competitors` | The list of competitors. |
| `markets` | The list of markets served. |
| `product_source` | Where the products come from: a page or a file. |

An `empresa.md` with an invalid or unknown field is refused, and the answer names each field to fix. Writing a file with the same name in the same folder again replaces the previous one, which moves to trash.

Every agent connection starts with the company's name in the server instructions, which point to `company_get` for the full profile.

## Company skills [#skills]

A company skill is the folder `skills/<name>/` holding a `SKILL.md` and its scripts, such as a Sankhya extraction the whole team uses. The top of `SKILL.md` holds `name` (lowercase letters, digits and hyphens) and `description` (when to use the skill).

- Each connection's instructions count the skills and name as many as fit in the 2,048 characters Claude Code keeps.
- `skill_find` with `query` searches the name and description of every skill the connection may read, opening no file; with `name` it returns the chosen skill's `SKILL.md` text, which the agent reads before the task.
- The plugin's `company-skill` skill saves new skills here. A personal skill is `restricted` and only its creator sees it; publishing it to the organization takes the permission to change the space.

## Siglata's skills [#catalog]

Siglata publishes skills of its own, such as working with the drive, managing members, using portal logins and social listening. A company installs them instead of writing them:

- Ask the agent: `skill_catalog` lists the skills the company can install and `skill_install` installs the chosen one. When no installed skill fits a task, the agent suggests the catalog skill that does.
- An installed skill always follows Siglata's latest version and cannot be edited. To adapt one, `skill_install` with `copy: true` writes its current text as a company skill, which then takes the installed one's place.
- Any member installs a skill for themselves; a personal install shows only to its installer and to whoever gets access with `grant_set`, like a file. Installing for the whole company takes the permission to edit company details.
- Every company starts with the drive, administration and portal-login skills installed; social listening and the others are a choice. Whoever may edit company details removes an install for everyone; any member hides one for themselves.
- Installing is free; a paid skill spends credits in its operations.

The Siglata plugin ships only the `siglata` skill, which takes each task to `skill_find`, and `company-skill`. Siglata's skills come through the connection, so a new version applies without a plugin update.

## Who reads and who changes [#access]

The company space uses the same visibility and permissions as files:

- Every member reads the items visible to the organization.
- Owners and admins change the space.
- "Edit company details" is a `write` permission on the space's root folder (the `folderId` from `company_get`), given to a member or a team with `grant_set`.
- A `restricted` item is visible only to its creator and to those given access. Any member can create one, such as a personal skill; making it visible to the organization takes the permission to change the space.