pattern-detector

Detects recurring session and memory patterns to surface automation opportunities.

11|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/brolag/neural-claude-code --skill pattern-detector-brolag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pattern-detector
Source: https://github.com/brolag/neural-claude-code/tree/main/skills/pattern-detector
Command: npx skills add https://github.com/brolag/neural-claude-code --skill pattern-detector-brolag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify recurring usage patterns from session logs and memory to surface automation opportunities and new agent ideas.

Core Features & Use Cases

  • Pattern extraction from session_logs and memory to surface potential skills and agents.
  • Detection of repeated command sequences, file access clusters, and similar prompts for pattern-driven improvements.
  • Use Case: When nightly optimization runs, surface ideas for new automation.

Quick Start

Run /evolve --detect-patterns to initiate pattern discovery on the current logs and memory.

Frequently Asked Questions about pattern-detector

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

FAQPage Schema
How do I find automation opportunities from session logs and memory?

Pattern detection scans session logs and memory to identify recurring command sequences, file access clusters, and similar prompts, surfacing potential skills and new agent ideas for automation.

What is pattern detection for skill improvement?

Pattern detection for skill improvement is the process of identifying repeated usage behaviors across commands, files, prompts, and errors to queue pattern-driven skill enhancements and new automations.

When should I run pattern detection during nightly optimization?

You should run pattern detection during nightly optimization or evolve sessions to discover patterns across recent logs and memory, automatically queuing pattern-driven skill improvements for the optimizer.

What data sources are needed to detect usage patterns?

Detecting usage patterns requires session logs and memory data sources, specifically capturing repeated command sequences, file access clusters, prompt similarities, and error occurrences to define detection logic.

Can I surface new skill ideas from repeated command sequences?

Yes, you can surface new skill ideas by detecting repeated command sequences and similar prompts, logging the results, and notifying optimizers to queue pattern-driven skill improvements.

Does pattern detection require external dependencies or components?

Pattern detection requires no external dependencies or components, operating directly on existing session logs and memory to define data sources, detection logic, output schema, and integration steps.