skills.rest
kazukinagata
kazukinagataCOMMUNITY
Explore all skills by this author →
𝕏@KazukiN74451GitHub

detecting-provider

Detect the active Waggle provider and load its provider SKILL.md across environments.

3|Updated Mar 21, 2026
Search Tags:#automation#integration#config#environment#provider#detect#waggle
One-click install
npx skills add https://github.com/kazukinagata/waggle --skill detecting-provider
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: detecting-provider
Source: https://github.com/kazukinagata/waggle/tree/main/skills/detecting-provider
Command: npx skills add https://github.com/kazukinagata/waggle --skill detecting-provider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects the active Waggle provider and loads its provider SKILL.md, an internal shared skill used to prepare downstream configuration for execution across environments.

Core Features & Use Cases

  • Provider identification: determines which waggle provider is active (notion, sqlite, or turso) and resolves its location.
  • Environment-aware discovery: supports cowork, Claude Desktop, and CLI workflows to select and load the correct provider.
  • Configuration loading: reads the provider's SKILL.md to extract IDs, constants, and prepares headless configuration for subsequent skills.
  • Reusability: designed as an internal shared skill to be invoked by other provider-related workflows.

Quick Start

Run this skill to automatically detect the active provider and load its configuration.

Frequently Asked Questions about detecting-provider

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

FAQPage Schema
How do I detect the active Waggle provider and load its config?▼

To detect the active Waggle provider, this skill validates provider availability and loads its SKILL.md. It identifies whether notion, sqlite, or turso is active and populates headless_config for downstream tasks.

What is Waggle provider detection and when do I need it?▼

Waggle provider detection identifies which provider plugin is active and where its SKILL.md resides. You need it to prepare downstream configuration for execution across cowork, Claude Desktop, and CLI environments.

Does Waggle provider detection work across CLI and Claude Desktop environments?▼

Yes, Waggle provider detection operates across cowork, Claude Desktop, and CLI workflows. It follows a multi-step process to select and load the correct provider SKILL.md based on the active environment.

Which Waggle providers can be detected and loaded?▼

The detection process supports notion, sqlite, and turso Waggle providers. It resolves the active provider's location, reads its SKILL.md to extract IDs and constants, and prepares headless configuration for subsequent skills.

Can I use detected provider config for downstream automation tasks?▼

Yes, detected provider config is designed for downstream automation. After reading the provider SKILL.md, the skill populates headless_config with extracted IDs and constants for subsequent provider-related workflows.

Why does my Waggle provider config fail to load across environments?▼

Provider config may fail if the multi-step validation cannot locate the active provider's SKILL.md. Ensure the correct provider plugin is installed and that your cowork, Claude Desktop, or CLI environment is properly configured.

Related Skills

Explore More Software Engineering Skills→
kazukinagatakazukinagata
3

setting-up-tasks

Detect MCP connections and initialize provider-specific Waggle databases.

Community
Advanced
kazukinagatakazukinagata
3

notion-provider

Load Notion provider configs, validate fields, and auto-repair schemas.

Community
Advanced
ZhangHanDongZhangHanDong
45

cowork-guide

Document CoWork Skills CLI commands for managing Claude Code skills and plugins.

Community
Basic
kazukinagatakazukinagata
3

provider-contract

Define standardized interface contracts for Waggle provider plugins.

Community
Advanced