Outlit

v1.0.3

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

3· 376·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
Requires OAuth token
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
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.

Like a lobster shell, security has layers — review code before you run it.

latestvk9742fsv83amp7xmcy5zz0pzjh84mnn7

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🔦 Clawdis
Binsoutlit
EnvOUTLIT_API_KEY
Primary envOUTLIT_API_KEY

Install

Node
Bins: outlit
npm i -g @outlit/cli
Homebrew
Bins: outlit
brew install outlitai/tap/outlit

Comments