This guide helps you diagnose and fix common issues with Skill-Seeker.
- Installation Issues
- Search Problems
- Installation Failures
- Security Scanner Issues
- Performance Problems
- GitHub API Issues
- General Debugging
Symptoms:
$ /skill-seeker:seek frontend
-bash: /skill-seeker:seek: No such file or directory
Diagnosis:
# Check if plugin is installed (inside Claude Code)
/plugin
# Go to the "Installed" tab and look for skill-seekerSolutions:
- Install via the plugin marketplace:
# Inside Claude Code:
/plugin marketplace add mmmantasrrr/skill-seeker
/plugin install skill-seeker@skill-seeker
-
Restart Claude Code: After installing, restart Claude Code completely.
-
Test locally:
git clone https://github.com/mmmantasrrr/skill-seeker.git
claude --plugin-dir ./skill-seeker- Verify file permissions:
chmod +x scripts/*.sh
chmod +x scripts/*.pySymptoms:
Error: curl not found
Error: jq not found
Error: python3 not found
Diagnosis:
# Check which dependencies are missing
which curl # Should output: /usr/bin/curl
which jq # Should output: /usr/bin/jq
which python3 # Should output: /usr/bin/python3Solutions:
On macOS:
# Install using Homebrew
brew install curl jq python3On Ubuntu/Debian:
sudo apt-get update
sudo apt-get install curl jq python3On CentOS/RHEL:
sudo yum install curl jq python3On Windows (WSL):
sudo apt-get install curl jq python3Symptoms:
$ /skill-seeker:seek react
No skills found matching "react"
Diagnosis:
# Test registry search directly
./scripts/search-registry.sh react
# Test GitHub API connectivity
curl -s https://api.github.com/rate_limitSolutions:
- Check internet connection:
ping -c 3 github.com- Try broader search terms:
# Instead of very specific:
/skill-seeker:seek react-hooks-typescript-patterns
# Try broader:
/skill-seeker:seek react patterns- Search registry directly (no internet needed):
cd /path/to/skill-seeker
./scripts/search-registry.sh react- Check for typos: Common misspellings:
- "frontned" → "frontend"
- "javascipt" → "javascript"
- "kuberntes" → "kubernetes"
Symptoms: Results don't match what you're looking for.
Solutions:
- Use more specific terms:
# Too broad:
/skill-seeker:seek code
# Better:
/skill-seeker:seek python code quality
# Best:
/skill-seeker:seek python pep8 style guide- Check synonyms in registry: The registry expands queries. View synonyms:
cat registry.json | jq '.query_synonyms'- Use exact repository if known:
/skill-seeker:browse pbakaus/impeccableSymptoms: Search takes 30+ seconds or times out.
Diagnosis:
# Check internet speed
curl -o /dev/null https://speed.cloudflare.com/__down?bytes=1000000
# Check GitHub API status
curl -s https://www.githubstatus.com/api/v2/status.json | jqSolutions:
- Use registry search (instant):
# Registry is cached locally, no API calls
/skill-seeker:seek [query]
# First results are always from registry- Check network issues:
# Test API latency
time curl -s https://api.github.com/ > /dev/null-
GitHub API might be slow: Check https://www.githubstatus.com/ for service issues.
-
Reduce concurrent searches: Wait for one search to complete before starting another.
Symptoms:
Error: Failed to fetch skill from https://raw.githubusercontent.com/...
Diagnosis:
# Test URL directly
curl -I https://raw.githubusercontent.com/owner/repo/main/path/to/SKILL.md
# Check if repo exists
curl -s https://api.github.com/repos/owner/repoSolutions:
- Verify URL is correct:
- Check repository name spelling
- Verify branch name (main vs master)
- Confirm file path is correct
- Check if repo is private:
# Set GitHub token for private repos
export GITHUB_TOKEN=ghp_your_token_here- Verify file exists: Visit the URL in your browser:
https://github.com/owner/repo/blob/main/path/to/SKILL.md
- Repository might be deleted or renamed: Search for the skill again to find updated location.
Symptoms:
Security scan detected HIGH risk issues.
Installation blocked for your safety.
Diagnosis: Review the security scan output shown in the error message.
Solutions:
- Review what was detected: Security scanner found potentially malicious patterns. Check:
- Instruction overrides?
- Shell command injection?
- Data exfiltration attempts?
- If it's a false positive:
- Review the skill content manually
- Understand why it was flagged
- If safe, you can override (use with caution)
- Report the issue: If you believe it's a false positive, open an issue with:
- Skill URL
- Security scan output
- Why you think it's safe
- Find alternative skills:
/skill-seeker:seek [same topic]
# Look for skills with higher trust scoresSymptoms: Skill loads successfully but Claude doesn't apply it.
Diagnosis:
# Verify skill is loaded
/skill-seeker:unload
# Check the list of loaded skillsSolutions:
- Be explicit in your request:
# Instead of:
"Review this code"
# Try:
"Apply the [skill name] framework to review this code"
- Check for skill conflicts: Multiple skills might conflict. Unload others:
/skill-seeker:unload
# Remove conflicting skills, keep only the one you need- Reload the skill:
/skill-seeker:unload
/skill-seeker:install [same-skill-path]- Verify skill content: Visit the skill file on GitHub to ensure it has actual content.
Symptoms:
Error: Python script failed
Traceback...
Diagnosis:
# Test scanner directly
python3 scripts/scan-skill.py --help
# Check Python version
python3 --version # Should be 3.6+Solutions:
- Verify Python installation:
python3 --version
# Should output: Python 3.x.x- Test scanner manually:
echo "# Test skill" > /tmp/test-skill.md
python3 scripts/scan-skill.py /tmp/test-skill.md- Check skill file encoding: Some files with unusual encoding can crash the scanner:
file path/to/SKILL.md
# Should show: UTF-8 Unicode text- Update Python: If using Python < 3.6, update to a newer version.
Symptoms: Safe skills are flagged as HIGH risk.
Solutions:
- Review specific detections: The scanner shows what was detected. Common false positives:
- Legitimate HTML examples in documentation
- Example code showing security vulnerabilities (educational)
-
Check trust score: High trust score (60+) indicates community-validated safety.
-
Manual review: Read the skill content yourself before installing.
-
Report false positives: Open an issue so we can improve the scanner.
Symptoms: Noticeable delay in Claude's responses.
Solutions:
- Unload unnecessary skills:
/skill-seeker:unload
# Remove skills you're not currently using-
Load fewer skills: Recommended: 1-3 skills for focused work Maximum: 5-6 skills for complex projects
-
Use more specific skills: Specific skills have less content than broad ones:
- ✅ "React Hooks Patterns" (focused)
- ❌ "Complete JavaScript Guide" (too broad)
Symptoms: System becomes slow, high RAM usage.
Solutions:
- Unload all skills:
/skill-seeker:unload
# Remove all loaded skills-
Restart Claude: Fresh start clears all cached content.
-
Load skills one at a time: Only load what you need for the current task.
Symptoms:
Error: API rate limit exceeded.
Rate limit will reset in 32 minutes.
Diagnosis:
# Check current rate limit
curl -H "Authorization: token $GITHUB_TOKEN" \
https://api.github.com/rate_limitSolutions:
- Set GitHub token:
# Create token at https://github.com/settings/tokens
export GITHUB_TOKEN=ghp_your_token_here
# Add to shell profile for persistence
echo 'export GITHUB_TOKEN=ghp_your_token' >> ~/.bashrc
source ~/.bashrcThis increases limit from 60 to 5,000 requests/hour.
- Use registry search (no limits):
# Registry searches don't use API
/skill-seeker:seek [query]- Wait for reset: Check when rate limit resets:
curl https://api.github.com/rate_limit | jq '.rate.reset'
date -r 1234567890 # Replace with the reset timestampSymptoms:
Error: Bad credentials
Solutions:
- Check token format:
echo $GITHUB_TOKEN
# Should start with: ghp_- Verify token is valid:
curl -H "Authorization: token $GITHUB_TOKEN" \
https://api.github.com/user- Create new token:
- Go to https://github.com/settings/tokens
- Generate new token (classic)
- Select scope:
public_repo(minimum) - Copy token immediately (shown only once)
- Unset invalid token:
unset GITHUB_TOKEN
# Will use unauthenticated access (60 req/hour)Add verbose output to diagnose issues:
# Enable bash debugging
export DEBUG=1
# Run command with detailed output
bash -x scripts/search-github.sh "test query"# View recent command output
# (varies by shell and system)
# Check system logs (macOS)
log show --predicate 'process == "Claude"' --last 10m
# Check system logs (Linux)
journalctl -u claude-code --since "10 minutes ago"# Test registry search
./scripts/search-registry.sh test
# Test GitHub API search
./scripts/search-github.sh test
# Test skill fetching
./scripts/fetch-skill.sh owner/repo path/to/skill.md
# Test security scanner
python3 scripts/scan-skill.py tests/fixtures/clean-skill.mdWhen reporting bugs, include:
# Operating system
uname -a
# Dependency versions
curl --version
jq --version
python3 --version
# Plugin version
cat .claude-plugin/plugin.json | jq '.version'
# Registry version
cat registry.json | jq '.version'If none of these solutions work:
-
Search existing issues: https://github.com/mmmantasrrr/skill-seeker/issues
-
Open a new issue: https://github.com/mmmantasrrr/skill-seeker/issues/new
Include:
- Problem description
- Steps to reproduce
- Error messages (full output)
- System information
- What you've already tried
- Check documentation:
- Community help:
- Start a discussion
- Ask in Claude Code community forums
# Update Skill-Seeker
cd /path/to/skill-seeker
git pull origin main
# Update dependencies
brew upgrade curl jq python3 # macOS
sudo apt-get upgrade curl jq python3 # Linux
# Clean cache (if experiencing issues)
rm -rf /tmp/claude-skills-cache-
Keep GitHub token fresh: Tokens expire. Regenerate annually.
-
Unload skills when done: Prevents conflicts and improves performance.
-
Review security scans: Don't blindly override security warnings.
-
Monitor rate limits: If doing heavy searching, set up a token.
-
Report bugs: Help improve Skill-Seeker by reporting issues.
| Feature | Skill-Seeker (Skills) | MCP Tools |
|---|---|---|
| Type | Behavioral frameworks (prompts) | Executable code |
| Purpose | Shape AI thinking | Add capabilities |
| Installation | Markdown files | Binary/code installation |
| Security | Content scanning | Code execution |
Use Skill-Seeker when: You want Claude to apply specific thinking patterns, frameworks, or best practices.
Use MCP tools when: You need Claude to interact with external systems or execute code.
Trust scores indicate skill quality based on:
- Repository stars (log scale, max 40 points)
- Recent activity (updated within 30 days, max 20 points)
- Fork count (log scale, max 15 points)
- Proper GitHub topics (5 points)
- Not archived, has description, has license (5 points each)
Score ranges: 60+ (HIGH) → 40–59 (MEDIUM) → <40 (LOW)
Yes! You can install multiple complementary skills sequentially. Claude will apply all frameworks simultaneously. For best results, limit to 1–3 focused skills per session and unload any you no longer need.
Use the browse command to list all skills in a repository:
/skill-seeker:browse owner/repoThen view the raw file on GitHub before installing.
Yes! Skills are plain markdown files. Create a repository with a .claude/skills/ directory, add your SKILL.md files, and install from your repo. See pbakaus/impeccable for a reference example.
Yes. You'll need a GITHUB_TOKEN with private repo access:
export GITHUB_TOKEN=ghp_your_token_here
/skill-seeker:install owner/private-repo/path/to/SKILL.mdNote: private skills won't appear in public search results.
Need more help? Open an issue or start a discussion.