AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Rudder Data Path Diagnostician Maintainer

skill-undertone0809-rudder-rudder-data-path-diagnostician-maintainer · by Undertone0809

Use when Rudder pages or product surfaces show missing, stale, sparse, empty, slow, or wrong data, including Calendar, runs, issues, dashboard counts, chat output, prod/local org data, API/UI/DB mismatches, or “这个数据从哪来”.

↗ Website ↗ Repository
— No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-undertone0809-rudder-rudder-data-path-diagnostician-maintainer

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-undertone0809-rudder-rudder-data-path-diagnostician-maintainer)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Rudder Data Path Diagnostician Maintainer? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Rudder Data Path Diagnostician Maintainer

Overview

Trace Rudder surface data from UI query through API, service aggregation, database rows, derived sources, org scope, and runtime instance.

When to Use

Use this skill when:

  • a Rudder screen has missing, stale, sparse, empty, or wrong data
  • the user asks where a value comes from
  • UI, API, service, DB, org scope, or runtime source might disagree
  • the task is evidence-backed lineage or root cause before fixing/seed changes

Do not use this skill when:

  • pure visual polish where data is correct
  • broad performance tuning; use performance maintainer
  • guess from screenshot without tracing the chain

Core Pattern

symptom -> environment/org -> UI query -> API/service -> source rows -> root cause -> fix or explanation

Quick Reference

| Situation | Action | | --- | --- | | Missing page data | Confirm environment and org first | | Wrong count | Trace API aggregation and filters | | Explainer mode | Read source/code path before DB if enough | | Fix requested | Keep org scope and product contracts aligned |

Implementation

  1. Confirm target environment, org, route, and symptom.
  2. Identify UI query/client state and API route.
  3. Inspect service aggregation and filters.
  4. Read source rows safely when needed.
  5. Classify root cause and recommend or implement the narrow fix.
  6. Hand off lineage, evidence, and verification status.

Reference files are part of this skill contract. Before executing high-risk actions or final judgments, load references/runbook.md for the detailed legacy workflow, examples, validation cases, and command-level guidance.

Use evals/ when the route needs that detail; keep the entrypoint thin.

Common Mistakes

| Mistake | Fix | | --- | --- | | Assuming empty UI means empty DB | Trace filters and org/runtime first. | | Jumping to seed data | Diagnose source chain before seeding. | | Ignoring derived data generation | Check derivation jobs/services. | | Fixing without org scoping checks | Preserve organization boundaries. |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Data & Analytics