add-swapper-integration

Add and validate a new swapper integration to the ShapeShift Revenue Dashboard.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/shapeshift/revenue-dashboard --skill add-swapper-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-swapper-integration
Source: https://github.com/shapeshift/revenue-dashboard/tree/main/.claude/skills/add-swapper-integration
Command: npx skills add https://github.com/shapeshift/revenue-dashboard --skill add-swapper-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides engineering teams through adding a new DEX/swapper integration to the ShapeShift Revenue Dashboard, ensuring a consistent, maintainable workflow from research to frontend wiring.

Core Features & Use Cases

  • Structured research: standardizes API investigation, affiliate identifiers, and data sources for a new swapper.
  • Implementation patterns: provides a repeatable getFees workflow, amount normalization to base units, and USD enrichment strategy.
  • Frontend integration: aligns backend data with the dashboard UI, labels, colors, and service registration for charts and tables.

Quick Start

Create a new backend integration scaffold under apps/revenue-api/src/affiliateRevenue/[swappername]/, implement the getFees function following the project’s patterns, register the integration in both backend provider lists and frontend service registries, and run the monorepo locally to validate end-to-end data flow.

Frequently Asked Questions about add-swapper-integration

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

FAQPage Schema
How do I add a new DEX swapper integration to a revenue dashboard?

Adding a new swapper integration requires scaffolding a backend directory, implementing the getFees flow, normalizing amounts to base units, enriching with USD pricing, and registering the service in both backend provider lists and frontend UI registries.

What is the getFees flow for swapper API integration?

The getFees flow is a standardized implementation pattern for fetching fee data from a swapper API. It enforces amount normalization to base units and applies a consistent USD enrichment strategy for revenue reporting across the dashboard.

How do I normalize crypto amounts to base units for API revenue tracking?

Amount normalization to base units converts varied API outputs into a consistent format for revenue tracking. The integration enforces this normalization within the getFees workflow before applying USD enrichment for dashboard reporting.

Do I need to update both backend and frontend registries when adding a swapper integration?

Yes, adding a swapper integration requires updating both backend provider lists and frontend service registries. This dual registration aligns backend data with dashboard UI components, including labels, colors, charts, and tables.

What API research is needed before implementing a new swapper integration?

API research for a new swapper involves investigating available endpoints, identifying affiliate identifiers, and confirming data sources. This structured research phase standardizes the workflow before implementing the getFees function and frontend wiring.