2.5K 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.
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.
Choose one North Star Metric, a central measure of customer value, and three to five supporting measures that influence it. Classify the business by how customers use it and assess the proposed metric against seven criteria.
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.
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.
Add team-specific evaluation criteria to plugin-eval by designing a metric pack, a set of custom checks and measurements. Create its manifest and JSON-producing script, then run it through the evaluator using a consistent output structure.
Choose metrics for AI product revenue, sales efficiency, retention, and computing costs. Plan dashboards and weekly reviews, assess customer data quality, and decide how to credit marketing and sales interactions for completed deals.
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.
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.
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.
Conducts Data Protection Impact Assessments for biometric identification and authentication systems under GDPR Article 35 and Article 9 special category rules. Covers facial recognition, fingerprint, iris scanning, voice recognition, and behavioural biometrics. Applies EDPB Guidelines 3/2019, CNIL Reglement Type Biometrie, and ISO/IEC 24745 biometric template protection. Keywords: DPIA biometric, facial recognition, fingerprint, Art. 35, Art. 9, biometric template, special category.
The English summary is being prepared. Showing the original description.
VictoriaMetrics provider for obz. Covers all 6 metric commands (query, list, info, labels, label-values, series) using MetricsQL, a PromQL superset with extensions like keep_metric_names and range_normalize. This skill should be used when the user mentions "VictoriaMetrics", "MetricsQL", "obz metric -p vm", or needs to query metrics from a VM backend.
The English summary is being prepared. Showing the original description.
Build graph neural networks, models that learn from connected nodes, with PyTorch Geometric. Supports node and graph classification, link prediction, custom datasets, and training approaches for large graphs or graphs containing multiple types of nodes and connections.
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.
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.
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.
Turn Cloud Monitoring metric definitions and resource filters into validated PromQL queries, a language for querying monitoring data. Choose suitable aggregation functions, preserve supplied resource names, and format queries for use in Cloud Monitoring.
Produce a complete metrics definition doc — metric name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like. Given a product area, outputs the full metrics spec. Use when asked to "define KPIs", "metrics framework", "what should we measure", "north star metric", or "instrument this feature".
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.
Define a practical KPI dashboard, a view of key business measures, by organizing metric definitions, sources, formulas, periods, targets, and owners. Produces empty CSV, SQL, JSON Schema, or Notion import mappings when requested.
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.
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.
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.