refresh-metrics

Scan MCP issues and specifications to update governance document metrics.

4|1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/samjhecht/wrangler --skill refresh-metrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refresh-metrics
Source: https://github.com/samjhecht/wrangler/tree/main/skills/refresh-metrics
Command: npx skills add https://github.com/samjhecht/wrangler --skill refresh-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically scans MCP data to refresh issue/spec metrics in governance docs, ensuring accuracy.

Core Features & Use Cases

  • Aggregate metrics: counts by status, specs, top projects
  • Update docs: issues/README, specs/README, roadmap
  • Consistency checks: Last updated times

Quick Start

Run: /wrangler:refresh-metrics to refresh governance metrics.

Frequently Asked Questions about refresh-metrics

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

FAQPage Schema
How do I automate updates to governance metrics in documentation?

Automate governance metrics updates by scanning MCP issues across status, priority, type, and phase to compute current counts and percentages, then automatically refresh README files and roadmap docs with accurate data. Run /wrangler:refresh-metrics to execute the full refresh cycle.

What metrics can I track across multiple governance documents?

Track issue counts by status, priority, and type; specification metrics; percentages within categories; and identify top projects. The Skill aggregates this data across MCP issues and updates README, NEXT_STEPS, and roadmap files with Last Updated timestamps for consistency.

Can I keep governance documentation synchronized with live issue data?

Yes. The Skill scans your MCP issues in real time, aggregates metrics by status, priority, type, and phase, then pushes updates directly to governance documents, ensuring README and roadmap files always reflect current counts and project rankings.

What data sources does the metrics refresh tool read from?

The Skill requires a TypeScript runtime with an issues_list accessor to scan MCP issues. It reads issue metadata by status, priority, type, and phase, then writes aggregated counts and percentages to .wrangler Markdown files.

When should I use automated metrics refresh over manual updates?

Use automated refresh when governance documents track multiple issue categories (status, priority, type, phase) across projects. Manual updates become error-prone and outdated; automation ensures consistency and eliminates manual recalculation of percentages and project rankings.