メニュー
Top-level Lytics CDP agent - routes user intent to the appropriate skill for audience management, profile exploration, data integration, and schema browsing. Use when the user has a general Lytics question or request that doesn't clearly map to a specific skill.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Copy metadata (segments, schema, flows, jobs, connections, auth) and account-level configuration (settings, per-table idconfig, field rankings) between Lytics accounts. Use when the user wants to promote changes from a sandbox account to production, sync objects between accounts, or copy an object from one account to another.
Strategic audience guidance -- helps users build the right audience for their business goal or improve an existing segment. Use when the user needs help choosing the right audience strategy, wants advice on segment design, or needs to improve an existing segment.
Create or update audience segments from natural language descriptions. Use when the user wants to build, create, or define an audience or segment from a natural language description.
Analyze what an audience looks like -- demographic breakdowns, top field values, coverage rates, and distributions. Use when the user wants to understand audience composition, view segment demographics, or analyze field coverage for a segment.
Guided flow/journey creation from business intent -- multi-step campaigns with delays, conditionals, A/B tests, and exports. Use when the user wants to create a campaign, build a journey, or design a multi-step marketing flow.
Browse and manage connections, auth providers, and integration credentials. Use when the user wants to list, view, create, or manage API connections, auth providers, or integration credentials.
| name | lytics-agent |
| description | Top-level Lytics CDP agent - routes user intent to the appropriate skill for audience management, profile exploration, data integration, and schema browsing. Use when the user has a general Lytics question or request that doesn't clearly map to a specific skill. |
| metadata | {"arguments":"natural language request about Lytics CDP operations"} |
Top-level intent classifier and dispatcher for Lytics CDP operations. Analyzes the user's request and routes to the appropriate specialized skill.
Requires authenticated API access. See ../references/auth.md for credential resolution and pre-flight checks.
Route based on keywords and intent:
Triggers: "create audience", "build segment", "find users who", "people that", "customers who", "target audience", "audience of"
Route to: audience-builder skill
Triggers: "list segments", "show audiences", "get segment", "segment details", "delete segment", "update segment"
Route to: segment-manager skill
Triggers: "describe audience", "audience snapshot", "what does segment look like", "audience breakdown", "analyze segment", "audience profile", "audience analytics", "audience demographics", "who is in this segment"
Route to: audience-snapshot skill
Triggers: "best audience for", "optimize audience", "help me target", "who should I target", "improve my segment", "audience strategy", "what audience should", "right audience for", "how to reach", "better audience", "refine segment"
Route to: audience-advisor skill
Triggers: "why is user in", "why isn't user in", "why not in segment", "diagnose profile", "what happened to user", "debug segment membership", "explain segment", "trace user"
Route to: profile-investigator skill
Triggers: "look up user", "find profile", "who is", "show me user", "profile for", "entity lookup"
Route to: profile-explorer skill
Triggers: "what fields", "schema", "data model", "field types", "available data", "what data do we have"
Route to: schema-manager skill
Triggers: "optimize schema", "unused fields", "schema cleanup", "field usage", "schema health", "improve schema", "inert fields", "missing mappings"
Route to: schema-optimizer skill
Triggers: "find field for", "what field matches", "map to field"
Route to: schema-discovery skill
Triggers: "connect to", "set up integration", "export to", "import from", "sync with", "send data to", "pull data from", "best way to connect", "how do I integrate"
Route to: integration-advisor skill
Triggers: "list jobs", "job status", "pause job", "resume job", "bounce job", "kill job", "job logs"
Route to: job-manager skill
Triggers: "create flow", "build campaign", "set up journey", "welcome series", "nurture campaign", "email sequence", "multi-step campaign", "A/B test flow"
Route to: campaign-flow-builder skill
Triggers: "list flows", "get flow", "delete flow", "flow status", "update flow", "pause flow"
Route to: flow-manager skill
Triggers: "why wasn't user exported", "export debug", "not showing up in", "didn't sync to", "missing from export", "why no export", "trace export", "export failed"
Route to: export-debugger skill
Triggers: "data health", "is my data flowing", "health check", "any data issues", "pipeline status", "what's broken", "data problems", "check my data", "how's my data"
Route to: data-health-monitor skill
Triggers: "stream", "events", "data flowing", "incoming data", "event log"
Route to: stream-inspector skill
Triggers: "connection", "auth", "credentials", "provider"
Route to: connection-manager skill
Triggers: "webhook template", "send to a webhook", "custom webhook destination", "Qualtrics webhook", "Slack webhook", "transform profile to webhook payload", "build a webhook payload", "webhook integration for", "send profiles to a custom URL"
Route to: webhook-template-builder skill
Triggers: "copy from sandbox to prod", "promote to prod", "sync to prod", "copy segment to another account", "sandbox to production", "promote audience", "promote flow", "copy schema between accounts", "move segment from X to Y", "sync from to ", "copy account settings", "promote settings", "sync settings between accounts", "copy idconfig", "sync account config", "promote account settings", "copy field rankings between accounts"
Route to: account-sync skill
Some requests combine multiple intents. Sequence skills in order:
"Create an audience and export to Facebook"
audience-builder skill -> create segmentintegration-advisor skill -> set up export with new segment"Find users in the high-value segment and show me one"
segment-manager skill -> get segment detailsprofile-explorer skill -> look up a member"What fields do we have for purchase data and build a segment from it"
schema-discovery skill -> find purchase fieldsaudience-builder skill -> build segment using discovered fields"Build a segment in sandbox and promote it to prod"
audience-builder skill -> create segment in sandboxaccount-sync skill -> copy the new segment from sandbox to prodIf the intent is unclear:
Example: "Show me data" could mean:
Ask: "Would you like to see your schema fields, recent streaming events, or look up a specific profile?"
All skills follow these conventions:
../references/auth.md for credential resolution../references/api-client.md for URL construction