growth-metrics

Generate weekly growth metric snapshots and flag underperforming leading indicators.

5|2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/NOMARJ/sigil --skill growth-metrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: growth-metrics
Source: https://github.com/NOMARJ/sigil/tree/main/packs/business/skills/growth/growth-metrics
Command: npx skills add https://github.com/NOMARJ/sigil --skill growth-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes how product teams select, evaluate, and report go-to-market metrics by reading the GTM spec, producing a weekly metrics snapshot, and flagging leading indicators that fall below defined thresholds to prompt a GTM review.

Core Features & Use Cases

  • Motion-specific metrics: maps leading and lagging indicators to developer-led, content-led, community-led, and relationship-led motions to avoid vanity metrics.
  • Per-product templates and thresholds: provides weekly and monthly metric examples, target values, and pivot thresholds for products such as Sigil, InstaIndex, Operable, and PolicyPA.
  • Weekly review format and persistence: generates a standardized review document, highlights failing indicators and trends, and saves snapshots for trend analysis and escalation.

Quick Start

Generate a weekly growth metrics snapshot for Sigil using the GTM spec and flag any leading indicators below threshold.

Frequently Asked Questions about growth-metrics

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

FAQPage Schema
How do I generate a weekly growth metrics snapshot for product go-to-market motions?

Generate a weekly growth metrics snapshot by reading the product GTM spec and historical actuals to map leading and lagging indicators, then saving the report to .nomark/growth/ for trend analysis and review.

What leading indicators should I track for a developer-led go-to-market strategy?

Track developer-led go-to-market leading indicators by mapping specific motion metrics from the GTM spec to avoid vanity metrics, applying defined target values and pivot thresholds to flag underperformance during weekly review cycles.

How do I flag underperforming leading indicators against consecutive failure thresholds?

Flag underperforming leading indicators by evaluating weekly metric actuals against consecutive-failure thresholds defined in the GTM spec, highlighting failing trends in the standardized review document for immediate escalation.

Can I use per-product metric templates and thresholds for community-led growth motions?

Apply per-product metric templates and thresholds for community-led growth motions by mapping specific leading and lagging indicators with target values and pivot thresholds tailored to products like Sigil, InstaIndex, and Operable.

What's the best way to standardize go-to-market metrics reporting across different product motions?

Standardize go-to-market metrics reporting by applying motion-specific templates across developer-led, content-led, community-led, and relationship-led motions, generating persistent weekly review documents that highlight failing indicators and trends.

When do I need to trigger a GTM review based on weekly metric failures?

Trigger a GTM review when leading indicators fall below defined consecutive-failure thresholds during the weekly metrics snapshot evaluation, prompting escalation through the saved standardized report document highlighting failing trends.