plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "endurance-analytics",
  "version": "2.6.0",
  "description": "Trail and ultra race planning from Endurance Analytics: plan the season, build and save a race-day plan (predicted arrival at each aid station, cut-off margins and fuel per segment, with your own gels and drinks), break the course down (climbs, descents, technicality, poles, quad damage, weather at the course), then review results, checkpoint splits and how the field went. Plus your stored races, GPX course upload, feedback and catalog requests.",
  "author": {
    "name": "Endurance Analytics",
    "url": "https://endurance-analytics.com"
  },
  "homepage": "https://endurance-analytics.com/en/connect",
  "repository": "https://github.com/IgorAleksandroff/endurance-analytics-plugin",
  "license": "MIT",
  "keywords": [
    "trail-running",
    "ultra",
    "race",
    "gpx",
    "terrain",
    "weather",
    "analytics",
    "race-plan",
    "nutrition"
  ],
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "Endurance Analytics",
        "shortDescription": "Trail race planning & analysis",
        "longDescription": "Endurance Analytics plans trail and ultra races from start to finish: the season, the race day and the review afterwards.\n\nPlan the season: search the public catalog by name, country, month, terrain and open registration, compare races side by side, find races like one you loved, and keep your season plan (races of the year and a wishlist): add, change and remove races, check the calendar of your prioritised races; every change can be undone for 90 days.\n\nPlan the race day: the platform predicts your finish time from your performance index (or takes your target), gives the arrival time at every aid station and the margin to each cut-off, and lays out the fuel per segment: gels, food, water or drink and salt tabs, with other fuel mixes for the same carbs per hour. Save the plan to your account, or change a saved one: target time, technicality, carbs per hour, gel size, fluid, your own gel or drink, a sandwich at one station, or your own checkpoints for a race without aid stations. The plan opens on the race page, where you can fine-tune it.\n\nKnow the course: flat-equivalent distance, the steepness profile, the longest and steepest climbs and descents with where they fall, surface and technical sections matched against OpenStreetMap, where running poles pay off, how much quad damage the descents inflict and where, and the weather at the course itself: the climate record of the race date, the forecast when the race is close, and what the weather did in past editions. Practical questions (supporters, bib pickup, gear, poles) are answered from the race FAQ with the source, edition and date of every answer.\n\nReview the race: results, any athlete's race checkpoint by checkpoint, and how the field went: finish-time percentiles, drops and cut-off margins per checkpoint.\n\nBring your own course: upload a GPX (by link or file) as a race or a route and get the same terrain, descent and pole analysis; your stored races come with climb, descent and altitudes. Send the team feedback or ask for a missing race or course track.\n\nBuilt for trail and ultra runners choosing races, preparing for one, or learning from the last.\n\nLimitations: training data, endurance curves, heart-rate zones and readiness are not available through this integration. Deleting your stored races or race plans, account settings and payments happen on the website; the assistant gives you a link. Uploading a GPX course uses one of your race slots, and a new race plan one race-plan slot unless that race already has one. Course insights are computed for a reference runner, and the assistant reports only numbers the platform returns. An Endurance Analytics account is required for your own data.",
        "developerName": "Endurance Analytics",
        "category": "Data & Analytics",
        "websiteURL": "https://endurance-analytics.com",
        "supportURL": "https://endurance-analytics.com/en/contact",
        "privacyPolicyURL": "https://endurance-analytics.com/en/privacy",
        "termsOfServiceURL": "https://endurance-analytics.com/en/terms",
        "defaultPrompt": [
          "Plan my CCC: predicted time at each aid station, cut-off margins and what to eat and drink.",
          "Find trail races in Italy next summer that have a course track.",
          "Compare OCC, CCC and TDS 2026: which has the toughest descents and the tightest cut-offs?"
        ],
        "brandColor": "#0068B2",
        "brandColorDark": "#0086E6",
        "logo": "./assets/logo.png",
        "composerIcon": "./assets/logo.png"
      },
      "onboardingSkill": "./skills/getting-started/SKILL.md",
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "Find races in the catalog by event name.",
              "prompt": "Which races are part of HOKA UTMB Mont-Blanc 2026? Give the distance and elevation gain of each.",
              "tools_triggered": "search_races",
              "expected_behavior": "Lists the 2026 races of the event (UTMB about 174 km / 9700 m, CCC about 108 km / 6200 m, OCC about 60 km / 3500 m, plus TDS, MCC, YCC and ETC) with distance and gain exactly as the catalog returns them. No invented values; missing fields are reported as unknown."
            },
            {
              "description": "Explain course terrain and the descents that cost the most for a real race.",
              "prompt": "How hard is the OCC 2026 course? Where are the biggest climbs, and which descents will hurt my quads most?",
              "tools_triggered": "search_races, get_race_terrain_summary, get_race_quad_damage",
              "expected_behavior": "Describes the point-to-point course of about 59.5 km and 3400 m of climbing with its highest point near km 34, names the longest climb (about 4.8 km at about 15% ending near km 17) and the steepest sections with their kilometre positions, then reports the quad-damage level (moderate at the time of writing) and the critical descents in course order with their kilometres. States that the damage figures are for a typical runner, not a personal prediction."
            },
            {
              "description": "Upload a GPX course by link and analyse its terrain.",
              "prompt": "Save this GPX as my race (not a training route) named 'OCC recon' and tell me how hard it is: https://api.endurance-analytics.com/public/trail/races/utmb-occ/track.gpx?season=2026",
              "tools_triggered": "save_gpx_as_race",
              "expected_behavior": "Creates one race in the account and reports its terrain from the tool response: about 59.5 km with about 3400 m of climbing, flat-equivalent distance, and the longest and steepest climbs with their positions. Mentions that the upload used one race slot, that technicality was set to the default of 1 rather than measured, that surface data may still be pending, and that deleting the race is done on the website."
            },
            {
              "description": "Compare races side by side.",
              "prompt": "Compare OCC 2026, CCC 2026 and TDS 2026: distance, climb, technicality and the longest gap between aid stations.",
              "tools_triggered": "search_races, compare_races",
              "expected_behavior": "Finds the three 2026 races and shows one table with the catalog's values and each difference from the first race. Empty cells are reported as unknown with the reason the tool gives; no invented numbers and no verdict on which race is better for the athlete."
            },
            {
              "description": "Build a race-day plan for a target time and save it to the account: aid station times, cut-off margins and fuel.",
              "prompt": "Make me a race plan for the CCC 2026 for about 24 hours: when do I reach each aid station, how close am I to the cut-offs, and what should I eat and drink? Save it as 'CCC 24h'.",
              "tools_triggered": "search_races, get_race_plan, save_race_plan",
              "expected_behavior": "Lists the aid stations in course order with the arrival time at a 24-hour finish and the margin to each cut-off, exactly as the tool returns them, and the fuel per segment and in total (gels, water or drink, salt) with the hourly rhythm; says the margins come from the time model, not from how real finishers did. Then saves the plan named 'CCC 24h' with the same target and fuel settings, reports that it was saved (and that the race joined the wishlist), and gives the link to the plan on the race page, where it can be edited or deleted. No time, margin or gel count recomputed by the assistant."
            }
          ],
          "negative": [
            {
              "description": "Training and heart-rate data are not available through this integration. The assistant must not call tools to approximate them; it explains they are not available here and points the athlete to the Endurance Analytics website.",
              "prompt": "Show my Strava trainings from last week and my heart-rate zones."
            },
            {
              "description": "Deleting a race is website-only by design. The assistant must not attempt any write or destructive action; it may look the race up and gives the web link where the athlete can delete it.",
              "prompt": "Delete my race 'OCC recon' from Endurance Analytics."
            },
            {
              "description": "The request is unrelated to race analytics. The plugin should not be used and no Endurance Analytics tool should be called.",
              "prompt": "Order me a pizza to my flat in Annecy for 8 pm tonight."
            }
          ]
        },
        "demo_recording_url": "https://youtu.be/ThNrgYxxuB4",
        "commerce": false
      },
      "publication": {
        "countries": [],
        "release_notes": "New: save a race-day plan to your account or change a saved one from the chat: target time, technicality, carbs per hour, gel size, fluid, your own gel or drink, items at one station and your own checkpoints. Earlier: the race-day plan itself (arrival at each aid station, cut-off margins, fuel per segment), season plan changes with undo, feedback and catalog requests."
      },
      "apps": "./.app.json"
    }
  }
}