auto-recall

Extract recurring tool-call sequences from operation logs and generate SKILL.md files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ferundatattoo/ethereal --skill auto-recall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-recall
Source: https://github.com/ferundatattoo/ethereal/tree/main/.claude/skills/auto-recall
Command: npx skills add https://github.com/ferundatattoo/ethereal --skill auto-recall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repeated manual automation planning wastes time and leads to inconsistent automation patterns. Auto-Recall analyzes tool operation logs to identify recurring workflows and auto-generate reusable skills.

Core Features & Use Cases

  • Pattern discovery: scans logs to find repeated sequences of tool calls (3+ in the same order across sessions).
  • Skill generation: derives a reusable workflow and creates a SKILL.md for future reuse.
  • Automation acceleration: reduces time to implement new automations by reusing proven patterns.

Quick Start

Run an on-demand analysis to identify repeating tool-call patterns and generate corresponding SKILL.md entries.

Frequently Asked Questions about auto-recall

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

FAQPage Schema
How do I extract reusable workflow patterns from tool operation logs?

To extract reusable workflow patterns from tool operation logs, analyze sequences of recurring tool calls (Read, Write, Edit, Bash, Grep, Glob) to identify repeats across sessions and auto-generate new SKILL.md files for future automation.

What is the minimum number of repeated tool calls needed to generate an automation skill?

An automation skill is generated when a specific sequence of tool calls appears at least 3 times in the exact same order across different operation sessions logged in the system.

Where are the generated SKILL.md files stored after pattern discovery?

Generated SKILL.md files are stored under the .claude/skills/ directory, creating reusable automation entries derived from the workflow patterns detected in your logs.

Do I need a specific log file format to analyze tool operation workflows?

Yes, workflow analysis requires access to tool operation logs stored specifically at ~/.claude/tool_logs/operations.jsonl to derive repeating sequences and generate automation skills.

What is the best way to automate repetitive coding workflows across different projects?

The best way to automate repetitive workflows across projects is to run an on-demand analysis of tool-call logs to discover proven sequences, accelerating implementation by generating reusable skills instead of manual planning.

Why does automated skill discovery fail to find patterns in my logs?

Pattern discovery fails if the operations.jsonl log file lacks sequences appearing 3 or more times in the same order, as the tool requires repeated identical tool-call workflows across sessions to extract a skill.