Motherduck Explore

Organization

motherduckdb

motherduck-explore

Find and understand MotherDuck databases, tables, columns, shares, and sample data, including which tables hold a given kind of data. Use first when a MotherDuck workspace or schema is unfamiliar.

Overview

Publisher	motherduckdb
Repository	`agent-skills`
Skill name	`motherduck-explore`
Stars	62
Forks	6
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by motherduckdb on GitHub. Read the source before you install it.

Installation

Install the Motherduck Explore AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/motherduckdb/agent-skills/tree/main/plugins/motherduck-skills-claude/skills/motherduck-explore
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/motherduckdb/agent-skills/tree/main/plugins/motherduck-skills-claude/skills/motherduck-explore

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/motherduckdb/agent-skills.git /tmp/agent-skills
mkdir -p .claude/skills
cp -r /tmp/agent-skills/plugins/motherduck-skills-claude/skills/motherduck-explore .claude/skills/motherduck-explore

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Motherduck Explore in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Motherduck Explore on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Motherduck Explore is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Explore MotherDuck Data

Prerequisites

An established MotherDuck connection (or an active MotherDuck MCP server)

Default Posture

Start at the known catalog object; broaden to databases or shares only when the target is unknown.
Prefer fully qualified "database"."schema"."table" names; they are required once more than one database or share is attached.
Check shared databases before concluding that data is unavailable. A share with secure views can hide columns and rows: a missing column in an attached share may be policy, not schema drift.
Use the MotherDuck MCP tools (list_databases, list_tables, list_views, list_columns, list_macros, search_catalog) when available because they return structured results faster than ad hoc SQL. Check list_macros before reimplementing logic; table and scalar macros often encode governed definitions.
When MotherDuck MCP is available and the SQL answers a business question, call get_query_guide first, then read only the relevant Guide topics and validate their claims against the live schema. Follow relatedGuides returned by catalog tools when they govern the objects in scope.
Record whether a share is filtered and whether an existing Dive is Draft, Ready, Endorsed, or Archived; these attributes change what downstream agents should trust or expect to see.
Return a concise schema map with table grain, join keys, date columns, and likely measures before moving into modeling or dashboard work.

Workflow

List databases in scope.
Load relevant Guide context, then list tables and views in the target database.
Inspect columns, types, nullability, and comments before writing queries.
Use targeted profiling or SUMMARIZE when ranges, cardinality, or null rates affect the answer; avoid broad scans for a catalog lookup.
Preview rows with SELECT * ... LIMIT n or USING SAMPLE; on wide tables these read only the row groups they need. Capture grain and join assumptions, and only then move into analytical SQL or modeling work.

References

Read only the reference sections needed for the current task.

Read references/EXPLORATION_PLAYBOOK.md for the full SQL workflow, share discovery patterns, MCP tool guidance, and common exploration mistakes

Related Skills

Load related skills only for missing capabilities; reuse established context.

motherduck-connect for session setup and authentication
motherduck-query for analytical SQL after the schema is understood
motherduck-duckdb-sql for DuckDB syntax patterns during exploration
motherduck-share-data for creating and consuming shares once shared datasets become part of the workflow
motherduck-manage-guides for reading or maintaining the context attached to discovered objects

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/EXPLORATION_PLAYBOOK.md6 KB

Frequently asked questions

What does the Motherduck Explore AI skill do?

Find and understand MotherDuck databases, tables, columns, shares, and sample data, including which tables hold a given kind of data. Use first when a MotherDuck workspace or schema is unfamiliar.

Why use Motherduck Explore on TypingMind?

Because you install it once and use it with any model. Motherduck Explore is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Motherduck Explore in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/motherduckdb/agent-skills/tree/main/plugins/motherduck-skills-claude/skills/motherduck-explore. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Motherduck Explore?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Motherduck Explore?

As many as you like. As long as a model supports skills, you can use Motherduck Explore with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Motherduck Explore AI skill free?

Yes. It is published on GitHub by motherduckdb under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Caveman Stats

JuliusBrussee

CommunityPopular

Show recorded output and cache-read token usage and mode attribution for the current Claude Code session, or locate the host's native usage report. Trigger: /caveman-stats.

Ci Metrics

Query PyTorch CI, GitHub Actions, HUD, Grafana, and infrastructure metrics. Use when users ask about CI duration, job failures, queue times, workflow trends, runner health, dashboard data, or PyTorch…

Notcrawl

Notion archive: search, sync freshness, pages/databases, Markdown exports, SQL counts, and Notcrawl repo work.

Openclaw Test Heap Leaks

openclaw

OrganizationPopular

Investigate OpenClaw pnpm test memory growth, Vitest OOMs, RSS spikes, and heap snapshot deltas.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Explore MotherDuck Data

Prerequisites

Default Posture

Workflow

References

Related Skills

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now