Update to Accoil Product Tracking

{
  "canonical_app_id": null,
  "connector_id": null,
  "created_at": "2026-10-08T23:24:13.005824Z",
  "discoverability": "LISTED",
  "id": "plugins_6ac734edeb8c8191b5cfaae829aea29d",
  "is_template": false,
  "is_template_instance": false,
  "is_v2_template": false,
  "name": "product-tracking",
  "release": {
    "app_ids": [],
    "app_manifest": null,
    "app_templates": [],
    "description": "Skills that make SaaS products data-ready for product analytics: model the product, audit existing tracking, design a tracking plan, generate an SDK-specific implementation guide, implement typed tracking code, and keep the plan current as features ship.",
    "display_name": "Accoil Product Tracking",
    "id": "pluginrel_7d1a60ff6af88191894aa163993c4604",
    "interface": {
      "brand_color": "#000000",
      "capabilities": [
        "Scan a codebase for analytics tracking",
        "Design a tracking plan",
        "Generate analytics instrumentation code"
      ],
      "category": "Developer Tools",
      "composer_icon_dark_url": null,
      "composer_icon_url": "https://files.openai.com/content?id=file_00000000afd8820ba930c9e7dfb486b4",
      "default_prompt": "Audit the analytics tracking in this codebase and save a current-state inventory.",
      "default_prompts": [
        "Audit the analytics tracking in this codebase and save a current-state inventory.",
        "Design a tracking plan for this product with users, accounts, and core events.",
        "Generate typed tracking code from our tracking plan for our analytics SDK."
      ],
      "developer_name": "Accoil",
      "logo_url": "https://files.openai.com/content?id=file_0000000017c0820b976e70aedb421f1e",
      "logo_url_dark": null,
      "long_description": "Accoil Product Tracking is a set of seven skills for engineers and product teams who need reliable product analytics in a B2B SaaS codebase.\n\nWhat it does:\n- Model the product: scan the codebase and ask a few questions to describe users, accounts, entities, and how value flows (.telemetry/product.md).\n- Audit current tracking: inventory existing analytics SDK calls, identity handling, and event naming (.telemetry/current-state.yaml).\n- Design a tracking plan: propose a minimal, consistently named set of events, properties, and group hierarchy, plus a delta from the current state (.telemetry/tracking-plan.yaml, .telemetry/delta.md).\n- Generate an implementation guide for one of 25 destinations, such as Segment, Amplitude, Mixpanel, PostHog, RudderStack, Google Analytics, Sentry, LaunchDarkly, or a generic HTTP API (.telemetry/instrument.md).\n- Implement tracking: generate typed wrapper functions and identity management code in a tracking/ directory.\n- Instrument new features: update the plan, delta, and changelog when a feature ships, changes, or is removed.\n- Write a business case for investing in product telemetry.\n\nLimitations: the lifecycle skills read and write files in the user's repository, so this plugin is available in Codex only. The skills generate plans and code only; they do not send any data to Accoil or to analytics vendors, do not create analytics accounts, and do not define KPIs or build dashboards. Review generated code before merging.",
      "plugin_category_id": "developer tools",
      "privacy_policy_url": "https://www.accoil.com/privacy",
      "screenshot_urls": [],
      "short_description": "Plan and instrument analytics",
      "terms_of_service_url": "https://www.accoil.com/terms",
      "website_url": "https://www.accoil.com/product-tracking"
    },
    "keywords": [
      "product-analytics",
      "product-tracking",
      "tracking-plan",
      "event-tracking",
      "instrumentation",
      "b2b-saas",
      "segment",
      "amplitude",
      "mixpanel",
      "posthog"
    ],
    "mcp_servers": [],
    "onboarding_skill_name": "product-tracking-model-product",
    "requires_local_executor": false,
    "skills": [
      {
        "description": "Reverse-engineer the current state of analytics tracking from a codebase. Scans for SDK calls, identity management, and instrumentation patterns to produce a factual inventory — not recommendations. Outputs .telemetry/current-state.yaml and a timestamped audit report. Use when the user wants to know what's currently tracked, audit existing analytics, capture tracking reality before designing a new plan, 'what analytics do we have,' 'what events are tracked,' 'scan for tracking,' or 'tracking inventory.'\n",
        "interface": {
          "brand_color": "#000000",
          "default_prompt": "Audit the analytics tracking in this codebase.",
          "display_name": "Audit current tracking",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "radar",
          "short_description": "Inventory existing analytics calls"
        },
        "name": "product-tracking-audit-current-tracking",
        "plugin_release_skill_id": "pluginrsk_6ac82373ec408191b17930e6841614c6"
      },
      {
        "description": "Write a business case for adding product telemetry and analytics to a product. Produces a concise, stakeholder-ready document explaining what telemetry enables, what you're currently blind to, what's involved in implementation, and the business value. Sits outside the main telemetry lifecycle — use before committing to the technical work. Use when the user asks to 'write a business case,' 'justify analytics,' 'make the case for tracking,' 'telemetry brief,' 'why add analytics,' 'convince leadership about tracking,' or 'analytics ROI.'\n",
        "interface": {
          "brand_color": "#000000",
          "default_prompt": "Write a business case for adding product analytics.",
          "display_name": "Business case",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "chart",
          "short_description": "Make the case for product telemetry"
        },
        "name": "product-tracking-business-case",
        "plugin_release_skill_id": "pluginrsk_6ac823755f908191abd55d0953363562"
      },
      {
        "description": "Design an opinionated target tracking plan and produce an explicit delta from current state to target. Combines the product model, current-state audit, and telemetry best practices to decide what events, properties, entities, and group hierarchies should exist. Outputs .telemetry/tracking-plan.yaml and .telemetry/delta.md. Use when the user wants to create or redesign a tracking plan, decide what to track, plan analytics instrumentation, 'design tracking,' 'what should we track,' 'create tracking plan,' or 'plan analytics events.'\n",
        "interface": {
          "brand_color": "#000000",
          "default_prompt": "Design a tracking plan for this product.",
          "display_name": "Design tracking plan",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "chart",
          "short_description": "Plan events, properties and groups"
        },
        "name": "product-tracking-design-tracking-plan",
        "plugin_release_skill_id": "pluginrsk_6ac8237566648191823de0f3e3f2b54f"
      },
      {
        "description": "Translate a tracking plan into an SDK-specific instrumentation guide. Shows how to make identify, group, and track calls using the target analytics SDK with real template code, architecture guidance, and constraint documentation. Outputs .telemetry/instrument.md. Covers 25 analytics destinations across product analytics, CDPs, product adoption, web analytics, error monitoring, feature flags, and session tools. Use when the user has a tracking plan and needs to know how to implement it with a specific SDK like Segment, Amplitude, Mixpanel, PostHog, Accoil, Google Analytics, Sentry, LaunchDarkly, or via generic HTTP POST. Also use when user asks 'create instrumentation guide,' 'how to implement tracking,' 'SDK guide,' or 'generate implementation guide.'\n",
        "interface": {
          "brand_color": "#000000",
          "default_prompt": "Generate an implementation guide for our analytics SDK.",
          "display_name": "Implementation guide",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "SDK-specific instrumentation guide"
        },
        "name": "product-tracking-generate-implementation-guide",
        "plugin_release_skill_id": "pluginrsk_6ac823764f348191833c4ec9ce73ee89"
      },
      {
        "description": "Generate real instrumentation code from the tracking plan and instrumentation guide. Produces typed SDK wrapper functions, identity management, and integration guidance. Outputs files in a tracking/ directory. Use when the user wants to generate or regenerate tracking code, implement the delta plan, turn the instrumentation guide into working code, 'implement tracking,' 'generate code,' 'create tracking module,' or 'build analytics SDK wrapper.'\n",
        "interface": {
          "brand_color": "#000000",
          "default_prompt": "Generate typed tracking code from our tracking plan.",
          "display_name": "Implement tracking",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Generate typed tracking code"
        },
        "name": "product-tracking-implement-tracking",
        "plugin_release_skill_id": "pluginrsk_6ac82375649081918ccbf6e316de4fe6"
      },
      {
        "description": "Update the tracking plan when a feature ships, changes, or is removed. Assesses whether new events are needed, extends existing events with properties where possible, and produces a versioned mini-delta with changelog entry. Updates .telemetry/tracking-plan.yaml, delta.md, and changelog.md. Use when the user ships a new feature, modifies existing functionality, wants to keep tracking coherent as the product evolves, 'feature shipped,' 'new feature tracking,' 'update tracking for [feature],' 'what tracking does this feature need,' or 'instrument new feature.'\n",
        "interface": {
          "brand_color": "#000000",
          "default_prompt": "Update the tracking plan for the feature I just shipped.",
          "display_name": "Instrument new feature",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "chart",
          "short_description": "Update tracking for a shipped feature"
        },
        "name": "product-tracking-instrument-new-feature",
        "plugin_release_skill_id": "pluginrsk_6ac8237511ac8191af9bbb884c41d550"
      },
      {
        "description": "Build a structured product model by scanning the codebase and talking to the user. Produces .telemetry/product.md — a description of what the product does, who uses it, how value flows, and what entities exist. Use when starting telemetry work on a new codebase, when the user asks to 'model this product,' 'understand this product,' 'what does this product do,' 'map the product,' 'product model,' or when no .telemetry/product.md exists yet. This is the entry point for the telemetry lifecycle.\n",
        "interface": {
          "brand_color": "#000000",
          "default_prompt": "Model this product for analytics: users, accounts, entities and value flow.",
          "display_name": "Model product",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "hierarchy",
          "short_description": "Map users, accounts and value flow"
        },
        "name": "product-tracking-model-product",
        "plugin_release_skill_id": "pluginrsk_6ac82373edfc81919978c84c8bc9ce88"
      }
    ],
    "version": "1.2.3"
  },
  "scope": "GLOBAL",
  "share_url": "https://chatgpt.com/plugins/plugins_6ac734edeb8c8191b5cfaae829aea29d?open_in_app",
  "status": "ENABLED"
}