trend-tracker

Classify WordPress scan findings as NEW or RECURRING using historical trends.

27|1|Updated Feb 16, 2026

Search Tags:#security #reporting #issue tracking #diagnostics #trend analysis #wordpress

Ready to run

npx skills add https://github.com/dr-robert-li/cowork-wordpress-expert --skill trend-tracker-dr-robert-li

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trend-tracker
Source: https://github.com/dr-robert-li/cowork-wordpress-expert/tree/main/skills/trend-tracker
Command: npx skills add https://github.com/dr-robert-li/cowork-wordpress-expert --skill trend-tracker-dr-robert-li

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users understand if issues found during a WordPress scan are new or recurring problems by comparing current scan results with historical data.

Core Features & Use Cases

Issue Classification: Automatically labels findings as [NEW] or [RECURRING] based on historical data.
Trend Persistence: Maintains a history of findings in trends.json for ongoing analysis.
Use Case: After running a security scan, you can quickly see if a vulnerability is a fresh issue or one that has persisted across multiple scans, allowing for more targeted remediation efforts.

Quick Start

Run the trend-tracker skill after the report-generator has completed its scan.

Frequently Asked Questions about trend-tracker

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

FAQPage Schema

How do I track if WordPress security scan findings are new or recurring?▼

To track WordPress security scan findings, you compare current diagnostic results against historical data. This classifies issues as [NEW] or [RECURRING] by maintaining a rolling history of scan data for ongoing trend analysis.

What is the best way to classify recurring vulnerabilities in a security report?▼

The best way to classify recurring vulnerabilities is to compare current scan data against historical trends stored in memory. This automatically patches inline [RECURRING] or [NEW] badges onto report findings for targeted remediation.

How does issue trend analysis work for WordPress diagnostics?▼

Issue trend analysis works by comparing current diagnostic scan results against a two-slot rolling history of previous data. It patches inline badges onto findings to indicate whether an issue is newly discovered or has persisted across scans.

Do I need a live WordPress connection to track issue trends from a security scan?▼

You do not need a live WordPress connection to track issue trends. The trend analysis operates solely on scan result data without direct WordPress interaction, classifying findings by comparing them against stored historical trends.

Can I use historical scan data to patch inline badges onto security findings?▼

Yes, you can use historical scan data to patch inline badges onto security findings. The system compares current diagnostic results against a rolling history and automatically patches [NEW] or [RECURRING] labels directly onto the report.

What are the limitations of maintaining a two-slot rolling history for trend analysis?▼

The limitation of a two-slot rolling history for trend analysis is that it only stores the current and immediately previous scan. This restricts trend visibility to a short window, preventing long-term diagnostic pattern analysis across multiple historical scans.