ndb2-api

Connect mission-control to the NDB2 HTTP API with V2 and V1 endpoints.

5|2|Updated Nov 16, 2020
One-click install
npx skills add https://github.com/Off-Nominal/mission-control --skill ndb2-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ndb2-api
Source: https://github.com/Off-Nominal/mission-control/tree/main/.cursor/skills/ndb2-api
Command: npx skills add https://github.com/Off-Nominal/mission-control --skill ndb2-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides engineers on integrating mission-control with the Off-Nominal NDB2 HTTP API and webhooks, covering V2-first paths alongside V1 legacy routes, a shared client, error shapes, and webhook routing. It also explains how to migrate existing calls and add or modify predictions, bets, votes, and scores.

Core Features & Use Cases

  • Provides a clear map of V2 endpoints (seasons, predictions, webhooks) and how to use the shared client.
  • Documents V1 to V2 migration patterns, including path changes, response shapes, and error handling rules.
  • Describes how to extend or adapt the integration for new NDB2 calls, webhooks, and related workflows in mission-control.

Quick Start

Configure mcconfig.ndb2.baseUrl and mcconfig.ndb2.clientId, then instantiate the Ndb2Client and call addPrediction to create a new prediction.

Frequently Asked Questions about ndb2-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate with the NDB2 HTTP API and webhooks?

To integrate with the NDB2 HTTP API and webhooks, configure mcconfig.ndb2.baseUrl and clientId, then instantiate the shared Ndb2Client to handle predictions, bets, votes, scores, and webhook routing.

What is the best way to migrate existing API calls from V1 to V2?

The best way to migrate V1 API calls to V2 is by following the documented migration patterns for path changes, response shapes, and error handling while maintaining V1 legacy endpoints for backward compatibility.

Does the NDB2 integration support legacy V1 endpoints alongside V2?

Yes, the NDB2 integration specifies V2 as the preferred path while explicitly maintaining V1 legacy endpoints to ensure migration compatibility across predictions, bets, votes, and scores.

How do I add a new prediction using the NDB2 shared client?

To add a new prediction using the NDB2 shared client, instantiate the Ndb2Client after configuring the base URL and clientId, then call the addPrediction method to submit the prediction to the V2 endpoints.

What NDB2 webhook routing and error shapes are defined for developers?

The NDB2 integration defines standardized webhook routing and shared error shapes for developers to use when adding or modifying NDB2 calls, ensuring consistent error handling across mission-control workflows.

Can I extend the NDB2 API integration for new calls and workflows?

Yes, you can extend the NDB2 API integration for new calls and workflows by using the shared client and documented webhook routing patterns to adapt predictions, bets, votes, and scores within mission-control.