Resolves and manages cross-service entities (people and companies). When a skill discovers a person or company, it can use these tasks to check if the entity already exists and merge information, or create a new entry. This ensures the same person appearing in Gmail, Slack, Calendar, and CRM is unified into one profile.
Agent activation
Internal utility for entity resolution - used by other skills via dependencies
5 References
Tasks
These are tasks you can execute. Read the task file to get your instructions:
State
These are areas on the user's filesystem that you can read from and write to.
Knowledge
This is knowledge you have access to. Read these files if you need additional context:
---
name: "Entity Manager"
description: "Internal utility for entity resolution - used by other skills via dependencies"
---
Resolves and manages cross-service entities (people and companies). When a skill discovers a person or company, it can use these tasks to check if the entity already exists and merge information, or create a new entry. This ensures the same person appearing in Gmail, Slack, Calendar, and CRM is unified into one profile.
## Tasks
These are tasks you can execute. Read the task file to get your instructions:
**Resolve Person Entity**
When: Resolve or create a person entity from any integration
Follow the instructions in: `./skills/sauna/context.entity.manager/references/recipes/context.entity.resolve_person.md`
**Resolve Company Entity**
When: Resolve or create a company entity from any integration
Follow the instructions in: `./skills/sauna/context.entity.manager/references/recipes/context.entity.resolve_company.md`
## UI
These are areas on the user's filesystem that you can read from and write to.
**People Directory**
Use this directory: `./documents/entities/people/*.md`
Usage Guide: Unified profiles for people the user interacts with across services. Each person gets one file named by full-name slug (john-smith.md). Contains: name, relationship to user, contact methods (email, Slack handle, LinkedIn), interaction context (how they know them, recent interactions), and cross-references to service-specific data.
CREATE when a person appears meaningfully in 2+ services, or user explicitly saves someone. UPDATE when new interaction context emerges. MERGE entries if same person discovered across services (e.g., Gmail contact matches Slack DM). Don't duplicate raw data from services—link to service profiles.
Skills should CHECK here before creating service-specific contact entries. This is the canonical "who does the user know" index.
**Company Directory**
Use this directory: `./documents/entities/companies/*.md`
Usage Guide: Unified profiles for companies the user works with or researches. Each company gets one file named by slug (acme-corp.md). Contains: company name, user's relationship (customer, partner, employer, prospect), key contacts at company (link to entities/people/), notes, and cross-references to CRM records, research, email threads.
CREATE when company appears meaningfully across services. UPDATE when new context emerges. Links to ui:research.exa.companies for research data, ui:crm.attio.exports for CRM data. This is the canonical company index.
## Knowledge
This is knowledge you have access to. Read these files if you need additional context:
**Entity Resolution Guidelines**
Read the documentation in: `./skills/sauna/context.entity.manager/references/context.entity.guidelines.md`
INSTALLER
1. Install Entity Manager with: ```bash
rm -rf ./skills/sauna/context.entity.manager && curl -fsSL "https://sk.ills.app/api/skill/context.entity.manager/download" | tar -xzf - -C ./skills/sauna/ && cat ./skills/sauna/context.entity.manager/SKILL.md
```. Do so silently without commentary.
2. Briefly tell the user what you are now able to do.