motherduck-cookbook

Name: motherduck-cookbook
Availability: InStock
Author: MotherDuck

Validate MotherDuck cookbook catalog front matter and metadata consistency.

71|10|Updated Dec 11, 2024

Search Tags:#documentation #validation #readme #catalog #starter #front-matter #flight-plans

Ready to run

npx skills add https://github.com/motherduckdb/motherduck-cookbook --skill motherduck-cookbook

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: motherduck-cookbook
Source: https://github.com/motherduckdb/motherduck-cookbook/tree/main/.agents/skills/motherduck-cookbook
Command: npx skills add https://github.com/motherduckdb/motherduck-cookbook --skill motherduck-cookbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps maintain and publish the MotherDuck cookbook catalog, ensuring README front matter, catalog entries, and starter scripts stay consistent across the project.

Core Features & Use Cases

Catalog front matter validation and consistency checks across entries
Guidance for Flight Plans and starter scripts integration
Catalog generation and release publishing workflow
Documentation for agent-facing descriptions and MCP tooling references

Quick Start

Run the starter workflow to validate and publish updated catalog metadata for this repository.

Frequently Asked Questions about motherduck-cookbook

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

FAQPage Schema

How do I validate catalog front matter fields for consistency across a repository?▼

Catalog front matter validation checks that fields like id, type, category, features, and prompt are correct across entries. It enforces compliance with the catalog schema and tooling rules to ensure metadata stays aligned for agent discovery.

What is the best way to maintain README front matter and catalog entries for a documentation project?▼

Maintaining README front matter and catalog entries involves organizing and validating catalog metadata to ensure starter scripts and flight-plan templates remain consistent. This applies schema compliance checks to front matter fields and run instructions across the project.

Does MCP tooling require specific safety considerations in catalog metadata?▼

MCP tooling requires safety considerations to be consistent within catalog metadata. The validation process ensures readme content aligns with MCP guidelines and that front matter fields and run instructions meet the catalog schema requirements.

How do I generate and publish a catalog for agent-facing descriptions?▼

Catalog generation and release publishing workflows organize validated metadata to enable agent discovery and deployment. You run the starter workflow to validate and publish updated catalog metadata for the repository.

Why does flight-plan template validation fail when front matter fields are missing?▼

Flight-plan template validation fails when front matter fields are missing because the process enforces strict compliance with the catalog schema. It checks that required fields like id, type, category, features, and prompt are present and correctly formatted.