Giskard to Collibra export Agent Skill

Export Giskard scan results into Collibra AI Governance.

Context cost
850 tokensestimated from the bundle, loaded when it triggers
Bundle
3 of 4 fileshanded out here; the rest is at its source
Licence
Apache-2.0the author’s own terms
Last change
—v1.0.0
Servers it uses
Noneruns standalone

What it does

Export Giskard scan results into Collibra AI Governance. Use this whenever the user asks to export, push, sync, or import a Giskard scan, agent, or project (e.g. "Zephyr") into Collibra, or to update Collibra AI Governance assets, monitors, or Quality-tab metrics from Giskard. Also use it when the user asks to "retrieve the latest scan of a project and send it to Collibra", even if they do not say the word "export".

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

data science

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md3.3 kB · preview
--- name: giskard-to-collibra license: Apache-2.0 metadata: author: Giskard version: 1.0.0 category: integration tags: [giskard, collibra, ai-governance, scan, vulnerability, export, metrics] ---
12# Giskard to Collibra export
13
14This skill is self-contained. scripts/giskard_to_collibra.py does the whole job: it finds the scan in Giskard Hub, builds the Collibra asset hierarchy (AI Agent, AI Agent Version, AI Endpoint, AI Monitors, and the deployment complex relation), imports it into Collibra, and pushes pass/fail metrics.
15
16All paths below are relative to this skill's base directory.
17
18## One-time setup
19
20The user may not be technical. Do these checks for them and explain in plain language.
21
221. Check Python 3.10 or newer is available (python3 --version).
232. Install the dependencies: python3 -m pip install -r requirements.txt. If the environment blocks system-wide installs, create a virtualenv first and use its Python for every command below.
243. Check that a .env file exists in the current working directory (or next to the script) with values for all six variables listed in env.example. If the file is missing, or any of the six variables has no value, do not guess and do not proceed. Explicitly ask the user for each missing value, then create or complete .env. Never print or echo the secret values back.
25
26## Run the export
27
281. If the user gives a scan ID, run python3 scripts/giskard_to_collibra.py --scan-id <SCAN_ID>. It exports exactly that scan. Done.
292. If the user gives a project ID, run python3 scripts/giskard_to_collibra.py --project-id <PROJECT_ID>. It exports the project's latest finished scan. Done.
303. If the user gives a project name (the usual case), first run python3 scripts/giskard_to_collibra.py --list-projects. It prints one id name line per project. Match the user's words against the names yourself. Tolerate case differences and small typos ("zyphyr" means "Zephyr"). If the match is not obvious, show the names and ask the user. Then run with --project-id <the matched id>.
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md512 words
Files3
LicenceApache-2.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈160
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
690
on trigger
The instruction body and 2 supporting files, read only when the skill fires.
0.43%
of a 200k window
Ten skills this size would take about 4% of the window before you open a file.
050k100k150k200k context window

850 tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Small enough to keep loaded permanently without thinking about it.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

The download carries 3 of the 4 files in its source folder; the list here names 3 files, 11.8 kB on disk. Mostly text — the instructions the model reads — with 1 script in it that your client would run only if the instructions tell it to. The other one is not in the download — listed after these, with why.

  • SKILL.md3.3 kB
  • requirements.txt0.1 kB
  • scripts/giskard_to_collibra.py8.4 kB

Not in the download

Not carried is a type a skill download does not hold. Marked read: its SKILL.md or scripts name the file, so without it the skill works only in part. Take it from its source.

  • env.exampleread · not carried
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 1 script beside the text, so the download is 3 files — not the whole of its source: 1 file is left out, and the skill reads it. It is listed under the files, with why. The Apache-2.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Giskard to Collibra export · 850 tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/giskard-to-collibra-export/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/giskard-to-collibra-export" ] && { [ ! -e .claude/skills/giskard-to-collibra-export ] || { mv .claude/skills/giskard-to-collibra-export "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/giskard-to-collibra-export" .claude/skills/ && echo "Installed .claude/skills/giskard-to-collibra-export"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add giskard-ai/giskard-to-collibra-export

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/giskard-to-collibra-export/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/giskard-to-collibra-export/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/giskard-to-collibra-export" ] && { [ ! -e ~/.claude/skills/giskard-to-collibra-export ] || { mv ~/.claude/skills/giskard-to-collibra-export "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/giskard-to-collibra-export" ~/.claude/skills/ && echo "Installed ~/.claude/skills/giskard-to-collibra-export" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/giskard-to-collibra-export/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as giskard-to-collibra in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, giskard-to-collibra-export. Not in this download: 1 file of its source, which its SKILL.md or scripts read (which one, and why). Take it from its source.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version1.0.0
Publishedno release date on file
PriceFree
Referencegiskard-ai/giskard-to-collibra-export

Versions

v1.0.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v1.0.0
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v1.0.0 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill