Configuration Structure
Configuration is defined by theConfig interface:
Config Interface
Detection Configuration
Controls how patterns are detected and filtered:DetectionConfig
Default Detection Config
Detection Config Examples
Detection Config Examples
- Aggressive Detection
- Conservative Detection
- Long Workflows
- Ignore Noisy Tools
Detect patterns more aggressively (more noise, faster learning):
Agent Settings
Configures multi-agent support and skill sharing:AgentSettings
Default Agent Settings
Agent Configuration Examples
When
symlinkSkills: true, Auto-Skill creates symlinks from ~/.claude/skills/auto/ to other agents’ skill directories (e.g., ~/.cursor/skills/auto/).Provider Settings
Configures skill discovery sources:ProviderSettings
Default Provider Settings
Provider Configuration Examples
Custom Paths
Override default storage locations:Custom Paths
Default Paths
| Setting | Default | Description |
|---|---|---|
dbPath | ~/.claude/auto-skill/events.db | SQLite event database |
skillsOutputDir | ~/.claude/skills/auto/ | Generated skills directory |
Master Enable/Disable
Disable Auto-Skill entirely:Disable Auto-Skill
When disabled, hooks will exit immediately without recording events or analyzing patterns.
Configuration File
Create.claude/auto-skill.local.md in your project root:
.claude/auto-skill.local.md
Loading Configuration
Loading Config
Configuration Merging
- Merge Behavior
- Example
Configuration is merged with the following precedence:
- Project-local config (
.claude/auto-skill.local.md) - Default config (built-in defaults)
Environment Variables
Some settings can be controlled via environment variables:| Variable | Purpose | Example |
|---|---|---|
AUTO_SKILL_NO_TELEMETRY | Disable telemetry | export AUTO_SKILL_NO_TELEMETRY=1 |
DO_NOT_TRACK | Disable telemetry | export DO_NOT_TRACK=1 |
GITHUB_TOKEN | Skills.sh API auth | export GITHUB_TOKEN=ghp_xxx |
AUTO_SKILL_DB_PATH | Custom database path | export AUTO_SKILL_DB_PATH=/tmp/events.db |
AUTO_SKILL_SKILLS_DIR | Custom skills directory | export AUTO_SKILL_SKILLS_DIR=~/my-skills |
Environment variables take precedence over configuration file settings.
Complete Example
.claude/auto-skill.local.md
CLI Configuration Commands
CLI Commands
Configuration Best Practices
Commit to Version Control
Commit to Version Control
Check
.claude/auto-skill.local.md into Git so the entire team uses consistent settings:Document Your Choices
Document Your Choices
Use the markdown body to explain why you chose specific settings:
Start Conservative
Start Conservative
Begin with higher thresholds and relax them if needed:It’s easier to lower thresholds than to deal with noise.
Project-Specific Settings
Project-Specific Settings
Different projects may need different configs:
- New projects: Aggressive detection to bootstrap skills
- Mature projects: Conservative detection, patterns are established
- Experiments: Disable Auto-Skill entirely (
enabled: false)
Troubleshooting
Config file not being loaded
Config file not being loaded
Check:
- File is named exactly
.claude/auto-skill.local.md - File is in the project root (same directory as
.git/) - YAML frontmatter is valid (use
---markers) - Field names use snake_case (
min_occurrences, notminOccurrences)
Patterns not being detected
Patterns not being detected
Possible causes:
minOccurrencestoo high (lower to 2-3)minConfidencetoo high (lower to 0.6)lookbackDaystoo short (increase to 14-30)- Tools in sequence are in
ignoredToolslist - Not enough sessions recorded yet
Too many false positives
Too many false positives
Solutions:
- Increase
minOccurrencesto 5-7 - Increase
minConfidenceto 0.8-0.85 - Add noisy tools to
ignoredTools - Decrease
maxSequenceLengthto 6-8
Next Steps
Custom Patterns
Deep dive into pattern detection configuration
Integration Guide
Learn how configuration affects the integration
CLI Reference
Complete CLI command reference