Automated summary
This plugin automatically detects recurring workflow patterns from coding agent sessions, generates reusable skills, and can load them dynamically mid-session.
Strengths
- Automates skill creation from observed patterns
- Loads skills without requiring session restart
- Proactively discovers relevant skills for current tasks
- Confidence scoring system to filter high-quality patterns
Limitations
- Requires npm package installation for CLI commands
- Pattern detection limited to tool sequences of 2–10 steps
- Patterns must occur at least 3 times within the last 7 days
Use this plugin when you frequently perform repetitive tasks with your coding agent and want to automate turning them into reusable skills.
Avoid using it for one-off or infrequent workflows, or if you prefer to manage your skills manually.
Security analysis
CautionThe skill documents a tool that auto-generates and loads skills. It includes a bash installation command, which poses a risk if the target script is compromised. No direct destructive or exfiltrating actions are described, but the tool's dynamic loading feature could be a vector for malicious skills.
- •Instructs running a bash script for installation, which could execute arbitrary code if the script is untrusted.
- •Dynamic skill loading could introduce untrusted instructions if not properly reviewed.
Examples
Show me the patterns that have been detected so I can approve or reject them.Load the skill named 'code-review' into the current session.What is the current status of the auto-skill plugin? Show me stats and config.name: auto-skill-guide description: Documentation for the Auto-Skill plugin - automatic workflow pattern detection, skill generation, and dynamic loading
Auto-Skill Plugin
This plugin automatically detects workflow patterns from your coding agent sessions, generates reusable skills, and can load them dynamically mid-session.
CLI Tool Installation
The agent skills are now installed, but to use CLI commands like auto-skill init, auto-skill discover, etc., you need to install the npm package.
Quick Install:
# Option 1: Run the included install script
bash ~/.agents/skills/auto-skill-guide/install-cli.sh
# Option 2: Install globally via npm
npm install -g @matrixy/auto-skill
# Option 3: Use without installing (via npx)
npx @matrixy/auto-skill init
Verify: auto-skill version
How It Works
Session 1: Grep → Read → Edit ─┐
Session 2: Grep → Read → Edit ├──▶ Pattern Detected → SKILL.md
Session 3: Grep → Read → Edit ─┘
- Observation: Every tool call is recorded via PostToolUse hook
- Detection: Patterns are analyzed for repetition (3+ occurrences)
- Generation: Approved patterns become SKILL.md files with proper frontmatter
- Discovery: Claude proactively offers relevant skills for your tasks
- Loading: Skills can be loaded mid-session without restart
Commands
/auto-skill:review
Review and approve detected patterns:
/auto-skill:review # List all detected patterns
/auto-skill:review preview ID # Preview a pattern as a skill
/auto-skill:review approve ID # Generate skill from pattern
/auto-skill:review reject ID # Dismiss a pattern
/auto-skill:load
Load a generated skill into the current session:
/auto-skill:load # List available skills
/auto-skill:load <name> # Load specific skill immediately
Skills loaded this way become active immediately without requiring a session restart.
/auto-skill:status
Show system diagnostics:
/auto-skill:status # Display stats, patterns, and config
Pattern Detection
Patterns are detected when:
- Same tool sequence appears 3+ times across sessions
- Sequence is 2-10 tools long
- Pattern has occurred within the last 7 days
Confidence Scoring
| Factor | Weight | Description | |--------|--------|-------------| | Occurrences | 40% | More occurrences = higher confidence | | Length | 20% | 3-5 tools is ideal | | Success Rate | 25% | Successful patterns score higher | | Recency | 15% | Recent patterns are prioritized |
Example Patterns
Grep → Read → Edit # Search, read context, make changes
Glob → Read → Write # Find files, read, create new file
Read → Edit → Bash # Read file, edit, run tests
Dynamic Skill Loading
Unlike standard Claude Code skills (loaded at session start), auto-generated skills can be loaded mid-session using a registry system.
How It Works
- A lightweight registry indexes all skills (~metadata only)
- Scripts retrieve and format skill content on demand
- Output uses clear delimiters that signal active instructions:
======================================================================
SKILL LOADED: <name>
Confidence: <score>
Allowed tools: <tools>
======================================================================
<skill instructions>
======================================================================
END OF SKILL - INSTRUCTIONS ARE NOW ACTIVE
======================================================================
Proactive Discovery
Claude can automatically discover relevant skills using the skill-discovery skill:
- User requests a multi-step task
- Claude searches for matching skills
- If found, Claude asks: "Would you like me to load this skill?"
- User approves → skill is loaded and followed
CLI Commands
auto-skill discover # Discover skill patterns
auto-skill stats # Show adoption statistics
auto-skill graduate # Manage skill graduation
auto-skill agents list # List known agents
auto-skill agents detect # Detect installed agents
To search for community skills, use Skills CLI:
npx skills find "query" # Interactive search
npx skills add owner/repo # Install skill
Execution Contexts
Generated skills automatically get appropriate execution settings:
| Pattern Type | Context | Agent | Why |
|-------------|---------|-------|-----|
| Grep → Read | Inline | Explore | Read-only, safe |
| Read → Edit → Bash | Fork | general-purpose | Has side effects |
Inline: Runs in current conversation context.
Fork (context: fork): Runs in isolated subagent. Use for:
- Tasks with side effects (deployments, builds)
- Workflows that shouldn't pollute conversation history
- Long-running operations
Tool Restrictions
Generated skills include allowed-tools based on the pattern:
allowed-tools: Grep, Read, Edit
This prevents scope creep and ensures predictable behavior.
Generated Skills
Auto-generated skills are saved to:
~/.claude/skills/auto/<skill-name>/SKILL.md
Each skill includes:
- YAML frontmatter with metadata
auto-generated: trueflagcontext: forkif appropriateallowed-toolsrestrictions- Confidence score and source sessions
- Procedural steps derived from the pattern
Configuration
Detection thresholds (in ~/.claude/auto-skill.local.md):
---
detection:
min_occurrences: 3 # Minimum pattern repetitions
min_sequence_length: 2 # Shortest pattern
max_sequence_length: 10 # Longest pattern
lookback_days: 7 # Analysis window
min_confidence: 0.7 # Suggestion threshold
---
Data Storage
| Data | Location |
|------|----------|
| Events | ~/.claude/auto-skill/events.db |
| Skills | ~/.claude/skills/auto/ |
| Tracking | ~/.claude/auto-skill/skills_tracking.db |
Privacy
- All data is stored locally
- No data is sent to external services
- Anonymous telemetry can be disabled via
AUTO_SKILL_NO_TELEMETRY=1orDO_NOT_TRACK=1
Troubleshooting
No patterns detected?
- Need 3+ occurrences of the same sequence
- Check the lookback period (default: 7 days)
- Run
/auto-skill:statusto see event counts
Skill not loading?
- Run
auto-skill discoverto refresh - Check the skill exists in
~/.claude/skills/auto/
Hooks not working?
- Verify plugin is installed correctly
- Check
hooks/hooks.jsonconfiguration - Ensure Node.js 18+ is available
Want to reset?
- Delete
~/.claude/auto-skill/events.db - Remove skills from
~/.claude/skills/auto/
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/auto-skill-plugin-pattern-detection-generation-mma3jr7k/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/auto-skill-plugin-pattern-detection-generation-mma3jr7k' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/auto-skill-plugin-pattern-detection-generation-mma3jr7k/download' --output '.skill-downloads/auto-skill-plugin-pattern-detection-generation-mma3jr7k/SKILL.md.part' && mv '.skill-downloads/auto-skill-plugin-pattern-detection-generation-mma3jr7k/SKILL.md.part' '.skill-downloads/auto-skill-plugin-pattern-detection-generation-mma3jr7k/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/auto-skill-plugin-pattern-detection-generation-mma3jr7k/SKILL.md' && test -s '.skill-downloads/auto-skill-plugin-pattern-detection-generation-mma3jr7k/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/auto-skill-guide' && cp -R '.skill-downloads/auto-skill-plugin-pattern-detection-generation-mma3jr7k' '.claude/skills/auto-skill-guide'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/auto-skill-plugin-pattern-detection-generation-mma3jr7k'openskills read 'auto-skill-plugin-pattern-detection-generation-mma3jr7k'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/auto-skill-plugin-pattern-detection-generation-mma3jr7k/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.