d001-sanity-check
v0.8.0Daily D-001 Performance Cube data-pipeline sanity check (Jira DMABGS-3270): verify Snowflake tasks succeeded, each cube slice is fresh with non-zero revenue and spend, and Google/Bing per-source spend is non-zero, reconcile revenue and spend vs. source day-by-day over a rolling ~2 months, then post a pass/fail summary to Slack.
By G2 GDM Team0 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 17, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install d001-sanity-check for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install d001-sanity-check@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/smarimadappa/tech-hub-sanity-checksClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/d001-sanity-check/.
Plugin files
├── .claude-plugin/plugin.json└── skills/d001-sanity-check/SKILL.md
Included Skills1
Run the daily D-001 Performance Cube data-pipeline sanity check (Jira DMABGS-3270) and post a pass/fail summary to Slack. Use this skill WHENEVER the user asks to run or trigger the "D-001 sanity check", "sanity check the performance cube", "check the MDD pipeline", verify the D-001 Snowflake tasks ran, confirm the cube's max dates are current, or when a scheduled task invokes the daily D-001 check — even if they phrase it loosely (e.g. "did the cube refresh land today?", "is the GDM data fresh?", "run the tech-hub sanity check"). It checks the GDM Snowflake + Slack connectors and live compute first, verifies the two D-001 Snowflake tasks (cube refresh + MDD) succeeded and the six max-date checks are current, then posts the result (tagging the week's on-call) to #sanity-check-testing. Prefer this skill over ad-hoc SQL whenever D-001 / performance cube / MDD monitoring is involved.
Plugin manifests1
{
"name": "d001-sanity-check",
"version": "0.8.0",
"description": "Daily D-001 Performance Cube data-pipeline sanity check (Jira DMABGS-3270): verify Snowflake tasks succeeded, each cube slice is fresh with non-zero revenue and spend, and Google/Bing per-source spend is non-zero, reconcile revenue and spend vs. source day-by-day over a rolling ~2 months, then post a pass/fail summary to Slack.",
"author": {
"name": "G2 GDM Team",
"email": "[email protected]"
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[d001-sanity-check on Agent Plugins Marketplace](https://pluginsmp.com/plugins/d001-sanity-check)