Skills Analysis Troubleshooting
I'll help you diagnose and fix common issues with the Claude Skills Analyzer.
š Quick Diagnostics
Let me check your current setup and identify any issues:
Directory Structure Check
First, let me verify your project has the required directories:
Expected structure:
āāā data-exports/
ā āāā claude/ # Claude export files
ā āāā chatgpt/ # ChatGPT export files
āāā reports/ # Analysis outputs
āāā generated-skills/ # Generated skill packages
Data Files Check
Looking for these required files:
Claude exports (data-exports/claude/):
ChatGPT exports (data-exports/chatgpt/):
šØ Common Issues & Solutions
Issue: "No conversation files detected"
Causes:
- Files in wrong directories
- Incorrect file names
- Empty or corrupted JSON files
Solutions:
- Check file locations: Ensure JSON files are in correct
data-exports/ subdirectories
- Verify file names: Must match exactly (case-sensitive)
- Validate JSON: Open files in text editor to check they're valid JSON
- Check file sizes: Empty files (0 bytes) won't work
Issue: "Analysis produces no patterns"
Causes:
- Too few conversations (need 20+ minimum)
- Conversations too short or simple
- No recurring patterns in usage
Solutions:
- Accumulate more data: Export again after more AI usage
- Lower thresholds: Adjust frequency requirements in analysis
- Check conversation quality: Need substantial back-and-forth interactions
- Try different timeframes: Use older exports if available
Issue: "Plugin command not found"
Causes:
- Plugin not properly installed
- Claude Code needs restart
- Marketplace not added correctly
Solutions:
- Verify installation:
/plugin list
- Restart Claude Code: Close and reopen
- Reinstall plugin:
/plugin uninstall claude-skills-analyzer@hirefrank
/plugin install claude-skills-analyzer@hirefrank
Issue: "JSON parsing errors"
Causes:
- Incomplete export downloads
- File corruption during transfer
- Unsupported export format versions
Solutions:
- Re-download exports: Get fresh copies from AI platforms
- Check file integrity: Verify files open properly in text editor
- Try smaller batches: Export smaller date ranges if available
Issue: "Skills generation fails"
Causes:
- Insufficient write permissions
- Conflicting files in output directories
- Pattern analysis errors
Solutions:
- Check permissions: Ensure you can write to project directory
- Clear output directories: Remove old
reports/ and generated-skills/ content
- Try incremental analysis: Start with Option A (report only)
š§ Manual Diagnostics
Check Your Export Files
# Navigate to your data directory
cd data-exports
# Check file sizes (should be >1KB)
ls -la claude/
ls -la chatgpt/
# Preview file contents (first few lines)
head -5 claude/conversations.json
head -5 chatgpt/conversations.json
Validate JSON Structure
# Check if files are valid JSON (on systems with jq)
jq . claude/conversations.json > /dev/null && echo "Claude JSON valid"
jq . chatgpt/conversations.json > /dev/null && echo "ChatGPT JSON valid"
š Data Requirements
Minimum Requirements
- 20+ conversations total across platforms
- Average 3+ exchanges per conversation
- Variety of topics/tasks represented
- JSON files >1KB in size
Optimal Requirements
- 50+ conversations for meaningful patterns
- Mix of short and long conversations
- Regular usage patterns over time
- Both platforms represented (if you use both)
šÆ Quick Fixes
Create Missing Directories
mkdir -p data-exports/claude data-exports/chatgpt reports generated-skills
Test Plugin Installation
# Check if plugin is available
/help | grep analyze-skills
# List installed plugins
/plugin list | grep claude-skills-analyzer
Reset and Retry
# Clear any partial outputs
rm -rf reports/* generated-skills/*
# Re-run analysis with fresh start
/analyze-skills
š Getting Additional Help
For Setup Issues
- Review
/skills-setup for complete setup guide
- Check plugin README at
plugins/claude-skills-analyzer/README.md
- Verify you have the latest plugin version
For Analysis Issues
- Try Option A (Analysis Report Only) first
- Review conversation export quality
- Consider smaller dataset for initial testing
For Technical Issues
- Check GitHub Issues
- Report bugs with error messages and setup details
- Join discussions for community support
š” Pro Troubleshooting Tips
- Start small: Test with a small, known-good dataset first
- Check permissions: Ensure you can read/write in the project directory
- Update regularly: Keep the plugin updated to latest version
- Document patterns: Note what types of conversations work best
- Incremental approach: Use existing analysis logs for efficiency
š Still Having Issues?
If problems persist:
-
Gather diagnostics:
- Plugin version (
/plugin list)
- Error messages (exact text)
- File sizes and locations
- Claude Code version
-
Try minimal test:
- Create new directory
- Add just 1-2 export files
- Run analysis with Option A
-
Get support:
- Open GitHub issue with full details
- Include anonymized error logs
- Describe expected vs actual behavior
Let me know what specific issue you're experiencing and I'll provide targeted help!