integration-generator

Generate OAuth provider integration scaffolding for Dafthunk across backend and frontend.

114|24|Updated Feb 13, 2025
One-click install
npx skills add https://github.com/dafthunk-com/dafthunk --skill integration-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-generator
Source: https://github.com/dafthunk-com/dafthunk/tree/main/.claude/skills/integration-generator
Command: npx skills add https://github.com/dafthunk-com/dafthunk --skill integration-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end OAuth provider integration scaffolding for Dafthunk, enabling rapid creation of backend, frontend, and node support for new providers.

Core Features & Use Cases

  • Research provider APIs: Gather OAuth endpoints, scopes, and user info requirements from provider docs.
  • Create backend OAuth provider and types: Generate token/response types and provider class templates, plus registry wiring.
  • Configure frontend and registry: Add frontend provider config and update shared integration types for client apps.
  • Optionally create integration nodes: Scaffold workflow nodes for actions and events around the new provider.

Quick Start

Run the integration generator to scaffold a new OAuth provider across backend, frontend, and optional integration nodes.

Frequently Asked Questions about integration-generator

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

FAQPage Schema
How do I auto-generate OAuth provider integrations end-to-end?

You can auto-generate OAuth provider integrations by scaffolding backend types, provider classes, registries, frontend integration configs, and optional node templates across the entire stack.

What is included in end-to-end OAuth integration scaffolding?

End-to-end OAuth integration scaffolding includes backend token and response type definitions, provider class templates, provider registry wiring, frontend provider configuration, and optional integration node templates.

How do I scaffold a new OAuth provider across backend and frontend?

Scaffolding a new OAuth provider involves generating backend provider classes and types, updating the shared integration registry, and adding frontend provider configuration to connect client applications.

Do I need to manually configure OAuth scopes and endpoints when adding a new provider?

You need to research provider APIs for OAuth endpoints, scopes, and user info requirements from provider documentation before generating the automated backend and frontend configuration templates.

Can I generate workflow nodes for new OAuth integrations?

Yes, you can optionally scaffold workflow integration nodes for actions and events around the new OAuth provider during the end-to-end generation process.

What's the best way to add a new OAuth provider to an existing integration registry?

The best way to add a new OAuth provider is to auto-generate the provider class, update the backend registry wiring, and configure the frontend integration types simultaneously to maintain consistency.