profile

name	profile
description	Fires during setup and daily briefing. Provides: seller identity, company/product context, competitor context, communication style, daily briefing preference, and setup-state logic. Output contract: the system always knows what has been captured and what is still missing.
user-invocable	false

Profile — Starter Setup & Identity Skill

Purpose

Holds the starter identity and setup-tracking logic for Founders OS.

What It Covers

• who the seller is
• what they sell
• who they sell to
• how they sell
• value proposition
• current offer / CTA
• ICP and disqualifiers
• top competitors
• current priorities
• communication style
• whether daily briefing is part of the user's workflow
• whether the workspace install was verified
• whether morning briefing, daily cleanup, and weekly audit agents are scheduled, manual, or not enabled
• whether daily and weekly checklist workflows are being used
• connector readiness, especially email, calendar, Drive, CRM, call recording, Apollo, Slack, Teams, and search/Tavily
• Slack / Teams selected-source intelligence readiness when used

Setup Discipline

The canonical local tracker is data/setup-status.md.

The global settings block should be written from templates/global-identity.md.

The local company context should be written to knowledge-bases/company-context.md using templates/company-context.md.

Connector status should be written to data/connectors.md using templates/connector-status.md.

Required Paths

Read:

• data/setup-status.md
• templates/company-context.md
• templates/global-identity.md
• templates/setup-status.md
• templates/connector-status.md
• data/connectors.md if present

Write:

• data/setup-status.md
• knowledge-bases/company-context.md
• data/connectors.md when connector setup runs
• append one line to data/ops.log

Tool Requirements

• Global settings write is best effort. If unavailable, provide the completed block for copy/paste and mark it in setup status.
• Connector verification must route to /connectors; do not claim live tools are connected unless available.
• Slack and Teams setup must route to /slack-setup or /teams-setup when used.

If global write is not available automatically:

• provide the completed block
• mark global_identity_copy_ready: true in data/setup-status.md
• keep moving
• still update data/setup-status.md

Install Understanding

During setup, explain that the founder installed:

• a local operating-system workspace
• eight operating workflows for the operating week
• three starter-safe operating agents that must be scheduled or run manually
• daily and weekly checklist workflows for keeping maintenance visible
• optional Slack / Teams intelligence workflows for selected-channel operating context
• an outbound SDR engine that should be activated only after the operating layer has context

Daily Briefing Use

The daily briefing should use this skill to:

• understand setup maturity
• surface setup gaps
• show what workflows have and have not been used
• show which agents are scheduled, manual, or missing
• show daily cleanup and checklist status
• show Slack / Teams digest status when configured
• show connector readiness gaps
• frame the day in the user's own context

Required Setup Fields

Setup is not complete until these fields are captured or explicitly marked unknown:

• founder name/title/company
• product/service sold
• how the company sells
• ICP and disqualifiers
• clear value proposition
• current offer or CTA if outbound will be used
• top competitors
• priorities
• communication style
• connector readiness and fallbacks