Borrowing it
Nothing to install: this file belongs to zuarbase/Zuar-Portal-MCP-Public. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zuarbase/Zuar-Portal-MCP-Public/main/.claude/skills/lineage-health/SKILL.mdgit clone --depth 1 https://github.com/zuarbase/Zuar-Portal-MCP-PublicWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zuarbase/zuar-portal-mcp-public/lineage-health)<a href="https://agentmods.dev/skills/zuarbase/zuar-portal-mcp-public/lineage-health"><img src="https://agentmods.dev/badge/skills/zuarbase/zuar-portal-mcp-public/lineage-health/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zuarbase/zuar-portal-mcp-public/lineage-health"><img src="https://agentmods.dev/badge/skills/zuarbase/zuar-portal-mcp-public/lineage-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02102 |
| Opus 5 | $0.00000 | $0.01051 |
| Sonnet 5 | $0.00000 | $0.00420 |
| Haiku 4.5 | $0.00000 | $0.00210 |
Grade A, and why
lineage-health scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zuar Portal — Lineage & Pipeline Health
This skill answers data-lineage and pipeline-health questions from the Lineage Explorer and Runner Health dashboards deployed on a Zuar Portal. It is the read/ask half of a two-part system:
- Runner side (zuar-runner MCP): jobs build the lineage tables —
runner.job_lineage_status,runner.bottom_up_lineage,runner.lineage_used_flag, and the materializedrunner_health_mqb.*tables. Source:github.com/zuarbase/cust-lineage-health. - Portal side (this MCP): the Lineage Explorer + Runner Health blocks visualize those tables. They
ship as a content pack — deploy them with the
content_packstools (list_content_packs→preview_content_pack→import_content_pack, assigning your DB connection to the pack's datasource).
Once the blocks are on a page, use this skill to answer questions from the data behind them — either
by executing the block's bound query (execute_query) or by walking the page to its bound queries
(find_resource → get_resource → execute_query, see "Reading it from the page" below).
Mental model — lineage is a DAG of tables and the jobs that build them
Every node is a data model / table; every edge is "job B reads table A to build table B". A node carries the health of the job that produces it (status, last run, component counts) and two analytics flags:
is_used_in_analytics— this table is directly referenced by a dashboard/analytics layer.impacts_analytics— this table is upstream of something used in analytics (breaking it breaks analytics, even if nothing reads it directly).
A table with neither flag and no downstream references is a dead-end / unused table.
The data model (source tables, in the Runner database)
Reach these through the datasource the content pack brings in (or any datasource on the Runner DB). Column names use the Runner's quoted, space-and-caps convention — quote them exactly.
| Table | Grain | Key columns |
|---|---|---|
runner.job_lineage_status |
one row per data model | "Data Model", "Job" (job number), "Job Title", "TYPE *" (IO/SQL/…), "Status", "Last Complete", "Components", "Components OK" |
runner.bottom_up_lineage |
one row per edge | "Data Table" (upstream), "Downstream Model" (dependent), "Min Depth" |
runner.lineage_used_flag |
one row per model | data_model, is_used_in_analytics |
runner_health_mqb.lineage_materialized |
edge (job→job) | input_table_job_id, output_table_job_id, depth |
runner_health_mqb.jobs_master |
one row per job | job attributes for the Health dashboard |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 158 lines · 0 tokens per session scan A f77031ad2664
lineage-health is a skill published in the GitHub repository zuarbase/Zuar-Portal-MCP-Public (0 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,102 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.