Seer
Official@seer-engg · United States of America
no-code, controllable AI workflows
Agent Skills by Seer
Showing 9 vetted skills indexed across 1 GitHub repositories.
seer-enggresource-browser
Document resource picker debugging across Google Drive, GitHub, Discord, and Supabase providers.
seer-enggworkflow-compiler
Document Seer's workflow compiler and runtime for developers implementing node types.
seer-enggintegration-metadata
Clarify how integration metadata configures the Seer frontend UI.
seer-enggintegration-providers
Explain the IntegrationProvider abstraction for OAuth provider integration in Seer.
seer-enggcredential-resolution
Resolves and validates runtime credentials for tool executions in Seer.
seer-enggworkflow-validation
Validate workflow specifications, expressions, and block configurations for correctness.
seer-enggadd-integration
Scaffold metadata, OAuth config, and provider implementations for Seer integrations.
seer-enggoauth-integration
Explain OAuth authentication flows and token management across provider integrations.
seer-enggtools-creation
Document Seer tool registration, credential resolution, and runtime execution patterns.
Frequently Asked Questions About Seer
FAQPage SchemaWhat specific tasks does Seer enable for developers?▼
Seer enables developers to build, validate, and manage integration providers. It facilitates the creation of custom node types, handles OAuth authentication flows, resolves runtime credentials, and ensures configuration correctness through a centralized compiler and validation system.
Which technical personas benefit from using Seer?▼
Seer is designed for backend and integration engineers responsible for connecting disparate services. It is ideal for developers building modular systems that require standardized authentication, credential management, and metadata-driven UI configurations across multiple external platforms.
What are the core prerequisites for implementing Seer integrations?▼
Implementation requires familiarity with OAuth authentication standards and the ability to define integration metadata. Developers must configure provider-specific credentials and adhere to the established runtime execution patterns for registering new services within the Seer environment.