How do I install the Motherduck Pricing Roi skill?

Run npx skillmds add motherduckdb/motherduck-pricing-roi in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Motherduck Pricing Roi safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Motherduck Pricing Roi?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Motherduck Pricing Roi free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Motherduck Pricing Roi?

motherduckdb (@motherduckdb) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Motherduck Pricing Roi by motherduckdb

Name: Motherduck Pricing Roi
Rating: 4.2 (5 reviews)
Author: motherduckdb

File contents

Pricing and ROI

Source Of Truth

Always verify current numbers, plan limits, and feature entitlements against the live public pricing page before answering.
If the MotherDuck MCP ask_docs_question feature is available, use it first for pricing-related documentation lookups.
Use the live pricing, Hypertenancy, and Trust & Security pages for exact commercial framing.

Default Posture

Do not hardcode pricing numbers unless you have verified them in the current turn.
When quoting numbers, include the verification date and the public source you checked.
For estimates and comparisons, separate storage, compute, and operational overhead. A narrow price lookup needs only the relevant verified rate and conditions.
Map workload shape to cost shape before comparing vendors or plans.
Treat many pricing questions as risk, predictability, or procurement questions rather than purely technical ones.
Verify plan-sensitive entitlements such as Flight scheduling/runtime limits, custom roles, table-level security, regions, and embedded features in the current turn; do not infer them from an older release note.

Workflow

Identify the workload shape, team size, and comparison baseline.
Determine whether the real concern is raw spend, predictability, procurement, or operational overhead.
Map the workload to MotherDuck cost buckets and plan posture.
Frame ROI in terms of systems replaced, complexity removed, and faster delivery.
Call out what still needs live pricing-page or sales confirmation.

References

Read only the reference sections needed for the current task.

Read references/PRICING_ROI_PLAYBOOK.md for workload-to-cost mapping, publicly safe talking points, ROI framing, and what not to promise

Related Skills

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

motherduck-connect when the pricing discussion depends on connection-path choices
motherduck-security-governance when compliance, residency, or commercial controls affect ROI
motherduck-build-cfa-app and motherduck-build-dashboard when the economics depend on the application architecture

---name: motherduck-pricing-roidescription: Assess MotherDuck costs, plan fit, and ROI using current pricing and the workload’s compute and storage needs.license: MIT--- # Pricing and ROI ## Source Of Truth - Always verify current numbers, plan limits, and feature entitlements against the live public pricing page before answering. - If the MotherDuck MCP `ask_docs_question` feature is available, use it first for pricing-related documentation lookups. - Use the live pricing, Hypertenancy, and Trust & Security pages for exact commercial framing. ## Default Posture - Do not hardcode pricing numbers unless you have verified them in the current turn. - When quoting numbers, include the verification date and the public source you checked. - For estimates and comparisons, separate storage, compute, and operational overhead. A narrow price lookup needs only the relevant verified rate and conditions. - Map workload shape to cost shape before comparing vendors or plans. - Treat many pricing questions as risk, predictability, or procurement questions rather than purely technical ones. - Verify plan-sensitive entitlements such as Flight scheduling/runtime limits, custom roles, table-level security, regions, and embedded features in the current turn; do not infer them from an older release note. ## Workflow 1. Identify the workload shape, team size, and comparison baseline. 2. Determine whether the real concern is raw spend, predictability, procurement, or operational overhead. 3. Map the workload to MotherDuck cost buckets and plan posture. 4. Frame ROI in terms of systems replaced, complexity removed, and faster delivery. 5. Call out what still needs live pricing-page or sales confirmation. ## References Read only the reference sections needed for the current task. - Read `references/PRICING_ROI_PLAYBOOK.md` for workload-to-cost mapping, publicly safe talking points, ROI framing, and what not to promise ## Related Skills Load related skills only for missing capabilities; reuse established context. - `motherduck-connect` when the pricing discussion depends on connection-path choices - `motherduck-security-governance` when compliance, residency, or commercial controls affect ROI - `motherduck-build-cfa-app` and `motherduck-build-dashboard` when the economics depend on the application architecture

Frequently asked questions