skills.rest
tower
towerOFFICIAL
Explore all skills by this author →
WebsiteGitHub

find-source

Identify optimal DLT data source connectors for a given API or provider.

19|Updated Apr 1, 2026
Search Tags:#validation#dlt#rest-api#data-pipeline#connectors#source-discovery
One-click install
npx skills add https://github.com/tower/agentic-data-engineering --skill find-source-tower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: find-source
Source: https://github.com/tower/agentic-data-engineering/tree/main/.claude/skills/find-source
Command: npx skills add https://github.com/tower/agentic-data-engineering --skill find-source-tower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locate and recommend the most suitable data-source connectors (DLT sources) for a given API or data provider, reducing guesswork and setup time.

Core Features & Use Cases

  • Guided source discovery: classifies user needs and maps them to verified connectors or suggests a custom integration path.
  • Source vetting and validation: searches verified sources, dlthub contexts, and performs web validation to ensure accuracy.
  • Clear options and next steps: presents tradeoffs and recommended actions to empower fast decisions.

Quick Start

Ask the user which API or data provider they want to integrate and begin the guided source-discovery workflow.

Frequently Asked Questions about find-source

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

FAQPage Schema
How do I find the right data source connector for a REST API?▼

To find a data source connector for a REST API, you can use a guided source-discovery workflow that classifies your needs and maps them to verified connectors or suggests a custom integration path. This process searches verified sources and dlthub contexts to ensure accuracy and reduce setup time.

What is the best way to validate if a dlt data pipeline connector exists for my provider?▼

The best way to validate if a dlt data pipeline connector exists is to perform source vetting against verified sources and dlthub contexts, supplemented by web validation. This ensures the recommended connector is accurate and viable before you commit to setup.

Can I use a verified dlt source instead of building a custom REST API integration?▼

Yes, you can use a verified dlt source instead of building a custom REST API integration if one exists for your provider. The discovery process compares your API against verified connectors and dlthub contexts to surface viable options and clear tradeoffs.

When do I need a custom REST API integration for my data pipeline?▼

You need a custom REST API integration for your data pipeline when no verified connector or dlthub context exists for your specific provider. The discovery workflow identifies this gap and proposes a custom integration path as the next step.

How do I compare data-source connectors and choose the right option?▼

To compare data-source connectors, the discovery workflow presents clear options, tradeoffs, and recommended actions based on your API. It evaluates whether a verified connector exists or if a custom REST integration is required, empowering you to choose fast.

Related Skills

Explore More Data & Analytics Skills→
Happy-Technologies-LLCHappy-Technologies-LLC
34

service-graph-diagnosis

Diagnose Service Graph Connector issues in ServiceNow CMDB workflows.

Official
Advanced
dlt-hubdlt-hub
53

new-endpoint

Add a REST API endpoint to an existing dlt pipeline configuration.

Official
Intermediate
dlt-hubdlt-hub
53

validate-data

Validate schemas and data integrity after dlt pipeline loads.

Official
Intermediate
dlt-hubdlt-hub
53

find-source

Identify dlt source connectors for APIs and data providers.

Official
Intermediate