decile-hub-connector

What problem does it solve?

Lossless VC client workspaces previously required manual, error-prone configuration to connect to Decile Hub's per-tenant API, with no standardized guidance for handling its inconsistent pagination, authentication, and data mapping rules.

Core Features & Use Cases

• Standardized Per-Client Connection: Handles tenant-specific subdomain base URLs and raw API token authentication (no Bearer prefix) for each Decile Hub VC client workspace.
• Consistent API Interaction: Normalizes Decile's three distinct pagination patterns, supports upsert-by-natural-key write semantics, and handles custom data points and merge tags.
• Canonical Layer Mapping: Maps Decile people, organizations, and pipeline prospects to SurrealDB canonical tables with required client tagging for VC client data sync.
• Use Case: A VC firm using augment-it can use this skill to pull the latest pipeline prospects, sync deal memos, and update portfolio company data from Decile Hub without manually parsing the 12,000-line OpenAPI spec or handling edge cases like inconsistent error response shapes.

Quick Start

Use the decile-hub-connector skill to pull all active pipeline prospects for the humain-vc client from Decile Hub and sync them to the SurrealDB canonical persons and organizations tables.