1.7K skills · sorted by relevance
Explore and query measurements stored in Axiom MetricsDB. The skill discovers metrics and tags, checks measurement types and units, and builds MPL queries, Axiom’s metrics query language, to retrieve values and aggregate them over a chosen period.
Collect and assess quality metrics for Simulink models using the metric.Engine API. Use when evaluating model design quality (maintainability, complexity, architecture) or testing completeness (unit testing, SIL, PIL, coverage, pass rates) after edits or test runs. Covers metric discovery, collection, report generation, and diagnostics. Triggers on: "collect metrics", "quality metrics", "metric.Engine", "testing metrics", "maintainability metrics", "SIL metrics", "PIL metrics", "what metrics are available", "assess quality", "coverage metrics", "generate metric report", "diagnose metric errors".
The English summary is being prepared. Showing the original description.
Metrics architecture — produce a complete metrics plan given a product description. North Star, input metrics tree, instrumentation spec, action triggers, and counter-metrics. Use when asked to "design a metrics framework", "what should we measure", "build a metrics system", "define our KPIs", "what are our success metrics", "metrics strategy", or "what do we track".
The English summary is being prepared. Showing the original description.
Choose and track startup metrics suited to the business model and funding stage. Calculate customer acquisition cost, customer lifetime value, retention, and cash usage, then organize trends and targets for operational reviews and investor reporting.
Diagnose failures in GKE HorizontalPodAutoscaler (HPA), which adjusts Pod counts automatically. Investigate missing metrics, unexpected scaling behavior, and slow reactions, then receive proposed configuration fixes or commands for review before deployment.
Quickly look up SaaS financial metrics, including recurring revenue and customer acquisition costs. Get definitions, formulas, benchmarks, and warning signs, plus reminders of which metrics matter when reviewing features, pricing, acquisition channels, or business health.
When the user wants to define GTM metrics, build a metrics dashboard, measure pipeline efficiency, or track AI product performance. Also use when the user mentions 'GTM metrics,' 'revenue latency,' 'pipeline metrics,' 'TTFV,' 'time-to-first-value,' 'data health,' 'attribution,' 'conversion rate,' 'CAC,' 'LTV,' 'NRR,' 'GTM dashboard,' 'magic number,' 'pipeline velocity,' or 'funnel metrics.' This skill covers GTM measurement from metric selection through dashboard design, including AI-specific cost metrics, attribution models, and weekly review cadences. Do NOT use for technical implementation, code review, or software architecture.
The English summary is being prepared. Showing the original description.
Choose and audit startup metrics using Croll and Yoskovitz's "Lean Analytics". Use when the user mentions "what metrics should we track", "KPIs", "north star metric", "One Metric That Matters (OMTM)", "vanity metrics", "analytics dashboard", "DAU/MAU", "churn benchmark", or "measure product-market fit". Also trigger when choosing metrics for a startup or feature, auditing a dashboard for vanity metrics, setting metric targets and baselines, or instrumenting a product by business model and stage. Covers good-vs-vanity metrics, the One Metric That Matters, metrics by business model, the five startup stages, and benchmarks. For the build-measure-learn loop, see lean-startup. For fixing activation and retention, see improve-retention.
The English summary is being prepared. Showing the original description.
Analyze flow metrics to identify delivery bottlenecks and improve throughput. Use when the user says "flow metrics", "why is delivery slow", "cycle time analysis", "WIP analysis", "throughput review", "what's our lead time", "DORA metrics", "where is work getting stuck", "Kanban metrics", or wants to diagnose delivery performance using data - even if they don't explicitly say "flow metrics review". Based on "Making Work Visible" by Dominica DeGrandis (WIP limits, flow blockers, time thieves) and "Accelerate" by Forsgren, Humble & Kim (DORA metrics, delivery performance indicators).
The English summary is being prepared. Showing the original description.
Plan technology strategy and engineering team growth with frameworks for technical debt, hiring, architecture decisions, and vendor evaluation. Use Python tools and decision templates to prioritize improvements, structure teams, and track engineering performance.
Design a product metrics dashboard with clearly defined measures, data sources, charts, targets, and alert thresholds. The skill produces a Markdown specification that also covers dashboard layout, review schedules, and responsibilities for responding to alerts.
Configure GKE logging, metrics collection, dashboards, and alerts with Cloud Logging, Cloud Monitoring, and managed Prometheus. Diagnose missing measurements, collection failures, permission errors, and alert rule problems to identify appropriate configuration changes.
Monitor TPU workloads on GKE using system metrics and PromQL, a metrics query language. Check utilization, memory, node availability, and interruptions to investigate infrastructure issues and calculate average recovery times and intervals between interruptions.
Investigate crashes, out-of-memory errors, and device initialization failures on GKE TPU v6e nodes. The skill checks logs and custom metrics collection for conflicting operations, then guides temporary mitigation by disabling an identified collector.
Builds your north star metric, a metric tree with owned input metrics and guardrails, and a review cadence, as a one-page metrics spec you can paste into a doc. Use it when you ask 'what should our north star be', 'which metric should this team goal on', 'our dashboard is a mess', 'how do we measure AI productivity', 'activation metric', 'OKR metrics', 'vanity metrics', or 'metrics review cadence'. Draws on 254 insights from 118 Lenny's Podcast guests incl. Sarah Tavel, Crystal Widjaja and Jessica Lachs.
The English summary is being prepared. Showing the original description.
Targeted deep research to fill a specific gap in an existing thesis. Use when user says "deepen", "flesh out", "expand on", "fill in", or specifies a thesis section to improve. Also supports --sync-metrics mode — detects stale financial metrics across every in-scope analytical section of a thesis (not just Key Metrics or Summary) and coherently updates every sentence that depends on them, using a Key-Metrics-table / FMP / web-search waterfall. Use when user says "sync metrics", "update the numbers throughout the note", or "fix stale figures across the whole thesis". The batch form `--sync-metrics --all-flagged` syncs every thesis flagged by the latest `$numbers --all-open` in one operation — detection fanned out to capped READ-ONLY agents, one consolidated confirmation gate, direct sequential writes (agents never write).
The English summary is being prepared. Showing the original description.
Targeted deep research to fill a specific gap in an existing thesis. Use when user says "deepen", "flesh out", "expand on", "fill in", or specifies a thesis section to improve. Also supports --sync-metrics mode — detects stale financial metrics across every in-scope analytical section of a thesis (not just Key Metrics or Summary) and coherently updates every sentence that depends on them, using a Key-Metrics-table / FMP / web-search waterfall. Use when user says "sync metrics", "update the numbers throughout the note", or "fix stale figures across the whole thesis". The batch form `--sync-metrics --all-flagged` syncs every thesis flagged by the latest `/numbers --all-open` in one operation — detection fanned out to capped READ-ONLY agents, one consolidated confirmation gate, direct sequential writes (agents never write).
The English summary is being prepared. Showing the original description.
Design KPI dashboards that help teams make decisions using clearly defined performance measures. Choose relevant metrics, organize summary and detail views, document calculations, and address inconsistent figures, database load, and excessive alerts.
Review product performance by comparing usage, retention, revenue, and other metrics with previous periods and targets. Turn the numbers into a scorecard, explain meaningful trends and uncertainties, and recommend investigations or improvement experiments.
Plan technology investments and engineering team growth using structured assessments. Evaluate technical debt, compare building versus buying, document architecture choices, and define engineering health metrics to produce prioritized plans grounded in costs, risks, and business needs.
Query Prometheus metrics through Grafana and manage dashboards as JSON files. Use it to investigate current values and trends, add or adjust panels, and preview dashboard updates before applying them.
Find relevant Google Cloud monitoring metrics for a service or resource. Retrieves current metric definitions through the API, filters them by the requested concepts, and presents selected metrics with their names, data types, units, and monitored resources.
Create weekly reports from Postgres metrics, comparing current figures with recent weeks. Add plain-language explanations for notable changes, flag missing data, and post one report to Slack while keeping database access read-only.
Build dashboards from verified product or business data, with clearly defined metrics, charts, and useful filters. Organize the view from headline results to supporting detail, and check data freshness, numerical consistency, and dashboard behavior before handoff.