AI Agent Hub
Back to skills
Metabase Wrap icon

Metabase Wrap

Data Analysis Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @user_922b1001/metabase-wrap into your AI assistant.

About this skill

Problem to Solve

Metabase is a BI system, and direct integration from a Clojure project or automation pipeline can introduce scattered concerns such as requests, authentication, and result conversion. The listed positioning of Metabase Wrap is a Clojure-side wrapper entry point around Metabase BI, making it easier to consolidate fragmented integration points.

How It Works and Boundaries

Based on SKILL.md, the core role is a wrap layer in Clojure for Metabase BI. The github and automation tags also suggest possible use in scripted, task-based, or workflow automation scenarios. It is worth evaluating when:
- Calling Metabase from Clojure projects: if the project already has Clojure dependencies or scripts, a consistent entry point is easier to maintain.
- BI operations in automation: if CI, scheduled jobs, or scripts need to trigger Metabase-related actions, check the wrapper's scope first.
- GitHub workflow integration: within an existing GitHub automation chain, Metabase calls can be organized as reusable steps.

The provided details do not specify which Metabase APIs, authentication methods, or result shapes are supported. Before adoption, review source code, version, and target environment compatibility.

Use Cases

  • Call Metabase BI from a Clojure project and consolidate scattered requests and response handling into one wrapper entry point.
  • Prepare reusable scripts for Metabase-related actions in a GitHub Actions workflow to reduce duplicated steps.
  • Integrate Metabase BI inside Clojure automation tasks and organize BI-related steps into maintainable scripts.
  • Separate the Metabase integration point from business code in a data pipeline, making it easier to review and replace.

Best For

  • Backend engineers maintaining Metabase integration scripts in Clojure, who want to consolidate BI calls into one entry point.
  • Platform engineers responsible for GitHub automation pipelines, who want to include Metabase-related steps in reusable tasks.
  • Engineers building Clojure services around a data platform, who want to reduce repeated Metabase integration boilerplate.
  • Operations or platform engineers maintaining Clojure automation tasks, who want to centralize the Metabase integration point.