armor-profile
Profile tables and columns for statistics and distributions. Handles "profile this table", "show column stats", "data distribution", "table statistics", "cardinality analysis".
What this skill does
# Data Profiling
Analyze table and column statistics, distributions, and data characteristics.
## Prerequisites
- AnomalyArmor API key configured (`~/.armor/config.yaml` or `ARMOR_API_KEY` env var)
- Python SDK installed (`pip install anomalyarmor`)
## When to Use
- "Profile this table"
- "Show column statistics"
- "What's the data distribution?"
- "Cardinality analysis"
- "Show null rates"
- "Table row counts over time"
## Profiling Metrics
### Table-Level Metrics
- **row_count**: Number of rows
- **freshness**: Time since last update
### Column-Level Metrics
- **null_rate**: Percentage of null values
- **distinct_count**: Number of unique values (cardinality)
- **min/max**: Value ranges for numeric/date columns
## Steps
1. Get metrics summary for the asset
2. List existing metrics to see what's being tracked
3. View metric snapshots for trends over time
4. Create new metrics if needed for additional coverage
## Example Usage
### Get Table Profile Summary
```python
from anomalyarmor import Client
client = Client()
# Get metrics summary
summary = client.metrics.summary("asset-uuid")
print(f"Total Metrics: {summary.total_metrics}")
print(f"Passing: {summary.passing_count}")
print(f"Failing: {summary.failing_count}")
# List all metrics
metrics = client.metrics.list("asset-uuid")
print("\nMetrics:")
for m in metrics:
print(f" {m.metric_type}: {m.name}")
print(f" Status: {m.status}")
if m.last_value is not None:
print(f" Last Value: {m.last_value}")
```
### Get Column Statistics
```python
# List column-level metrics
column_metrics = client.metrics.list("asset-uuid", metric_type="null_rate")
print("Null Rates by Column:")
for m in column_metrics:
print(f" {m.column_name}: {m.last_value}%")
# Get distinct counts
distinct_metrics = client.metrics.list("asset-uuid", metric_type="distinct_count")
print("\nDistinct Counts:")
for m in distinct_metrics:
print(f" {m.column_name}: {m.last_value} unique values")
```
### View Trends Over Time
```python
# Get metric snapshots (historical values)
snapshots = client.metrics.snapshots(
asset_id="asset-uuid",
metric_id="metric-uuid",
limit=30
)
print("Row Count Trend (last 30 days):")
for snapshot in snapshots:
print(f" {snapshot.captured_at}: {snapshot.value}")
```
### Create New Profile Metrics
```python
# Add row count metric
row_metric = client.metrics.create(
asset_id="asset-uuid",
metric_type="row_count",
table_path="public.orders",
capture_interval="daily"
)
print(f"Created row count metric: {row_metric.id}")
# Add null rate metric for a column
null_metric = client.metrics.create(
asset_id="asset-uuid",
metric_type="null_rate",
table_path="public.orders",
column_name="customer_id",
capture_interval="daily"
)
print(f"Created null rate metric: {null_metric.id}")
# Add distinct count metric
distinct_metric = client.metrics.create(
asset_id="asset-uuid",
metric_type="distinct_count",
table_path="public.orders",
column_name="status",
capture_interval="daily"
)
print(f"Created distinct count metric: {distinct_metric.id}")
```
### Trigger Immediate Capture
```python
# Capture metrics now (don't wait for schedule)
result = client.metrics.capture("asset-uuid", "metric-uuid")
print(f"Captured value: {result['value']}")
print(f"Captured at: {result['captured_at']}")
```
## Expected Output
```
=== Table Profile: warehouse.public.orders ===
Summary:
Total Metrics: 8
Passing: 7
Failing: 1
Table Metrics:
row_count: 1,234,567 rows
freshness: Updated 2 hours ago
Column Statistics:
order_id:
Null Rate: 0%
Distinct Count: 1,234,567 (100% unique)
customer_id:
Null Rate: 0.1%
Distinct Count: 45,678
status:
Null Rate: 0%
Distinct Count: 5 (enum-like)
created_at:
Null Rate: 0%
Min: 2023-01-01
Max: 2026-01-31
Row Count Trend (7 days):
Jan 25: 1,200,000
Jan 26: 1,210,000
Jan 27: 1,220,000
Jan 28: 1,225,000
Jan 29: 1,230,000
Jan 30: 1,232,000
Jan 31: 1,234,567
```
## Follow-up Actions
- For high null rates: Create validity rules with `/armor:quality`
- For unexpected cardinality: Investigate with `/armor:investigate`
- For row count anomalies: Set up alerts with `/armor:alerts`
- For trending issues: Add more granular metrics
- To understand data flow: Check lineage with `/armor:lineage`
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.