Update to Fullstory

Changed files

.codex-plugin/plugin.json →

skills/idea-generation/SKILL.md →

.codex-plugin/plugin.json

--- before
+++ after
@@ -3,7 +3,7 @@
   "author": {
     "name": "Fullstory"
   },
-  "description": "Ask about your product analytics, and get answers you can verify.\n\nFullstory MCP connects Codex and ChatGPT to your product's behavioral data. Ask how many users adopted a feature, where checkout is leaking, or whether yesterday's release broke something, and Codex and ChatGPT builds the segment, computes the metric, and explains the result with a link back to Fullstory.\n\nAnalytics connectors can give you numbers. Fullstory shows you what happened. Metrics unpack into real session replay, so \"conversion dropped 12%\" becomes \"the coupon field errors for logged-out users.\"\n\nAnd because Fullstory autocaptures clicks, page views, errors, and frustration signals, many questions need no instrumentation at all. Ask about rage clicks on pricing or errors in checkout without shipping a single event.\n\nWhat Codex and ChatGPT can do:\n(1) Build and save segments and metrics.\nDescribe the users or behavior you care about in your own words; Codex and ChatGPT create segments or metrics in Fullstory where your whole team can reuse it.\n\n(2) Compute on demand.\n Counts, rates, trends, and breakdowns by device, browser, geography, or user property, over any time window.\n\n(3) Speak your product's language. \nCodex and ChatGPT discover your pages, named elements, and defined events, so questions map to your real product vocabulary instead of guessed selectors.\n\n(4) Analyze conversion.\nRead your saved funnels and measure where users drop and why.\n\n(5) Back every number with sessions.\nRetrieve the sessions and events behind any metric, including frustration signals like rage clicks and dead clicks.\n\n(6) Read sessions at scale.\nAsk Codex and ChatGPT to review dozens of sessions behind a drop-off or an alert and report the patterns, including failures that never reached your error tracker.\n\nTeams use it to let PMs, support, and engineers self-serve answers that used to queue behind an analyst, and to settle \"why did this number move?\" with evidence instead of theories.",
+  "description": "Ask about your product analytics, and get answers you can verify.\n\nFullstory MCP connects Codex and ChatGPT to your product's behavioral data. Ask how many users adopted a feature, where checkout is leaking, or whether yesterday's release broke something, and Codex and ChatGPT build the segment, computes the metric, and explains the result with a link back to Fullstory.\n\nAnalytics connectors can give you numbers. Fullstory shows you what happened. Metrics unpack into real session replay, so \"conversion dropped 12%\" becomes \"the coupon field errors for logged-out users.\"\n\nAnd because Fullstory autocaptures clicks, page views, errors, and frustration signals, many questions need no instrumentation at all. Ask about rage clicks on pricing or errors in checkout without shipping a single event.\n\nWhat Codex and ChatGPT can do:\n(1) Build and save segments and metrics.\nDescribe the users or behavior you care about in your own words; Codex and ChatGPT create segments or metrics in Fullstory where your whole team can reuse it.\n\n(2) Compute on demand.\n Counts, rates, trends, and breakdowns by device, browser, geography, or user property, over any time window.\n\n(3) Speak your product's language. \nCodex and ChatGPT discover your pages, named elements, and defined events, so questions map to your real product vocabulary instead of guessed selectors.\n\n(4) Analyze conversion.\nRead your saved funnels and measure where users drop and why.\n\n(5) Back every number with sessions.\nRetrieve the sessions and events behind any metric, including frustration signals like rage clicks and dead clicks.\n\n(6) Read sessions at scale.\nAsk Codex and ChatGPT to review dozens of sessions behind a drop-off or an alert and report the patterns, including failures that never reached your error tracker.\n\nTeams use it to let PMs, support, and engineers self-serve answers that used to queue behind an analyst, and to settle \"why did this number move?\" with evidence instead of theories.",
   "interface": {
     "capabilities": [],
     "category": "Data & Analytics",
@@ -14,7 +14,7 @@
     ],
     "developerName": "Fullstory",
     "displayName": "Fullstory",
