How does it handle multiple installed providers?

It prioritizes the WAGGLE_PROVIDER environment variable; if unset, it prompts the user to select the preferred provider through a conflict resolution step.

Which data providers are supported?

The skill currently supports and detects the Notion, SQLite, and Turso providers for the Waggle ecosystem.

Can I invoke this skill manually?

No, this is an internal shared skill intended for background orchestration. It is triggered automatically to ensure your environment is configured correctly.

What environments does it recognize?

It detects three primary environments: Cowork (a Claude desktop feature), the standard Claude Desktop app, and the Terminal CLI.

What is the detecting-provider skill used for?

It is an internal utility that identifies your execution environment and connects Claude to your active Waggle data provider, such as Notion or SQLite.

Waggle Environment & Provider Detection

Name: Waggle Environment & Provider Detection
Author: kazukinagata

bykazukinagata

0•

Database Management

Automatically detects the execution environment and configures the active data provider for the Waggle ecosystem.

The detecting-provider skill serves as an essential internal orchestration layer for Waggle within Claude Code. It intelligently identifies the execution context—whether in Cowork, Claude Desktop, or a standard CLI—to determine which data source provider (Notion, SQLite, or Turso) is active. By validating MCP tool availability and loading environment-specific constants, it ensures that Claude has the correct database IDs and configuration settings to interact with your external data sources without manual setup overhead.

Key Features

01Automated conflict resolution for multiple installed plugins

02Pre-flight validation of MCP tools and environment variables

030 GitHub stars

04Automatic discovery of Notion, SQLite, and Turso providers

05Context-aware environment detection (Cowork, Desktop, and CLI)

06Dynamic loading of provider-specific database configurations

Use Cases

01Switching between different backend data providers seamlessly

02Initializing the Waggle data environment upon session startup

03Validating system requirements for database and MCP tool access

Key Features

01Automated conflict resolution for multiple installed plugins

02Pre-flight validation of MCP tools and environment variables

030 GitHub stars

04Automatic discovery of Notion, SQLite, and Turso providers

05Context-aware environment detection (Cowork, Desktop, and CLI)

06Dynamic loading of provider-specific database configurations

Use Cases

01Switching between different backend data providers seamlessly

02Initializing the Waggle data environment upon session startup

03Validating system requirements for database and MCP tool access