prod-trends

Analyze weekly community, GitHub, and financial metrics against prior-week baselines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered weekly signals from community engagement, GitHub activity, and financial performance into a clear, action-oriented view of what is improving, worsening, and worth investigating.

Core Features & Use Cases

  • Weekly, week-over-week comparisons: Evaluates community (Discord), engineering (GitHub), and financial (MRR/refunds/subscriptions) metrics using current vs prior-week baselines.
  • Actionable risk classification: Assigns 🟢 healthy, 🟡 attention, or 🔴 risk status per metric using explicit thresholds and only escalates to red with evidence.
  • Automated reporting outputs: Generates an HTML report from the specified template, a summarized Markdown report, and a JSON snapshot for accumulating trend history.

Quick Start

Run the weekly routine by asking for "trends analysis" or "weekly comparison" so EvoNexus generates the HTML and Markdown reports for the current week.

Frequently Asked Questions about prod-trends

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

FAQPage Schema
How do I analyze weekly community and financial metrics for risk classification?

Weekly metrics analysis compares current community, GitHub, and financial data against a prior-week baseline to classify risks as healthy, attention, or elevated. It computes variances and assigns status levels using explicit thresholds to highlight growth signals and areas needing investigation.

How do I generate a week-over-week trends report from GitHub activity and MRR data?

To generate a week-over-week trends report, the system reads prior HTML reports and operational metrics, computes variances, and renders an HTML report, a Markdown summary, and a JSON snapshot. You simply request a trends analysis to compare current data against the previous week.

What is the best way to automate weekly checkups for community health and engineering metrics?

Automating weekly checkups involves comparing current Discord, GitHub, and financial metrics against prior-week references. The process assigns actionable risk classifications and outputs an HTML report, summarized Markdown, and JSON snapshot to your configured workspace paths.

Can I compare current operational metrics without a prior-week baseline?

Yes, when prior-week reference data is unavailable, current operational metrics are treated as a baseline. The analysis still evaluates community, GitHub, and financial data to establish initial variances and render the HTML, Markdown, and JSON trend snapshots.

How does risk classification handle evidence for worsening financial or GitHub metrics?

Risk classification assigns healthy, attention, or risk statuses per metric using explicit thresholds, only escalating to red with evidence. It evaluates financial MRR, refunds, and GitHub activity variances to identify worsening patterns that require operational investigation.