pattern-detect

Generate weekly pattern reports from usage data with trend and anomaly analyses.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/zm2231/personal-os-cowork --skill pattern-detect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pattern-detect
Source: https://github.com/zm2231/personal-os-cowork/tree/main/.claude/skills/pattern-detect
Command: npx skills add https://github.com/zm2231/personal-os-cowork --skill pattern-detect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users receive raw usage logs without clear guidance, making it hard to identify what works, what doesn’t, and how to improve productivity.

Core Features & Use Cases

  • Automated weekly analysis of session ratings, corrections, tool preferences, and time‑of‑day usage.
  • Insight generation with actionable recommendations, trend tracking, and anomaly detection.
  • Use case: After a week of varied sessions, request a pattern report to see peak productivity windows, recurring frustrations, and optimization suggestions.

Quick Start

Ask for a weekly pattern report by saying “Give me the weekly pattern report.”

Frequently Asked Questions about pattern-detect

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

FAQPage Schema
How do I generate a weekly pattern report from my usage data?

Weekly pattern reports require access to session logs, ratings, corrections, and timestamps to run frequency, co-occurrence, trend, and anomaly analyses. Provide these usage metrics to surface actionable insights and improvement areas.

What kind of actionable insights can I get from trend analysis of session logs?

Trend analysis of session logs surfaces peak productivity windows, recurring frustrations, tool preferences, and time-of-day usage patterns. These actionable insights help optimize personal productivity and identify strengths and areas for improvement.

Can I use productivity analysis to detect anomalies in my tool usage metrics?

Yes, productivity analysis applies anomaly detection to tool usage metrics and session feedback. By evaluating timestamps and corrections, it identifies unusual usage patterns and generates optimization suggestions for your workflow.

Do I need to provide timestamps and corrections to run frequency and co-occurrence analyses?

Yes, you need to provide timestamps, corrections, session logs, and ratings to run frequency and co-occurrence analyses. These inputs are required to accurately track trends and generate actionable recommendations from the usage data.

What is the best way to identify peak productivity windows from personal productivity logs?

The best way to identify peak productivity windows is to run an automated weekly analysis on personal productivity logs. Evaluating time-of-day usage and session ratings surfaces your most effective periods and recurring frustrations.