dimension-value-management

Automates mapping of unmatched dimension values from AggreUnmatched ICM alerts into NitroUMDP/PLSCoreData PRs.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/huangcd/gcusage --skill dimension-value-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dimension-value-management
Source: https://github.com/huangcd/gcusage/tree/main/.github/skills/dimension-value-management
Command: npx skills add https://github.com/huangcd/gcusage --skill dimension-value-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages new dimension value mappings triggered by ICM AggreUnmatched alerts. Queries ClickHouse for unmatched values, classifies dimensions (Legacy vs Standard), routes to correct PM, computes MurmurHash3 keys via MCP, generates CSV updates, creates PRs in NitroUMDP/PLSCoreData, and verifies deployment. USE WHEN: user says 'unmatched dimension', 'new dimension value', 'AggreUnmatched ICM', 'dimension value management', 'EmptyCheck failure', 'snd_alert', 'dimension mapping', or references ICM with 'AggreUnmatched_' in title.

Core Features & Use Cases

  • Classifies dimensions as Legacy (DimMapping CSV) or Standard (StandardDimension CSV) and queries ClickHouse for top unmatched values.
  • Computes MurmurHash3 keys via MCP, generates precise CSV updates, and creates pull requests in NitroUMDP/PLSCoreData.
  • Orchestrates end-to-end PR workflows and deployment verification, ensuring unmatched values are resolved.

Quick Start

Provide an ICM incident ID and the dimension name to start the end-to-end dimension value mapping workflow.

Frequently Asked Questions about dimension-value-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate dimension value mapping from AggreUnmatched ICM alerts?

Automating dimension value mapping from AggreUnmatched ICM alerts involves querying ClickHouse for unmatched values, classifying dimensions as Legacy or Standard, computing MurmurHash3 keys, updating CSVs, and creating PRs in NitroUMDP or PLSCoreData repositories.

What is the difference between Legacy and Standard dimension management in CSV updates?

Legacy dimension management updates DimMapping CSVs, whereas Standard dimension management updates StandardDimension CSVs. The classification routes the dimension to the correct PM and determines which CSV file receives the hash key and value mappings.

How do I resolve EmptyCheck failures and unmatched dimension values in ClickHouse?

Resolving EmptyCheck failures and unmatched dimension values requires querying ClickHouse for the new values, computing their MurmurHash3 keys, updating the relevant DimMapping or StandardDimension CSVs, and submitting a PR to deploy the fix.

Do I need local ClickHouse access and repository permissions to manage dimension mappings?

Yes, managing dimension mappings requires local access to ClickHouse, DimMapping CSVs, StandardDimension CSVs, MCP hash tooling, and the NitroUMDP and PLSCoreData repositories to perform PR creation and data validations.

How to compute MurmurHash3 keys for new dimension values before creating a pull request?

Computing MurmurHash3 keys for new dimension values is handled via MCP hash tooling during the automated workflow, which then generates precise CSV updates and creates the necessary pull requests in NitroUMDP or PLSCoreData.

What steps are needed to verify deployment after creating a dimension mapping PR?

Deployment verification after creating a dimension mapping PR is orchestrated end-to-end by the workflow, ensuring the unmatched values are resolved and the updated CSVs are successfully deployed across the NitroUMDP and PLSCoreData repositories.