-    "longDescription": "Ask about your product analytics, and get answers you can verify.\n\nFullstory MCP connects Codex and ChatGPT to your product's behavioral data. Ask how many users adopted a feature, where checkout is leaking, or whether yesterday's release broke something, and Codex and ChatGPT builds the segment, computes the metric, and explains the result with a link back to Fullstory.\n\nAnalytics connectors can give you numbers. Fullstory shows you what happened. Metrics unpack into real session replay, so \"conversion dropped 12%\" becomes \"the coupon field errors for logged-out users.\"\n\nAnd because Fullstory autocaptures clicks, page views, errors, and frustration signals, many questions need no instrumentation at all. Ask about rage clicks on pricing or errors in checkout without shipping a single event.\n\nWhat Codex and ChatGPT can do:\n(1) Build and save segments and metrics.\nDescribe the users or behavior you care about in your own words; Codex and ChatGPT create segments or metrics in Fullstory where your whole team can reuse it.\n\n(2) Compute on demand.\n Counts, rates, trends, and breakdowns by device, browser, geography, or user property, over any time window.\n\n(3) Speak your product's language. \nCodex and ChatGPT discover your pages, named elements, and defined events, so questions map to your real product vocabulary instead of guessed selectors.\n\n(4) Analyze conversion.\nRead your saved funnels and measure where users drop and why.\n\n(5) Back every number with sessions.\nRetrieve the sessions and events behind any metric, including frustration signals like rage clicks and dead clicks.\n\n(6) Read sessions at scale.\nAsk Codex and ChatGPT to review dozens of sessions behind a drop-off or an alert and report the patterns, including failures that never reached your error tracker.\n\nTeams use it to let PMs, support, and engineers self-serve answers that used to queue behind an analyst, and to settle \"why did this number move?\" with evidence instead of theories.",
+    "longDescription": "Ask about your product analytics, and get answers you can verify.\n\nFullstory MCP connects Codex and ChatGPT to your product's behavioral data. Ask how many users adopted a feature, where checkout is leaking, or whether yesterday's release broke something, and Codex and ChatGPT build the segment, computes the metric, and explains the result with a link back to Fullstory.\n\nAnalytics connectors can give you numbers. Fullstory shows you what happened. Metrics unpack into real session replay, so \"conversion dropped 12%\" becomes \"the coupon field errors for logged-out users.\"\n\nAnd because Fullstory autocaptures clicks, page views, errors, and frustration signals, many questions need no instrumentation at all. Ask about rage clicks on pricing or errors in checkout without shipping a single event.\n\nWhat Codex and ChatGPT can do:\n(1) Build and save segments and metrics.\nDescribe the users or behavior you care about in your own words; Codex and ChatGPT create segments or metrics in Fullstory where your whole team can reuse it.\n\n(2) Compute on demand.\n Counts, rates, trends, and breakdowns by device, browser, geography, or user property, over any time window.\n\n(3) Speak your product's language. \nCodex and ChatGPT discover your pages, named elements, and defined events, so questions map to your real product vocabulary instead of guessed selectors.\n\n(4) Analyze conversion.\nRead your saved funnels and measure where users drop and why.\n\n(5) Back every number with sessions.\nRetrieve the sessions and events behind any metric, including frustration signals like rage clicks and dead clicks.\n\n(6) Read sessions at scale.\nAsk Codex and ChatGPT to review dozens of sessions behind a drop-off or an alert and report the patterns, including failures that never reached your error tracker.\n\nTeams use it to let PMs, support, and engineers self-serve answers that used to queue behind an analyst, and to settle \"why did this number move?\" with evidence instead of theories.",
     "privacyPolicyURL": "https://www.fullstory.com/legal/privacy-policy/",
     "shortDescription": "Product analytics for agents.",
     "supportURL": "https://www.fullstory.com/contact/",
@@ -23,5 +23,5 @@
   },
   "name": "app-6a9a1ebb11fc81919ef2aa7231b9b068",
   "skills": "./skills",
-  "version": "2.0.0"
+  "version": "3.0.0"
 }
\ No newline at end of file