pattern-detector

Name: pattern-detector
Availability: InStock
Author: Binatrix

Analyze seven days of session logs to detect recurring actions and queue automation suggestions.

Updated Aug 27, 2026

Search Tags:#session-history #pattern-detection #memory-analysis #automation-suggestions #proactivity-engine #on-session-start

Ready to run

npx skills add https://github.com/BinatrixAI/tandem-marketplace --skill pattern-detector-binatrixai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pattern-detector
Source: https://github.com/BinatrixAI/tandem-marketplace/tree/main/plugins/tandem/skills/core/pattern-detector
Command: npx skills add https://github.com/BinatrixAI/tandem-marketplace --skill pattern-detector-binatrixai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically analyzes the last 7 days of memory/sessions at session start to detect recurring actions and suggest automations, reducing repetitive tasks and improving proactive assistance. This skill runs silently at session start and is not user-invocable.

Core Features & Use Cases

Reads the last 7 days of memory/sessions to identify recurring commands and actions.
Proposes automations via the proactivity engine and queues suggestions for the next natural pause.
Enforces guardrails: activates only when there are at least 3 session logs; does not run during onboarding; does not re-suggest patterns dismissed twice; not user-invocable.
Use Case: when /email-triage is used across several days, it can propose automated daily triage.

Quick Start

Scan the last 7 days of session logs to detect patterns and queue automations for the proactivity engine.

Frequently Asked Questions about pattern-detector

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

FAQPage Schema

How does automatic pattern detection from session logs work?▼

Pattern detection works by scanning the last seven days of session logs at session start to identify recurring commands and queue the strongest qualifying automation suggestion for the proactivity engine.

How to automate recurring tasks identified from session history?▼

Recurring tasks are automated when the system analyzes session history logs, detects repeated command patterns, and queues a proactivity-engine suggestion to propose an automation at the next natural pause.

How many days of session logs are needed for pattern detection to activate?▼

Pattern detection requires at least three days of session logs stored under memory/sessions to activate, ensuring sufficient data exists to identify recurring actions before suggesting automations.

Why does pattern detection not run during onboarding?▼

Pattern detection does not run during onboarding to prevent premature automation suggestions before enough session history is established, and it also respects exclusions if a pattern was previously dismissed twice.

Can I manually trigger session history analysis to find automation suggestions?▼

Session history analysis cannot be manually triggered because it runs silently at session start, automatically queuing automation suggestions through the proactivity engine without user invocation.