auto
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
Tracking Status (Auto-Captured)
Auto-Track: ![ -f .claude/.ref-autotrack ] && echo "✓ Enabled" || echo "✗ Disabled"
Sources Tracked: !wc -l < claude_usage/sources.md 2>/dev/null || echo "0"
Prompts Tracked: !grep -c '^Prompt:' claude_usage/prompts.md 2>/dev/null || echo "0"
Git Status: !git rev-parse --is-inside-work-tree &>/dev/null && echo "✓ Git repo" || echo "✗ Not a git repo"
Quick Example
/track:auto on
# ✓ Hooks-based tracking enabled
# PostToolUse: WebSearch/WebFetch/Read/Grep → claude_usage/sources.md
# SessionEnd: Major prompts → claude_usage/prompts.md
auto - Control Hooks-Based Auto-Tracking
Toggle or explicitly set automatic hooks-based tracking state.
Usage
/track:auto # Toggle between enabled/disabled
/track:auto on # Explicitly enable
/track:auto off # Explicitly disable
What it does
-
Check current status:
- Looks for
./.claude/.ref-autotrackmarker file - If exists → hooks-based tracking is enabled
- If missing → hooks are inactive
- Looks for
-
Update state:
- No argument → toggle current state
- Argument "on" → enable (create marker if missing)
- Argument "off" → disable (delete marker if exists)
-
When enabling:
- Creates
./.claude/.ref-autotrackwith metadata:# Track Plugin v2.0 - Automatic Tracking Enabled # # Hooks configured: # - PostToolUse: Tracks WebSearch, WebFetch, Read, Grep # - UserPromptSubmit: Captures user prompts # - SessionEnd: Pairs prompts with outcomes # # Initialized: <timestamp> - Hooks activate automatically
- No skill invocation needed
- Creates
-
When disabling:
- Deletes
./.claude/.ref-autotrackmarker file - Hooks stop running
- Temporary files cleaned up
- Deletes
-
Show new status:
- Reports whether hooks-based tracking is now enabled or disabled
- Shows what will be tracked based on current config
- Explains how to change verbosity settings
Output examples
When enabling:
✓ Hooks-based tracking enabled
Automatic tracking via hooks:
- PostToolUse: Research sources (WebSearch/WebFetch/Read/Grep) → claude_usage/sources.md
- SessionEnd: Major prompts and outcomes → claude_usage/prompts.md
Current verbosity settings:
- Prompts: major (only significant academic/development work)
- Sources: all (every search operation)
Hooks run automatically - no manual intervention needed.
Use /track:config to adjust verbosity settings.
When disabling:
✓ Hooks-based tracking disabled
Hooks will no longer run automatically.
Tracked files remain intact:
- claude_usage/sources.md
- claude_usage/prompts.md
To re-enable: /track:auto on
When toggling:
✓ Hooks-based tracking toggled: OFF → ON
[Shows enabled message above]
Prerequisites
Run /track:init first to create .claude/ directory structure.
Notes
- State changes do not affect existing tracked data
- Configuration in
.claude/.ref-configpersists across state changes - Marker file includes explanatory content and initialization timestamp
- Hooks activate/deactivate instantly based on marker presence
- Temporary files in
.claude/.track-tmp/are cleaned on disable
v2.0 Changes
Changed from v1.x:
- Old: Skill-based tracking (ref-tracker skill checked marker)
- New: Hooks-based tracking (hooks check marker)
- Benefit: Fully automatic, no skill activation needed
- Migration: Existing markers work unchanged
Implementation
Auto-tracking toggle functionality is implemented in scripts/auto.sh:
# Get skill directory
SKILL_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
# Execute auto script with arguments
bash "$SKILL_DIR/scripts/auto.sh" "$@"
Script: skills/auto/scripts/auto.sh (102 lines)
Features:
- Argument parsing (on/off/toggle)
- State detection via marker file
- Marker creation with metadata
- Temporary file cleanup on disable
- Status reporting with verbosity settings
- Toggle state tracking
See scripts/auto.sh for full implementation details.
More from cadrianmae/claude-marketplace
datetime
Use the `date` command via Bash tool whenever you or the user mention time, dates, or temporal concepts. Verify current date/time before ANY temporal response, as environment context may be outdated. Parse expressions like "tomorrow", "next week", "3 days", "in 2 weeks", "next Monday at 3pm". Proactively invoke for deadlines, schedules, time-sensitive tasks, week numbers, or any date/time reference.
70pandoc
Automatically assist with Pandoc document conversions when user mentions converting markdown to PDF/DOCX/HTML or other formats. Validate YAML frontmatter, check dependencies (bibliography, images), and provide format-specific conversion guidance. Use when user asks about citations, academic papers, presentations, or document generation from markdown.
6update
Update the current development session with progress notes
5list
List all development sessions
5nvr-list
This skill should be used when the user asks to "list neovim instances", "show all nvim", "what neovim processes are running", "list all editors", "show all active neovim", or wants to see all running neovim instances across all projects.
5current
Show the current session status
5