Outlit

Use when accessing Outlit customer intelligence through the `outlit` CLI or Outlit MCP tools, including customer lookups, timelines, facts, semantic search,...

Security Scan

The skill is internally consistent: it simply wraps the Outlit CLI/MCP, asks for the expected OUTLIT_API_KEY, and declares standard install options (npm/brew); nothing in the instructions or requirements is disproportionate to that purpose.

Purpose & Capability

Name/description say this integrates with Outlit customer intelligence and the skill requires the 'outlit' CLI plus OUTLIT_API_KEY. Both the declared binary and primary environment variable directly match the stated purpose and are appropriate for a CLI-based integration.

Instruction Scope

SKILL.md instructs the agent to use the outlit CLI or MCP endpoints, lists specific commands, and describes auth precedence. It does not instruct reading unrelated system files, harvesting other credentials, or sending data to unexpected endpoints.

Install Mechanism

Install options are an npm package (@outlit/cli) and a Homebrew formula (outlitai/tap/outlit). These are standard mechanisms for distributing a CLI; no downloads from ad-hoc URLs or extract-from-unknown-host behavior is declared.

Credentials

Only OUTLIT_API_KEY is required and declared as the primary credential. The SKILL.md's auth resolution (cli flag, env var, stored credentials) matches normal CLI behavior and there are no unrelated secrets requested.

Persistence & Privilege

always is false and the skill does not request system-wide config changes. The skill can be invoked autonomously by the agent (platform default), which is expected for an integration skill and not by itself a concern.

Assessment

This skill looks coherent with its description. Before installing: 1) Verify the npm package and Homebrew tap are the official Outlit distribution (check the vendor's docs and package/tap pages). 2) Use a least-privilege, rotatable OUTLIT_API_KEY and avoid reusing highly privileged keys. 3) Be mindful that CLI outputs may contain customer PII — limit what the agent is allowed to transmit externally. 4) If you allow autonomous agent invocation, consider policies or reviews for actions that access customer data. Overall this skill appears to be what it claims, but standard supply-chain and credential hygiene still apply.

Use the highest-level Outlit interface already available.

Outlit joins product activity, conversations, billing, and web signals into a unified customer context graph and timeline for agents.

Choose the interface

1. If outlit_* MCP tools are present, use MCP.
2. Else if the outlit CLI is installed, use the CLI.
3. Else guide setup:
   • Coding agents: prefer the outlit CLI plus outlit auth login. Prefer this over MCP for terminal agents.
   • MCP clients: use the workspace MCP URL from Settings > CLI & MCP. Auth may use OAuth or an API key depending on the client. Do not assume a shared hardcoded endpoint.

Quick chooser

• Browse customers: outlit_list_customers or outlit customers list
• Browse users: outlit_list_users or outlit users list
• Single account deep dive: outlit_get_customer or outlit customers get
• Chronology: outlit_get_timeline or outlit customers timeline
• Known signals for an account: outlit_get_facts or outlit facts list
• Exact fact by id: outlit facts get
• Exact source behind a fact or search hit: outlit sources get
• Specific question or topic: outlit_search_customer_context or outlit search
• Custom analytics: outlit_schema + outlit_query, or outlit schema + outlit sql

Use customer lookups before SQL. SQL is for aggregates, joins, cohorts, and custom reporting.

Working rules

• Use facts list to browse known intelligence for one account.
• Use facts get when you already have a fact id and need the canonical fact payload.
• Use sources get when a fact or search result points to a specific source and you need the exact artifact.
• Use search to answer a specific question, and timeline to inspect chronology.
• Call schema before writing SQL.
• Add explicit time filters to event SQL.
• Divide money fields by 100 for display.
• Request only the fields or include sections you need.

For ClickHouse syntax and query patterns, read references/sql-reference.md.

Output behavior

• Interactive CLI: readable tables
• Piped CLI output: automatic JSON
• Force JSON: --json
• Results include timestamps and source attribution when available

Facts vs Search vs Timeline

• Use facts list to list what Outlit already knows about an account.
• Use facts get when you already have a fact id and need that exact fact.
• Use search for a specific question or theme, including cross-customer questions.
• Use sources get when you need the exact email, call, calendar event, or ticket behind a fact or search hit.
• Use timeline when order and sequence matter.

Setup

Coding agents

npm install -g @outlit/cli   # or: brew install outlitai/tap/outlit
outlit auth login
outlit customers get acme.com --include users,revenue

Auth resolution order: --api-key, OUTLIT_API_KEY, stored credentials.

MCP clients

Get the workspace URL from Settings > CLI & MCP in Outlit.

MCP clients can authenticate with OAuth or an API key, depending on the client. Do not assume API key-only auth or OAuth-only auth.

Verify the connection with outlit_schema or outlit schema.

Docs

• Docs home: https://docs.outlit.ai/
• Agent skills: https://docs.outlit.ai/ai-integrations/skills
• CLI overview: https://docs.outlit.ai/cli/overview
• CLI commands: https://docs.outlit.ai/cli/commands
• AI agent setup: https://docs.outlit.ai/cli/ai-agents
• MCP integration: https://docs.outlit.ai/ai-integrations/mcp
• Customer context graph: https://docs.outlit.ai/concepts/customer-context-graph

Common prompts

• "What changed for this customer this week?"
• "Who is paying but inactive for 30 days?"
• "What pricing objections show up in conversations?"
• "Which channels are driving revenue?"