add-integration

Scaffold metadata, OAuth config, and provider implementations for Seer integrations.

5|1|Updated Oct 14, 2025
One-click install
npx skills add https://github.com/seer-engg/seer --skill add-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-integration
Source: https://github.com/seer-engg/seer/tree/main/.claude/skills/add-integration
Command: npx skills add https://github.com/seer-engg/seer --skill add-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and standardizes the process of adding new external integrations to Seer, ensuring consistent metadata, provider scaffolding, and tooling support.

Core Features & Use Cases

  • Metadata scaffolding and configuration for new integrations (OAuth-based and API-key-based)
  • Provider implementation templates and lifecycle hooks to manage authorization, tokens, and resource access
  • Optional tooling and resource integration to automate testing, validation, and deployment
  • Use Case: Add Slack or GitHub integration with minimal boilerplate and consistent UI metadata

Quick Start

Follow the guide to scaffold a new integration by adding INTEGRATION_CONFIG metadata, a provider class, and optional tooling scaffolds.

Frequently Asked Questions about add-integration

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

FAQPage Schema
How do I add a new OAuth-based integration for a service like GitHub?

To add an OAuth-based integration, you scaffold the integration metadata, implement a corresponding IntegrationProvider, and update the OAuth configuration and provider registry to ensure a consistent authorization lifecycle.

Can I use API-key-based authentication for custom provider integrations?

Yes, API-key-based authentication is fully supported for custom providers. You scaffold the integration metadata and implement an IntegrationProvider to manage token access and resource tools without requiring OAuth flows.

What is the standard way to scaffold integration metadata for external services?

Scaffolding integration metadata involves defining INTEGRATION_CONFIG metadata and implementing an IntegrationProvider class to manage authorization, tokens, and resource access consistently across external services.

Do I need to implement resource tools when adding a new external integration?

Resource tools are optional when adding a new external integration. You scaffold them to automate testing, validation, and deployment, but the core requirements are integration metadata and an IntegrationProvider implementation.

Does this integration scaffolding work for both Slack and Google providers?

Yes, integration scaffolding applies to scenarios involving both OAuth-based and API-key-based services like Google, GitHub, and Slack, ensuring consistent UI metadata and provider lifecycle management across all supported providers.