prod-trends

Compares weekly community, GitHub, and financial metrics to detect patterns and risks.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/EvolutionAPI/evo-nexus --skill prod-trends
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prod-trends
Source: https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/prod-trends
Command: npx skills add https://github.com/EvolutionAPI/evo-nexus --skill prod-trends

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable routine to compare community, GitHub, and financial metrics week-over-week so teams can detect patterns, surface risks, and identify opportunities without manual data wrangling.

Core Features & Use Cases

  • Multi-source aggregation: Collects data from Discord reports, GitHub reviews, Stripe/Omie financial feeds, and ADW runner metrics.
  • Automated trend calculation and classification: Computes absolute and percentage variance, assigns direction and status using defined thresholds, and highlights persistent trends, correlations, anomalies, and seasonality.
  • Report generation and persistence: Produces a populated HTML report from a template, a summarized Markdown version, and saves a JSON snapshot for historical tracking; sends a short Telegram summary when complete.
  • Use Case: Run every week to monitor community engagement, engineering throughput, and subscription revenue to guide product and ops decisions.

Quick Start

Generate a weekly trends report comparing the last 7 days to the prior week, save the HTML and markdown outputs, and persist the JSON snapshot.

Frequently Asked Questions about prod-trends

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

FAQPage Schema
How do I automate weekly trends reporting for community engagement, GitHub activity, and MRR?

Weekly trends reporting for community engagement, GitHub activity, and MRR is automated by comparing week-over-week metrics from Discord, GitHub, and Stripe or Omie to calculate variance and generate summarized Markdown and HTML reports.

What is the best way to compare week-over-week financial and engineering metrics?

The best way to compare week-over-week financial and engineering metrics is to aggregate data from GitHub reviews and Stripe or Omie accounting feeds, then compute absolute and percentage variance to classify status using defined thresholds.

Can I use Discord HTML reports and ADW logs for team health checks?

Yes, you can use Discord HTML reports and ADW logs for team health checks by applying this Skill to extract community and runner metrics, detect persistent trends or anomalies, and generate a populated HTML report for release retrospectives.

How do I generate and persist a JSON snapshot of weekly metric variances?

To generate and persist a JSON snapshot of weekly metric variances, the Skill calculates absolute and percentage changes across community, code, and finance data, then saves the historical tracking file to memory/trends.

Does weekly trend detection work with Stripe and Omie accounting data sources?

Yes, weekly trend detection works with Stripe and Omie accounting data sources by ingesting financial feeds, calculating subscription revenue variances, and highlighting correlations or seasonality patterns alongside GitHub and Discord metrics.

What format are the automated trend review reports delivered in?

Automated trend review reports are delivered as a populated HTML report from a template, a summarized Markdown version, a persisted JSON snapshot, and a short Telegram summary sent upon completion.