{
  "schemaVersion": "1.0",
  "item": {
    "slug": "outlit-sdk",
    "name": "Outlit SDK",
    "source": "tencent",
    "type": "skill",
    "category": "AI 智能",
    "sourceUrl": "https://clawhub.ai/leo-paz/outlit-sdk",
    "canonicalUrl": "https://clawhub.ai/leo-paz/outlit-sdk",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/outlit-sdk",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=outlit-sdk",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/outlit-sdk"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/outlit-sdk",
    "agentPageUrl": "https://openagent3.xyz/skills/outlit-sdk/agent",
    "manifestUrl": "https://openagent3.xyz/skills/outlit-sdk/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/outlit-sdk/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Outlit SDK Integration",
        "body": "Decision-tree-driven guide for integrating Outlit customer journey tracking. Detects what it can from the codebase, asks only what it must, and links to official docs for implementation details."
      },
      {
        "title": "Branching Check",
        "body": "Before anything else, check if Outlit is already installed:\n\nLook for @outlit/browser, @outlit/node, or outlit (Rust crate) in package.json or Cargo.toml\nIf not installed -> go to Phase 1: Quick Connect\nIf already installed -> go to Already Installed"
      },
      {
        "title": "Already Installed",
        "body": "Ask the user what they need help with:\n\nAdd event tracking -> Run detection, then go to Decision 7: Event Tracking. Fetch the relevant framework doc from the Doc URL Map for implementation patterns.\nAdd/change auth integration -> Run detection, then go to Decision 3: Auth & Identity. Fetch the framework doc and identity resolution doc.\nAdd consent management -> Go to Decision 2: Consent Stance. Fetch the framework doc's consent section.\nAdd server-side tracking -> Go to Decision 1: App Type & SDK for the server package, then fetch the Node.js or Rust doc.\nAdd billing/Stripe integration -> Go to Decision 6: Billing Integration. Fetch the customer journey doc.\nAdd activation tracking -> Go to Decision 5: Activation Event. Fetch the customer journey doc.\nMigrate from other analytics -> Run detection, then go to Decision 4: Existing Analytics.\nDebug/troubleshoot -> Go to Troubleshooting."
      },
      {
        "title": "Phase 1: Quick Connect",
        "body": "Goal: get events flowing in ~2 minutes so the user sees \"Connected\" on their Outlit onboarding screen. Zero user decisions required."
      },
      {
        "title": "Step 1: Detect Framework & Package Manager",
        "body": "Use glob/grep to check:\n\nFramework: Check package.json dependencies for next, vue, nuxt, react, svelte, @sveltejs/kit, @angular/core, astro, express, fastify. Check for Cargo.toml with tauri or outlit.\nPackage manager: Check for bun.lockb (bun), pnpm-lock.yaml (pnpm), yarn.lock (yarn), package-lock.json (npm). Use the first match found."
      },
      {
        "title": "Step 2: Install SDK",
        "body": "Based on detected framework:\n\nBrowser app (React, Next.js, Vue, Nuxt, Svelte, Angular, Astro) -> @outlit/browser\nServer app (Express, Fastify, Node.js) -> @outlit/node\nTauri -> outlit Rust crate via cargo add outlit\nElectron -> @outlit/browser\n\nInstall using the detected package manager."
      },
      {
        "title": "Step 3: Add Public Key",
        "body": "Ask the user for their Outlit public key. They get it from Outlit dashboard -> Settings -> Website Tracking or from the onboarding screen.\n\nAdd to environment variables with the correct framework prefix:\n\nFrameworkEnv varNext.jsNEXT_PUBLIC_OUTLIT_KEYVite (Vue, Svelte, React+Vite)VITE_OUTLIT_KEYCreate React AppREACT_APP_OUTLIT_KEYNuxtNUXT_PUBLIC_OUTLIT_KEYAngularAdd to environment.tsAstroPUBLIC_OUTLIT_KEYServer appsOUTLIT_KEY"
      },
      {
        "title": "Step 4: Minimal Setup",
        "body": "Fetch the framework-specific doc from the Doc URL Map and implement only the minimal setup — provider/init with just the publicKey, no auth, no consent, no custom events.\n\nFor React-based frameworks this means wrapping the app with OutlitProvider. For Vue it means installing the OutlitPlugin. For server apps it means creating an Outlit instance."
      },
      {
        "title": "Step 5: Verify Connection",
        "body": "Tell the user to:\n\nRun their dev server\nOpen the app in a browser\nCheck the Outlit onboarding screen for the \"Connected\" badge\nOr check DevTools -> Network for requests to app.outlit.ai/api/i/v1/... returning 200\n\nOnce connected, ask: \"Events are flowing. Ready to set up the full integration?\"\n\nIf yes -> continue to Phase 2. If no -> they can come back later (the skill will detect the existing install)."
      },
      {
        "title": "Phase 2: Full Integration",
        "body": "Run the full detection first, then walk through each decision."
      },
      {
        "title": "Full Detection",
        "body": "Use grep/glob to detect all of the following before starting the decision tree:\n\nSignalHow to detectAuth providerDeps: @clerk/nextjs, @clerk/clerk-react, next-auth, @auth/core, @supabase/auth-helpers-nextjs, @supabase/ssr, @auth0/auth0-react, @auth0/nextjs-auth0, firebase, @firebase/authBilling providerDeps: stripe, @stripe/stripe-js, @paddle/paddle-js, chargebeeExisting analyticsDeps: posthog-js, @posthog/node, @amplitude/analytics-browser, @amplitude/analytics-node, mixpanel-browser, @segment/analytics-next, @segment/analytics-nodeAnalytics abstractionGrep for files named analytics.ts, analytics.js, tracking.ts, tracking.js in lib/, utils/, helpers/, services/ that import 2+ analytics librariesEU/consent signalsDeps: cookiebot, @onetrust/*, cookie-consent, or grep for existing consent/cookie banner componentsApp typeDeps: @tauri-apps/api, electron, react-nativeActivation patternsGrep for onboarding routes/components, \"first\" resource creation handlers, invite flows\n\nPresent a summary of what was detected to the user before proceeding."
      },
      {
        "title": "Decision 1: App Type & SDK Package",
        "body": "Auto-resolved from Phase 1 detection. If hybrid (e.g., Next.js with API routes that need server tracking), install both @outlit/browser and @outlit/node.\n\nElectron -> @outlit/browser\nTauri -> outlit Rust crate\nReact Native -> @outlit/browser (uses fingerprint instead of cookies)"
      },
      {
        "title": "Decision 2: Consent Stance",
        "body": "DetectionRecommendationExisting CMP/cookie banner libraryautoTrack: false, integrate with their existing CMP's consent callback to call enableTracking()EU signals but no CMPautoTrack: false, mention they need a consent solution but don't build one unless askedNo EU signalsautoTrack: true — simpler, uses cookies immediately\n\nAlways explain the tradeoff: autoTrack: true starts tracking with cookies immediately. autoTrack: false waits until enableTracking() is called after user consent.\n\nFetch the relevant framework doc for consent implementation patterns."
      },
      {
        "title": "Decision 3: Auth & Identity",
        "body": "DetectionRecommendationReact/Vue with OutlitProvider/OutlitPluginPass user prop with { email, userId } after auth resolves. No manual identify() needed.Vanilla JS / script tagCall outlit.identify({ email, userId }) client-side right after auth completesServer-only (Node/Rust)Call outlit.identify() server-side for event attribution\n\nCritical: Client-side identify() (or the user prop) links the anonymous cookie/visitorId to a real person. This must happen after the auth flow completes. Server-side identify() is for attributing server events to a known user, but doesn't link browsing history.\n\nIf an auth provider was detected, fetch the framework doc and the identity resolution doc for the specific auth provider pattern."
      },
      {
        "title": "Decision 4: Existing Analytics Strategy",
        "body": "DetectionRecommendationExisting analytics abstraction (e.g., lib/analytics.ts wrapping PostHog + Amplitude)Add Outlit as another provider inside the existing abstractionScattered direct calls (e.g., posthog.capture() in 15 files)Tell the user: \"I found [N] direct [PostHog/Amplitude] calls across [N] files. Want me to create an analytics wrapper that calls both, or add Outlit calls alongside the existing ones?\"No existing analyticsAdd Outlit directly, no wrapper needed\n\nThe goal is minimal code changes. Don't reorganize their project."
      },
      {
        "title": "Decision 5: Activation Event",
        "body": "The activation event marks when a user first gets real value from the product. This is NOT just completing onboarding.\n\nScan the codebase for value-moment patterns:\n\nFirst resource/project/item created\nFirst core feature used (e.g., first message sent, first report generated)\nFirst invite to a teammate\nFirst successful integration/connection\n\n\nIf a clear value moment is found -> suggest it: \"It looks like creating their first [X] could be your activation event — is that where users first get value?\"\nIf only an onboarding flow is found -> mention it as a fallback: \"I see an onboarding flow, but activation usually maps to when users get real value, not just completing setup. What action means a user has truly gotten value from your product?\"\nIf nothing obvious -> ask: \"What action means a user has gotten real value from your product? That's where user.activate() should go.\"\n\nFetch the customer journey doc for user.activate() implementation."
      },
      {
        "title": "Decision 6: Billing Integration",
        "body": "DetectionRecommendationStripe in dependenciesRecommend the Stripe webhook integration — it automatically handles customer.paid(), customer.trialing(), customer.churned() based on Stripe events. Fetch the customer journey doc for webhook setup.Other billing provider (Paddle, Chargebee)Guide manual customer.paid() / customer.trialing() / customer.churned() calls in their existing webhook handlersNo billing provider detectedSkip. Mention it's available when they add billing."
      },
      {
        "title": "Decision 7: Event Tracking",
        "body": "Pageviews are tracked automatically by default. For custom events:\n\nScan the codebase for existing analytics calls, user action handlers, form submissions, key button clicks\nSuggest a list of events based on what the codebase reveals (e.g., form_submitted, feature_used, item_created, search_performed)\nAsk the user to confirm, modify, or add to the list before implementing\nUse snake_case for all event names\n\nFetch the framework doc for the track() API pattern."
      },
      {
        "title": "Doc URL Map",
        "body": "Fetch these docs as needed for implementation details. Always prefer linking to docs over hardcoding patterns.\n\nTopicURLQuickstarthttps://docs.outlit.ai/tracking/quickstartHow tracking workshttps://docs.outlit.ai/tracking/how-it-worksNPM packagehttps://docs.outlit.ai/tracking/browser/npmReacthttps://docs.outlit.ai/tracking/browser/reactNext.jshttps://docs.outlit.ai/tracking/browser/nextjsVue 3https://docs.outlit.ai/tracking/browser/vueNuxthttps://docs.outlit.ai/tracking/browser/nuxtSvelteKithttps://docs.outlit.ai/tracking/browser/sveltekitAngularhttps://docs.outlit.ai/tracking/browser/angularAstrohttps://docs.outlit.ai/tracking/browser/astroScript taghttps://docs.outlit.ai/tracking/browser/scriptCalendar embedshttps://docs.outlit.ai/tracking/browser/calendar-embedsNode.jshttps://docs.outlit.ai/tracking/server/nodejsRust / Taurihttps://docs.outlit.ai/tracking/server/rustIdentity resolutionhttps://docs.outlit.ai/concepts/identity-resolutionAnonymous trackinghttps://docs.outlit.ai/concepts/anonymous-trackingCustomer journeyhttps://docs.outlit.ai/concepts/customer-journeyMCP integrationhttps://docs.outlit.ai/ai-integrations/mcpIngest APIhttps://docs.outlit.ai/api-reference/ingestAPI introductionhttps://docs.outlit.ai/api-reference/introductionFull docs indexhttps://docs.outlit.ai/llms.txt"
      },
      {
        "title": "No events in dashboard",
        "body": "Verify the public key env var has the correct framework prefix (NEXT_PUBLIC_, VITE_, REACT_APP_, etc.)\nConfirm the provider/init wraps the entire app or runs at startup\nCheck autoTrack setting — if false, enableTracking() must be called after consent\nCheck DevTools -> Network for requests to app.outlit.ai/api/i/v1/... — look for 200 responses\nIf requests are missing entirely, the SDK isn't initializing — check for errors in the console"
      },
      {
        "title": "Events not linked to users",
        "body": "identify() or the user prop must be called/set after the auth flow resolves\nInclude both email and userId for reliable identity resolution\nClient-side identify links browsing history; server-side identify attributes server events"
      },
      {
        "title": "Server-side events missing",
        "body": "Always await outlit.flush() before the function returns, especially in serverless environments\nVerify OUTLIT_KEY env var is set in the server environment"
      },
      {
        "title": "Race condition with async auth",
        "body": "Auth providers like Clerk and Auth0 load asynchronously. If user.activate() or identify() is called before the auth provider resolves, events get silently dropped. Ensure auth state is fully loaded before calling identity or stage methods."
      },
      {
        "title": "Key Principles",
        "body": "Minimal changes — touch as few files as possible, add alongside existing code\nDetect first, ask second — auto-resolve what you can, only prompt for genuine decisions\nRecommendations have reasoning — when presenting a choice, lead with the recommendation and explain why\nClient-side identify is critical — this links anonymous browsing to a real user\nFlush in serverless — always await outlit.flush() before function exits\nsnake_case events — subscription_created not SubscriptionCreated\nBoth IDs — always provide both email and userId for identity resolution"
      },
      {
        "title": "Installation",
        "body": "To add this skill to your Claude Code environment:\n\nnpx add-skill outlitai/outlit-agent-skills\n# or\nbunx add-skill outlitai/outlit-agent-skills"
      }
    ],
    "body": "Outlit SDK Integration\n\nDecision-tree-driven guide for integrating Outlit customer journey tracking. Detects what it can from the codebase, asks only what it must, and links to official docs for implementation details.\n\nBranching Check\n\nBefore anything else, check if Outlit is already installed:\n\nLook for @outlit/browser, @outlit/node, or outlit (Rust crate) in package.json or Cargo.toml\nIf not installed -> go to Phase 1: Quick Connect\nIf already installed -> go to Already Installed\nAlready Installed\n\nAsk the user what they need help with:\n\nAdd event tracking -> Run detection, then go to Decision 7: Event Tracking. Fetch the relevant framework doc from the Doc URL Map for implementation patterns.\nAdd/change auth integration -> Run detection, then go to Decision 3: Auth & Identity. Fetch the framework doc and identity resolution doc.\nAdd consent management -> Go to Decision 2: Consent Stance. Fetch the framework doc's consent section.\nAdd server-side tracking -> Go to Decision 1: App Type & SDK for the server package, then fetch the Node.js or Rust doc.\nAdd billing/Stripe integration -> Go to Decision 6: Billing Integration. Fetch the customer journey doc.\nAdd activation tracking -> Go to Decision 5: Activation Event. Fetch the customer journey doc.\nMigrate from other analytics -> Run detection, then go to Decision 4: Existing Analytics.\nDebug/troubleshoot -> Go to Troubleshooting.\nPhase 1: Quick Connect\n\nGoal: get events flowing in ~2 minutes so the user sees \"Connected\" on their Outlit onboarding screen. Zero user decisions required.\n\nStep 1: Detect Framework & Package Manager\n\nUse glob/grep to check:\n\nFramework: Check package.json dependencies for next, vue, nuxt, react, svelte, @sveltejs/kit, @angular/core, astro, express, fastify. Check for Cargo.toml with tauri or outlit.\nPackage manager: Check for bun.lockb (bun), pnpm-lock.yaml (pnpm), yarn.lock (yarn), package-lock.json (npm). Use the first match found.\nStep 2: Install SDK\n\nBased on detected framework:\n\nBrowser app (React, Next.js, Vue, Nuxt, Svelte, Angular, Astro) -> @outlit/browser\nServer app (Express, Fastify, Node.js) -> @outlit/node\nTauri -> outlit Rust crate via cargo add outlit\nElectron -> @outlit/browser\n\nInstall using the detected package manager.\n\nStep 3: Add Public Key\n\nAsk the user for their Outlit public key. They get it from Outlit dashboard -> Settings -> Website Tracking or from the onboarding screen.\n\nAdd to environment variables with the correct framework prefix:\n\nFramework\tEnv var\nNext.js\tNEXT_PUBLIC_OUTLIT_KEY\nVite (Vue, Svelte, React+Vite)\tVITE_OUTLIT_KEY\nCreate React App\tREACT_APP_OUTLIT_KEY\nNuxt\tNUXT_PUBLIC_OUTLIT_KEY\nAngular\tAdd to environment.ts\nAstro\tPUBLIC_OUTLIT_KEY\nServer apps\tOUTLIT_KEY\nStep 4: Minimal Setup\n\nFetch the framework-specific doc from the Doc URL Map and implement only the minimal setup — provider/init with just the publicKey, no auth, no consent, no custom events.\n\nFor React-based frameworks this means wrapping the app with OutlitProvider. For Vue it means installing the OutlitPlugin. For server apps it means creating an Outlit instance.\n\nStep 5: Verify Connection\n\nTell the user to:\n\nRun their dev server\nOpen the app in a browser\nCheck the Outlit onboarding screen for the \"Connected\" badge\nOr check DevTools -> Network for requests to app.outlit.ai/api/i/v1/... returning 200\n\nOnce connected, ask: \"Events are flowing. Ready to set up the full integration?\"\n\nIf yes -> continue to Phase 2. If no -> they can come back later (the skill will detect the existing install).\n\nPhase 2: Full Integration\n\nRun the full detection first, then walk through each decision.\n\nFull Detection\n\nUse grep/glob to detect all of the following before starting the decision tree:\n\nSignal\tHow to detect\nAuth provider\tDeps: @clerk/nextjs, @clerk/clerk-react, next-auth, @auth/core, @supabase/auth-helpers-nextjs, @supabase/ssr, @auth0/auth0-react, @auth0/nextjs-auth0, firebase, @firebase/auth\nBilling provider\tDeps: stripe, @stripe/stripe-js, @paddle/paddle-js, chargebee\nExisting analytics\tDeps: posthog-js, @posthog/node, @amplitude/analytics-browser, @amplitude/analytics-node, mixpanel-browser, @segment/analytics-next, @segment/analytics-node\nAnalytics abstraction\tGrep for files named analytics.ts, analytics.js, tracking.ts, tracking.js in lib/, utils/, helpers/, services/ that import 2+ analytics libraries\nEU/consent signals\tDeps: cookiebot, @onetrust/*, cookie-consent, or grep for existing consent/cookie banner components\nApp type\tDeps: @tauri-apps/api, electron, react-native\nActivation patterns\tGrep for onboarding routes/components, \"first\" resource creation handlers, invite flows\n\nPresent a summary of what was detected to the user before proceeding.\n\nDecision 1: App Type & SDK Package\n\nAuto-resolved from Phase 1 detection. If hybrid (e.g., Next.js with API routes that need server tracking), install both @outlit/browser and @outlit/node.\n\nElectron -> @outlit/browser\nTauri -> outlit Rust crate\nReact Native -> @outlit/browser (uses fingerprint instead of cookies)\nDecision 2: Consent Stance\nDetection\tRecommendation\nExisting CMP/cookie banner library\tautoTrack: false, integrate with their existing CMP's consent callback to call enableTracking()\nEU signals but no CMP\tautoTrack: false, mention they need a consent solution but don't build one unless asked\nNo EU signals\tautoTrack: true — simpler, uses cookies immediately\n\nAlways explain the tradeoff: autoTrack: true starts tracking with cookies immediately. autoTrack: false waits until enableTracking() is called after user consent.\n\nFetch the relevant framework doc for consent implementation patterns.\n\nDecision 3: Auth & Identity\nDetection\tRecommendation\nReact/Vue with OutlitProvider/OutlitPlugin\tPass user prop with { email, userId } after auth resolves. No manual identify() needed.\nVanilla JS / script tag\tCall outlit.identify({ email, userId }) client-side right after auth completes\nServer-only (Node/Rust)\tCall outlit.identify() server-side for event attribution\n\nCritical: Client-side identify() (or the user prop) links the anonymous cookie/visitorId to a real person. This must happen after the auth flow completes. Server-side identify() is for attributing server events to a known user, but doesn't link browsing history.\n\nIf an auth provider was detected, fetch the framework doc and the identity resolution doc for the specific auth provider pattern.\n\nDecision 4: Existing Analytics Strategy\nDetection\tRecommendation\nExisting analytics abstraction (e.g., lib/analytics.ts wrapping PostHog + Amplitude)\tAdd Outlit as another provider inside the existing abstraction\nScattered direct calls (e.g., posthog.capture() in 15 files)\tTell the user: \"I found [N] direct [PostHog/Amplitude] calls across [N] files. Want me to create an analytics wrapper that calls both, or add Outlit calls alongside the existing ones?\"\nNo existing analytics\tAdd Outlit directly, no wrapper needed\n\nThe goal is minimal code changes. Don't reorganize their project.\n\nDecision 5: Activation Event\n\nThe activation event marks when a user first gets real value from the product. This is NOT just completing onboarding.\n\nScan the codebase for value-moment patterns:\nFirst resource/project/item created\nFirst core feature used (e.g., first message sent, first report generated)\nFirst invite to a teammate\nFirst successful integration/connection\nIf a clear value moment is found -> suggest it: \"It looks like creating their first [X] could be your activation event — is that where users first get value?\"\nIf only an onboarding flow is found -> mention it as a fallback: \"I see an onboarding flow, but activation usually maps to when users get real value, not just completing setup. What action means a user has truly gotten value from your product?\"\nIf nothing obvious -> ask: \"What action means a user has gotten real value from your product? That's where user.activate() should go.\"\n\nFetch the customer journey doc for user.activate() implementation.\n\nDecision 6: Billing Integration\nDetection\tRecommendation\nStripe in dependencies\tRecommend the Stripe webhook integration — it automatically handles customer.paid(), customer.trialing(), customer.churned() based on Stripe events. Fetch the customer journey doc for webhook setup.\nOther billing provider (Paddle, Chargebee)\tGuide manual customer.paid() / customer.trialing() / customer.churned() calls in their existing webhook handlers\nNo billing provider detected\tSkip. Mention it's available when they add billing.\nDecision 7: Event Tracking\n\nPageviews are tracked automatically by default. For custom events:\n\nScan the codebase for existing analytics calls, user action handlers, form submissions, key button clicks\nSuggest a list of events based on what the codebase reveals (e.g., form_submitted, feature_used, item_created, search_performed)\nAsk the user to confirm, modify, or add to the list before implementing\nUse snake_case for all event names\n\nFetch the framework doc for the track() API pattern.\n\nDoc URL Map\n\nFetch these docs as needed for implementation details. Always prefer linking to docs over hardcoding patterns.\n\nTopic\tURL\nQuickstart\thttps://docs.outlit.ai/tracking/quickstart\nHow tracking works\thttps://docs.outlit.ai/tracking/how-it-works\nNPM package\thttps://docs.outlit.ai/tracking/browser/npm\nReact\thttps://docs.outlit.ai/tracking/browser/react\nNext.js\thttps://docs.outlit.ai/tracking/browser/nextjs\nVue 3\thttps://docs.outlit.ai/tracking/browser/vue\nNuxt\thttps://docs.outlit.ai/tracking/browser/nuxt\nSvelteKit\thttps://docs.outlit.ai/tracking/browser/sveltekit\nAngular\thttps://docs.outlit.ai/tracking/browser/angular\nAstro\thttps://docs.outlit.ai/tracking/browser/astro\nScript tag\thttps://docs.outlit.ai/tracking/browser/script\nCalendar embeds\thttps://docs.outlit.ai/tracking/browser/calendar-embeds\nNode.js\thttps://docs.outlit.ai/tracking/server/nodejs\nRust / Tauri\thttps://docs.outlit.ai/tracking/server/rust\nIdentity resolution\thttps://docs.outlit.ai/concepts/identity-resolution\nAnonymous tracking\thttps://docs.outlit.ai/concepts/anonymous-tracking\nCustomer journey\thttps://docs.outlit.ai/concepts/customer-journey\nMCP integration\thttps://docs.outlit.ai/ai-integrations/mcp\nIngest API\thttps://docs.outlit.ai/api-reference/ingest\nAPI introduction\thttps://docs.outlit.ai/api-reference/introduction\nFull docs index\thttps://docs.outlit.ai/llms.txt\nTroubleshooting\nNo events in dashboard\nVerify the public key env var has the correct framework prefix (NEXT_PUBLIC_, VITE_, REACT_APP_, etc.)\nConfirm the provider/init wraps the entire app or runs at startup\nCheck autoTrack setting — if false, enableTracking() must be called after consent\nCheck DevTools -> Network for requests to app.outlit.ai/api/i/v1/... — look for 200 responses\nIf requests are missing entirely, the SDK isn't initializing — check for errors in the console\nEvents not linked to users\nidentify() or the user prop must be called/set after the auth flow resolves\nInclude both email and userId for reliable identity resolution\nClient-side identify links browsing history; server-side identify attributes server events\nServer-side events missing\nAlways await outlit.flush() before the function returns, especially in serverless environments\nVerify OUTLIT_KEY env var is set in the server environment\nRace condition with async auth\n\nAuth providers like Clerk and Auth0 load asynchronously. If user.activate() or identify() is called before the auth provider resolves, events get silently dropped. Ensure auth state is fully loaded before calling identity or stage methods.\n\nKey Principles\nMinimal changes — touch as few files as possible, add alongside existing code\nDetect first, ask second — auto-resolve what you can, only prompt for genuine decisions\nRecommendations have reasoning — when presenting a choice, lead with the recommendation and explain why\nClient-side identify is critical — this links anonymous browsing to a real user\nFlush in serverless — always await outlit.flush() before function exits\nsnake_case events — subscription_created not SubscriptionCreated\nBoth IDs — always provide both email and userId for identity resolution\nInstallation\n\nTo add this skill to your Claude Code environment:\n\nnpx add-skill outlitai/outlit-agent-skills\n# or\nbunx add-skill outlitai/outlit-agent-skills"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/leo-paz/outlit-sdk",
    "publisherUrl": "https://clawhub.ai/leo-paz/outlit-sdk",
    "owner": "leo-paz",
    "version": "1.0.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/outlit-sdk",
    "downloadUrl": "https://openagent3.xyz/downloads/outlit-sdk",
    "agentUrl": "https://openagent3.xyz/skills/outlit-sdk/agent",
    "manifestUrl": "https://openagent3.xyz/skills/outlit-sdk/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/outlit-sdk/agent.md"
  }
}